Yes — m.tamu.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 m.tamu.edu has 3 IPv6 addresses and answers on every one we tested. ✓ 2600:1f14:2009:e703:a3f0:5a51:f084:1446 answers · 443✓ 2600:1f14:2009:e705:bac7:a06d:9a5d:6909 answers · 443✓ 2600:1f14:2009:e704:4e21:a5f4:b1d9:b434 answers · 443	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. ns1.tamu.edu ✗ns2.tamu.edu ✗ns3.tamu.edu ✗	no

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

https://m.tamu.edu/ via 2600:1f14:2009:e703:a3f0:5a51:f084:1446 → 302https://m.tamu.edu/_kgo_default/persona/index via 2600:1f14:2009:e703:a3f0:5a51:f084:1446 → 200

works

What's keeping m.tamu.edu from an A

Nameservers without IPv6
ns1.tamu.edu, ns2.tamu.edu, ns3.tamu.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

m.tamu.edu Has IPv6

Alias of	texasam-prod.modolabs.net → k8s-usw2auto202507251-b18432e02c-1807614767.us-west-2.elb.amazonaws.com
A (IPv4)	54.68.252.216 32.186.207.235 184.33.223.99
AAAA (IPv6)	2600:1f14:2009:e703:a3f0:5a51:f084:1446 2600:1f14:2009:e705:bac7:a06d:9a5d:6909 2600:1f14:2009:e704:4e21:a5f4:b1d9:b434

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

A (IPv4):    54.68.252.216, 32.186.207.235, 184.33.223.99
AAAA (IPv6): 2600:1f14:2009:e703:a3f0:5a51:f084:1446, 2600:1f14:2009:e705:bac7:a06d:9a5d:6909, 2600:1f14:2009:e704:4e21:a5f4:b1d9:b434

Readiness grade B: Works over IPv6, with one gap: its nameservers lack IPv6.
- Website over IPv6: m.tamu.edu has 3 IPv6 addresses and answers on every one we tested.
    2600:1f14:2009:e703:a3f0:5a51:f084:1446: answers (TCP 443)
    2600:1f14:2009:e705:bac7:a06d:9a5d:6909: answers (TCP 443)
    2600:1f14:2009:e704:4e21:a5f4:b1d9:b434: answers (TCP 443)
- 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): Loads over IPv6 with a valid certificate after 1 redirect: HTTP 200.
    https://m.tamu.edu/ via 2600:1f14:2009:e703:a3f0:5a51:f084:1446 -> HTTP 302, certificate: valid
    https://m.tamu.edu/_kgo_default/persona/index via 2600:1f14:2009:e703:a3f0:5a51:f084:1446 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/NvMJhx7c5-

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

Checked 2026-11-03 03:09:09 UTC. Full DNS report: dns.pizza/domain/m.tamu.edu · Age, certificate and blocklists: how.is/m.tamu.edu · JSON: /api/v1/m.tamu.edu