Yes — teamg37.org has IPv6.

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

IPv6 readiness

Works over IPv6, with one gap: its mail servers lack IPv6.

Website over IPv6 teamg37.org has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3032::ac43:c695 answers · 443✓ 2606:4700:3032::6815:d40 answers · 443	yes
www over IPv6 www.teamg37.org has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3032::ac43:c695 answers · 443✓ 2606:4700:3032::6815:d40 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. _dc-mx.ea24b3d8d78c.teamg37.org ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. jaime.ns.cloudflare.com ✓kim.ns.cloudflare.com ✓	yes

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

https://teamg37.org/ via 2606:4700:3032::ac43:c695 → 302https://teamg37.org/dashboard.php via 2606:4700:3032::ac43:c695 → 302https://teamg37.org/login.php via 2606:4700:3032::ac43:c695 → 200

works

What's keeping teamg37.org from an A

Mail servers without IPv6
_dc-mx.ea24b3d8d78c.teamg37.org has no AAAA record, so mail from IPv6-only servers can't reach it directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

teamg37.org Has IPv6

A (IPv4)	104.21.13.64 172.67.198.149
AAAA (IPv6)	2606:4700:3032::ac43:c695 2606:4700:3032::6815:d40

www.teamg37.org Has IPv6

A (IPv4)	172.67.198.149 104.21.13.64
AAAA (IPv6)	2606:4700:3032::ac43:c695 2606:4700:3032::6815:d40

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: teamg37.org
Measured 2026-11-09 00:42:54 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.13.64, 172.67.198.149
AAAA (IPv6): 2606:4700:3032::ac43:c695, 2606:4700:3032::6815:d40
www AAAA:    2606:4700:3032::ac43:c695, 2606:4700:3032::6815:d40

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: teamg37.org has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3032::ac43:c695: answers (TCP 443)
    2606:4700:3032::6815:d40: answers (TCP 443)
- www over IPv6: www.teamg37.org has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3032::ac43:c695: answers (TCP 443)
    2606:4700:3032::6815:d40: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers has an AAAA record.
- Nameservers have IPv6: 2 of 2 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): Loads over IPv6 with a valid certificate after 2 redirects: HTTP 200.
    https://teamg37.org/ via 2606:4700:3032::ac43:c695 -> HTTP 302, certificate: valid
    https://teamg37.org/dashboard.php via 2606:4700:3032::ac43:c695 -> HTTP 302, certificate: valid
    https://teamg37.org/login.php via 2606:4700:3032::ac43:c695 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/rOg2XqJwgc

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

Checked 2026-11-09 00:42:54 UTC. Full DNS report: dns.pizza/domain/teamg37.org · Age, certificate and blocklists: how.is/teamg37.org · JSON: /api/v1/teamg37.org