Yes — joinamplixitytracker.cfd has IPv6.

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

Measured 2026-11-03 02:13 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check joinamplixitytracker.cfd now

B
IPv6 readiness
Works over IPv6, with one gap: its mail servers lack IPv6.
Website over IPv6
joinamplixitytracker.cfd has 2 IPv6 addresses and answers on every one we tested.
✓ 2606:4700:3031::ac43:954c answers · 443✓ 2606:4700:3030::6815:4fe5 answers · 443
yes
Mail servers (MX) have IPv6
None of the mail servers has an AAAA record.
_dc-mx.7baa1cc03d6f.joinamplixitytracker.cfd ✗
no
Nameservers have IPv6
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
clark.ns.cloudflare.com ✓maya.ns.cloudflare.com ✓
yes

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

HTTPS over IPv6 · not part of the grade yet
Loads over IPv6 with a valid certificate: HTTP 403.
https://joinamplixitytracker.cfd/ via 2606:4700:3031::ac43:954c → 403
works
 Load joinamplixitytracker.cfd over IPv6 from up to six other places — a second opinion.

What's keeping joinamplixitytracker.cfd from an A

  1. Mail servers without IPv6
    _dc-mx.7baa1cc03d6f.joinamplixitytracker.cfd 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

joinamplixitytracker.cfd  Has IPv6

A (IPv4)104.21.79.229
172.67.149.76
AAAA (IPv6)2606:4700:3031::ac43:954c
2606:4700:3030::6815:4fe5

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

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

Checked 2026-11-03 02:13:04 UTC. Full DNS report: dns.pizza/domain/joinamplixitytracker.cfd · Age, certificate and blocklists: how.is/joinamplixitytracker.cfd · JSON: /api/v1/joinamplixitytracker.cfd