Yes — autodiscover.uga.edu has IPv6.

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

IPv6 readiness

Works over IPv6, with one gap: its nameservers lack IPv6.

Website over IPv6 autodiscover.uga.edu has 4 IPv6 addresses and answers on every one we tested (4 more not tested). ✓ 2603:1036:302:415d::8 answers · 80✓ 2603:1036:302:415e::8 answers · 80✓ 2603:1036:302:4823::8 answers · 80✓ 2603:1036:302:4840::8 answers · 80– 2603:1036:302:4846::8 not tested– 2603:1036:302:505a::8 not tested– 2603:1036:302:505c::8 not tested– 2603:1036:302:505d::8 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 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. dns2.uga.edu ✗dns3.uga.edu ✗	no

HTTPS over IPv6 · not part of the grade yet
autodiscover.uga.edu didn't complete an HTTPS request over IPv6 (ECONNREFUSED).

https://autodiscover.uga.edu/ via 2603:1036:302:415d::8 · ECONNREFUSED

What's keeping autodiscover.uga.edu from an A

Nameservers without IPv6
dns2.uga.edu, dns3.uga.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

autodiscover.uga.edu Has IPv6

Alias of	autodiscover.outlook.com → autodiscover.outlook.cloud.microsoft → acdcatm.autodiscover.mira.tm.svc.cloud.microsoft → atm.autodiscover.mira.tm.svc.cloud.microsoft
A (IPv4)	40.104.46.56 40.104.46.88 52.96.88.120 52.96.109.168 52.96.109.200 52.96.111.120 52.96.183.40 52.96.242.24
AAAA (IPv6)	2603:1036:302:415d::8 2603:1036:302:415e::8 2603:1036:302:4823::8 2603:1036:302:4840::8 2603:1036:302:4846::8 2603:1036:302:505a::8 2603:1036:302:505c::8 2603:1036:302:505d::8

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: autodiscover.uga.edu
Measured 2026-11-03 03:24:53 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    40.104.46.56, 40.104.46.88, 52.96.88.120, 52.96.109.168, 52.96.109.200, 52.96.111.120, 52.96.183.40, 52.96.242.24
AAAA (IPv6): 2603:1036:302:415d::8, 2603:1036:302:415e::8, 2603:1036:302:4823::8, 2603:1036:302:4840::8, 2603:1036:302:4846::8, 2603:1036:302:505a::8, 2603:1036:302:505c::8, 2603:1036:302:505d::8

Readiness grade B: Works over IPv6, with one gap: its nameservers lack IPv6.
- Website over IPv6: autodiscover.uga.edu has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
    2603:1036:302:415d::8: answers (TCP 80)
    2603:1036:302:415e::8: answers (TCP 80)
    2603:1036:302:4823::8: answers (TCP 80)
    2603:1036:302:4840::8: answers (TCP 80)
    2603:1036:302:4846::8: not tested
    2603:1036:302:505a::8: not tested
    2603:1036:302:505c::8: not tested
    2603:1036:302:505d::8: 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: 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): autodiscover.uga.edu didn't complete an HTTPS request over IPv6 (ECONNREFUSED).
    https://autodiscover.uga.edu/ via 2603:1036:302:415d::8 (ECONNREFUSED)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/SidpmzPH2w

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

Checked 2026-11-03 03:24:53 UTC. Full DNS report: dns.pizza/domain/autodiscover.uga.edu · Age, certificate and blocklists: how.is/autodiscover.uga.edu · JSON: /api/v1/autodiscover.uga.edu