Yes — arizona.edu has IPv6.

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

Measured 2026-11-02 17:38 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check arizona.edu now

IPv6 readiness

Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.

Website over IPv6 arizona.edu has 2 IPv6 addresses and answers on every one we tested. ✓ 2620:12a:8000::4 answers · 443✓ 2620:12a:8001::4 answers · 443	yes
www over IPv6 www.arizona.edu has 2 IPv6 addresses and answers on every one we tested. ✓ 2620:12a:8000::4 answers · 443✓ 2620:12a:8001::4 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. usb-smtp-inbound-1.mimecast.com ✗usb-smtp-inbound-2.mimecast.com ✗	no
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns1.arizona.edu ✗ns2.arizona.edu ✗ns3.arizona.edu ✗ns4.arizona.edu ✗	no

First measured 2026-11-02; last confirmed 2026-11-02.

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.

https://arizona.edu/ via 2620:12a:8000::4 → 301https://www.arizona.edu/ via 2620:12a:8000::4 → 200

works

What's keeping arizona.edu from an A

Mail servers without IPv6
usb-smtp-inbound-1.mimecast.com, usb-smtp-inbound-2.mimecast.com have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.
Nameservers without IPv6
ns1.arizona.edu, ns2.arizona.edu, ns3.arizona.edu, ns4.arizona.edu all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

arizona.edu Has IPv6

A (IPv4)	23.185.0.4
AAAA (IPv6)	2620:12a:8000::4 2620:12a:8001::4

www.arizona.edu Has IPv6

A (IPv4)	23.185.0.4
AAAA (IPv6)	2620:12a:8000::4 2620:12a:8001::4

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: arizona.edu
Measured 2026-11-02 17:38:33 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    23.185.0.4
AAAA (IPv6): 2620:12a:8000::4, 2620:12a:8001::4
www AAAA:    2620:12a:8000::4, 2620:12a:8001::4

Readiness grade C: Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.
- Website over IPv6: arizona.edu has 2 IPv6 addresses and answers on every one we tested.
    2620:12a:8000::4: answers (TCP 443)
    2620:12a:8001::4: answers (TCP 443)
- www over IPv6: www.arizona.edu has 2 IPv6 addresses and answers on every one we tested.
    2620:12a:8000::4: answers (TCP 443)
    2620:12a:8001::4: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

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

HTTPS over IPv6 (not graded): Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.
    https://arizona.edu/ via 2620:12a:8000::4 -> HTTP 301, certificate: valid
    https://www.arizona.edu/ via 2620:12a:8000::4 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/aewzTBi9SH

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

Checked 2026-11-02 17:38:33 UTC. Full DNS report: dns.pizza/domain/arizona.edu · Age, certificate and blocklists: how.is/arizona.edu · JSON: /api/v1/arizona.edu