Yes — xn--ngbcnmq.com has IPv6.

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

This is a saved measurement from 2026-11-14 22:11 UTC. Check xn--ngbcnmq.com live now

IPv6 readiness

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

Website over IPv6 xn--ngbcnmq.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3031::ac43:bf78 answers · 443✓ 2606:4700:3037::6815:41b9 answers · 443	yes
www over IPv6 www.xn--ngbcnmq.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3031::ac43:bf78 answers · 443✓ 2606:4700:3037::6815:41b9 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. eforward1.registrar-servers.com ✗eforward2.registrar-servers.com ✗eforward3.registrar-servers.com ✗eforward4.registrar-servers.com ✗eforward5.registrar-servers.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. autumn.ns.cloudflare.com ✓etienne.ns.cloudflare.com ✓	yes

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

https://xn--ngbcnmq.com/ via 2606:4700:3031::ac43:bf78 → 301https://xn--ngbcnmq.com/ar/ via 2606:4700:3031::ac43:bf78 → 200

works

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

Mail servers without IPv6
eforward1.registrar-servers.com, eforward2.registrar-servers.com, eforward3.registrar-servers.com, eforward4.registrar-servers.com, eforward5.registrar-servers.com have no AAAA record, so mail from IPv6-only servers can't reach them directly. If a provider runs your mail, that's their setting; if you run it, add AAAA records for these hosts.

Check again

xn--ngbcnmq.com Has IPv6

A (IPv4)	104.21.65.185 172.67.191.120
AAAA (IPv6)	2606:4700:3031::ac43:bf78 2606:4700:3037::6815:41b9

www.xn--ngbcnmq.com Has IPv6

A (IPv4)	104.21.65.185 172.67.191.120
AAAA (IPv6)	2606:4700:3031::ac43:bf78 2606:4700:3037::6815:41b9

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--ngbcnmq.com
Measured 2026-11-14 22:11:03 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    104.21.65.185, 172.67.191.120
AAAA (IPv6): 2606:4700:3031::ac43:bf78, 2606:4700:3037::6815:41b9
www AAAA:    2606:4700:3031::ac43:bf78, 2606:4700:3037::6815:41b9

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: xn--ngbcnmq.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3031::ac43:bf78: answers (TCP 443)
    2606:4700:3037::6815:41b9: answers (TCP 443)
- www over IPv6: www.xn--ngbcnmq.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3031::ac43:bf78: answers (TCP 443)
    2606:4700:3037::6815:41b9: 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 1 redirect: HTTP 200.
    https://xn--ngbcnmq.com/ via 2606:4700:3031::ac43:bf78 -> HTTP 301, certificate: valid
    https://xn--ngbcnmq.com/ar/ via 2606:4700:3031::ac43:bf78 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/ffJD9gI-vR

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

Checked 2026-11-14 22:11:03 UTC. Full DNS report: dns.pizza/domain/xn--ngbcnmq.com · Age, certificate and blocklists: how.is/xn--ngbcnmq.com · JSON: /api/v1/xn--ngbcnmq.com