Yes — assets.tcu.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 assets.tcu.edu has 4 IPv6 addresses and answers on every one we tested (4 more not tested). ✓ 2600:9000:2501:ba00:11:9f39:cac0:93a1 answers · 443✓ 2600:9000:2501:6600:11:9f39:cac0:93a1 answers · 443✓ 2600:9000:2501:1e00:11:9f39:cac0:93a1 answers · 443✓ 2600:9000:2501:3200:11:9f39:cac0:93a1 answers · 443– 2600:9000:2501:c800:11:9f39:cac0:93a1 not tested– 2600:9000:2501:8000:11:9f39:cac0:93a1 not tested– 2600:9000:2501:4400:11:9f39:cac0:93a1 not tested– 2600:9000:2501:d600:11:9f39:cac0: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 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns1.tcu.edu ✗ns99.tcu.edu ✗	no

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

https://assets.tcu.edu/ via 2600:9000:2501:ba00:11:9f39:cac0:93a1 → 200

works

What's keeping assets.tcu.edu from an A

Nameservers without IPv6
ns1.tcu.edu, ns99.tcu.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

assets.tcu.edu Has IPv6

Alias of	d15kvublqksy0b.cloudfront.net
A (IPv4)	18.154.227.11 18.154.227.9 18.154.227.87 18.154.227.21
AAAA (IPv6)	2600:9000:2501:ba00:11:9f39:cac0:93a1 2600:9000:2501:6600:11:9f39:cac0:93a1 2600:9000:2501:1e00:11:9f39:cac0:93a1 2600:9000:2501:3200:11:9f39:cac0:93a1 2600:9000:2501:c800:11:9f39:cac0:93a1 2600:9000:2501:8000:11:9f39:cac0:93a1 2600:9000:2501:4400:11:9f39:cac0:93a1 2600:9000:2501:d600:11:9f39:cac0: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: assets.tcu.edu
Measured 2026-11-03 12:07:17 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    18.154.227.11, 18.154.227.9, 18.154.227.87, 18.154.227.21
AAAA (IPv6): 2600:9000:2501:ba00:11:9f39:cac0:93a1, 2600:9000:2501:6600:11:9f39:cac0:93a1, 2600:9000:2501:1e00:11:9f39:cac0:93a1, 2600:9000:2501:3200:11:9f39:cac0:93a1, 2600:9000:2501:c800:11:9f39:cac0:93a1, 2600:9000:2501:8000:11:9f39:cac0:93a1, 2600:9000:2501:4400:11:9f39:cac0:93a1, 2600:9000:2501:d600:11:9f39:cac0:93a1

Readiness grade B: Works over IPv6, with one gap: its nameservers lack IPv6.
- Website over IPv6: assets.tcu.edu has 4 IPv6 addresses and answers on every one we tested (4 more not tested).
    2600:9000:2501:ba00:11:9f39:cac0:93a1: answers (TCP 443)
    2600:9000:2501:6600:11:9f39:cac0:93a1: answers (TCP 443)
    2600:9000:2501:1e00:11:9f39:cac0:93a1: answers (TCP 443)
    2600:9000:2501:3200:11:9f39:cac0:93a1: answers (TCP 443)
    2600:9000:2501:c800:11:9f39:cac0:93a1: not tested
    2600:9000:2501:8000:11:9f39:cac0:93a1: not tested
    2600:9000:2501:4400:11:9f39:cac0:93a1: not tested
    2600:9000:2501:d600:11:9f39:cac0: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: 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: HTTP 200.
    https://assets.tcu.edu/ via 2600:9000:2501:ba00:11:9f39:cac0:93a1 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/RGqNpo_47a

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

Checked 2026-11-03 12:07:17 UTC. Full DNS report: dns.pizza/domain/assets.tcu.edu · Age, certificate and blocklists: how.is/assets.tcu.edu · JSON: /api/v1/assets.tcu.edu