Yes — xn--n1ae8d0v.com 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 xn--n1ae8d0v.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3030::ac43:abdc answers · 443✓ 2606:4700:3033::6815:1dd6 answers · 443	yes
www over IPv6 www.xn--n1ae8d0v.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3033::6815:1dd6 answers · 443✓ 2606:4700:3030::ac43:abdc answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx.postfern.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. elmo.ns.cloudflare.com ✓rose.ns.cloudflare.com ✓	yes

HTTPS over IPv6 · not part of the grade yet
Redirects to ihop.com, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.

https://xn--n1ae8d0v.com/ via 2606:4700:3030::ac43:abdc → 302https://ihop.com/ · redirects to ihop.com, which has no IPv6 address

problem

What's keeping xn--n1ae8d0v.com from an A

A redirect leads off IPv6
Redirects to ihop.com, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all. Give the redirect target IPv6 too, or redirect somewhere that has it.
Mail servers without IPv6
mx.postfern.com 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

xn--n1ae8d0v.com Has IPv6

A (IPv4)	104.21.29.214 172.67.171.220
AAAA (IPv6)	2606:4700:3030::ac43:abdc 2606:4700:3033::6815:1dd6

www.xn--n1ae8d0v.com Has IPv6

A (IPv4)	104.21.29.214 172.67.171.220
AAAA (IPv6)	2606:4700:3033::6815:1dd6 2606:4700:3030::ac43:abdc

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: xn--n1ae8d0v.com
Measured 2026-11-10 00:08:16 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.29.214, 172.67.171.220
AAAA (IPv6): 2606:4700:3030::ac43:abdc, 2606:4700:3033::6815:1dd6
www AAAA:    2606:4700:3033::6815:1dd6, 2606:4700:3030::ac43:abdc

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: xn--n1ae8d0v.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3030::ac43:abdc: answers (TCP 443)
    2606:4700:3033::6815:1dd6: answers (TCP 443)
- www over IPv6: www.xn--n1ae8d0v.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3033::6815:1dd6: answers (TCP 443)
    2606:4700:3030::ac43:abdc: 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): Redirects to ihop.com, which has no IPv6 address — so IPv6 visitors end up needing IPv4 after all.
    https://xn--n1ae8d0v.com/ via 2606:4700:3030::ac43:abdc -> HTTP 302, certificate: valid
    https://ihop.com/ (redirects to ihop.com, which has no IPv6 address)
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/D8s9OXH4Wc

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

Checked 2026-11-10 00:08:16 UTC. Full DNS report: dns.pizza/domain/xn--n1ae8d0v.com · Age, certificate and blocklists: how.is/xn--n1ae8d0v.com · JSON: /api/v1/xn--n1ae8d0v.com