Yes — xn----htbcngbe7bgqc.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----htbcngbe7bgqc.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3033::6815:5c0d answers · 443✓ 2606:4700:3032::ac43:b87f answers · 443	yes
www over IPv6 www.xn----htbcngbe7bgqc.com has 2 IPv6 addresses and answers on every one we tested. ✓ 2606:4700:3032::ac43:b87f answers · 443✓ 2606:4700:3033::6815:5c0d answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. \208\187\209\131\208\186\209\129-\208\186\209\128\208\181\208\180\208\184\209\130.com ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. greg.ns.cloudflare.com ✓melissa.ns.cloudflare.com ✓	yes

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

https://xn----htbcngbe7bgqc.com/ via 2606:4700:3033::6815:5c0d → 200

works

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

Mail servers without IPv6
\208\187\209\131\208\186\209\129-\208\186\209\128\208\181\208\180\208\184\209\130.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----htbcngbe7bgqc.com Has IPv6

A (IPv4)	172.67.184.127 104.21.92.13
AAAA (IPv6)	2606:4700:3033::6815:5c0d 2606:4700:3032::ac43:b87f

www.xn----htbcngbe7bgqc.com Has IPv6

A (IPv4)	104.21.92.13 172.67.184.127
AAAA (IPv6)	2606:4700:3032::ac43:b87f 2606:4700:3033::6815:5c0d

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

A (IPv4):    172.67.184.127, 104.21.92.13
AAAA (IPv6): 2606:4700:3033::6815:5c0d, 2606:4700:3032::ac43:b87f
www AAAA:    2606:4700:3032::ac43:b87f, 2606:4700:3033::6815:5c0d

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: xn----htbcngbe7bgqc.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3033::6815:5c0d: answers (TCP 443)
    2606:4700:3032::ac43:b87f: answers (TCP 443)
- www over IPv6: www.xn----htbcngbe7bgqc.com has 2 IPv6 addresses and answers on every one we tested.
    2606:4700:3032::ac43:b87f: answers (TCP 443)
    2606:4700:3033::6815:5c0d: 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: HTTP 200.
    https://xn----htbcngbe7bgqc.com/ via 2606:4700:3033::6815:5c0d -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/D0Yqj7E7SV

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

Checked 2026-11-02 14:50:41 UTC. Full DNS report: dns.pizza/domain/xn----htbcngbe7bgqc.com · JSON: /api/v1/xn----htbcngbe7bgqc.com