Yes — calendar.nyu.edu has IPv6.

Has both IPv4 (A) and IPv6 (AAAA) addresses.

IPv6 readiness

Website, mail and DNS all work over IPv6.

Website over IPv6 calendar.nyu.edu has 4 IPv6 addresses and answers on every one we tested (4 more not tested). ✓ 2600:9000:2501:9e00:16:2450:51c0:93a1 answers · 443✓ 2600:9000:2501:ea00:16:2450:51c0:93a1 answers · 443✓ 2600:9000:2501:2c00:16:2450:51c0:93a1 answers · 443✓ 2600:9000:2501:d400:16:2450:51c0:93a1 answers · 443– 2600:9000:2501:9200:16:2450:51c0:93a1 not tested– 2600:9000:2501:6c00:16:2450:51c0:93a1 not tested– 2600:9000:2501:5000:16:2450:51c0:93a1 not tested– 2600:9000:2501:ac00:16:2450:51c0:93a1 not tested	yes
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.	yes
Nameservers have IPv6 2 of 3 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns1.nyu.net ✓ns4.nyu.edu ✗ns2.nyu.org ✓	yes

HTTPS over IPv6 · not part of the grade yet
More than 5 redirects — stopped following.

https://calendar.nyu.edu/ via 2600:9000:2501:9e00:16:2450:51c0:93a1 → 302https://www.google.com/calendar/hosted/nyu.edu via 2001:4860:4829:7700:: → 302https://calendar.google.com/calendar/hosted/nyu.edu via 2607:f8b0:4004:c1d::8a → 302https://calendar.google.com/calendar/a/nyu.edu via 2607:f8b0:4004:c1d::8a → 302https://www.google.com/a/nyu.edu/ServiceLogin?service=cl&continue=https://calendar.google.com/calendar/&followup=https://calendar.google.com/calendar/&osid=1&passive=1209600 via 2001:4860:4829:7700:: → 302https://accounts.google.com/samlredirect?continue=https%3A%2F%2Fcalendar.google.com%2Fcalendar%2F&sso_profile=inboundSamlSsoProfiles%2F03a14e4u3zlpreo via 2607:f8b0:4004:c06::54 → 302

Nothing keeping you from an A

Nothing to fix
Show it off: add the badge to your README.
[![IPv6](https://aaaa.bot/badge/calendar.nyu.edu.svg)](https://aaaa.bot/calendar.nyu.edu)

Check again

calendar.nyu.edu Has IPv6

Alias of	d2668vs6wprm13.cloudfront.net
A (IPv4)	18.154.227.85 18.154.227.34 18.154.227.17 18.154.227.118
AAAA (IPv6)	2600:9000:2501:9e00:16:2450:51c0:93a1 2600:9000:2501:ea00:16:2450:51c0:93a1 2600:9000:2501:2c00:16:2450:51c0:93a1 2600:9000:2501:d400:16:2450:51c0:93a1 2600:9000:2501:9200:16:2450:51c0:93a1 2600:9000:2501:6c00:16:2450:51c0:93a1 2600:9000:2501:5000:16:2450:51c0:93a1 2600:9000:2501:ac00:16:2450:51c0:93a1

Browsers on dual-stack networks will usually pick IPv6 here (the "Happy Eyeballs" algorithm races both and prefers v6).

Copy the evidence — a citation-ready record of this measurement

IPv6 measurement: calendar.nyu.edu
Measured 2026-11-03 03:37:45 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    18.154.227.85, 18.154.227.34, 18.154.227.17, 18.154.227.118
AAAA (IPv6): 2600:9000:2501:9e00:16:2450:51c0:93a1, 2600:9000:2501:ea00:16:2450:51c0:93a1, 2600:9000:2501:2c00:16:2450:51c0:93a1, 2600:9000:2501:d400:16:2450:51c0:93a1, 2600:9000:2501:9200:16:2450:51c0:93a1, 2600:9000:2501:6c00:16:2450:51c0:93a1, 2600:9000:2501:5000:16:2450:51c0:93a1, 2600:9000:2501:ac00:16:2450:51c0:93a1

Readiness grade A: Website, mail and DNS all work over IPv6.
- Website over IPv6: calendar.nyu.edu has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
    2600:9000:2501:9e00:16:2450:51c0:93a1: answers (TCP 443)
    2600:9000:2501:ea00:16:2450:51c0:93a1: answers (TCP 443)
    2600:9000:2501:2c00:16:2450:51c0:93a1: answers (TCP 443)
    2600:9000:2501:d400:16:2450:51c0:93a1: answers (TCP 443)
    2600:9000:2501:9200:16:2450:51c0:93a1: not tested
    2600:9000:2501:6c00:16:2450:51c0:93a1: not tested
    2600:9000:2501:5000:16:2450:51c0:93a1: not tested
    2600:9000:2501:ac00:16:2450:51c0:93a1: not tested
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.
- Nameservers have IPv6: 2 of 3 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): More than 5 redirects — stopped following.
    https://calendar.nyu.edu/ via 2600:9000:2501:9e00:16:2450:51c0:93a1 -> HTTP 302, certificate: valid
    https://www.google.com/calendar/hosted/nyu.edu via 2001:4860:4829:7700:: -> HTTP 302, certificate: valid
    https://calendar.google.com/calendar/hosted/nyu.edu via 2607:f8b0:4004:c1d::8a -> HTTP 302, certificate: valid
    https://calendar.google.com/calendar/a/nyu.edu via 2607:f8b0:4004:c1d::8a -> HTTP 302, certificate: valid
    https://www.google.com/a/nyu.edu/ServiceLogin?service=cl&continue=https://calendar.google.com/calendar/&followup=https://calendar.google.com/calendar/&osid=1&passive=1209600 via 2001:4860:4829:7700:: -> HTTP 302, certificate: valid
    https://accounts.google.com/samlredirect?continue=https%3A%2F%2Fcalendar.google.com%2Fcalendar%2F&sso_profile=inboundSamlSsoProfiles%2F03a14e4u3zlpreo via 2607:f8b0:4004:c06::54 -> HTTP 302, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/5HX2eJSIhS

Permanent link: aaaa.bot/r/5HX2eJSIhS · How we measure

Checked 2026-11-03 03:37:45 UTC. Full DNS report: dns.pizza/domain/calendar.nyu.edu · Age, certificate and blocklists: how.is/calendar.nyu.edu · JSON: /api/v1/calendar.nyu.edu