Yes — xn--pokdfense-d4ab.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--pokdfense-d4ab.com has 4 IPv6 addresses and answers on every one we tested. ✓ 2606:50c0:8000::153 answers · 443✓ 2606:50c0:8001::153 answers · 443✓ 2606:50c0:8002::153 answers · 443✓ 2606:50c0:8003::153 answers · 443	yes
www over IPv6 www.xn--pokdfense-d4ab.com has 4 IPv6 addresses and answers on every one we tested. ✓ 2606:50c0:8003::153 answers · 443✓ 2606:50c0:8000::153 answers · 443✓ 2606:50c0:8001::153 answers · 443✓ 2606:50c0:8002::153 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx1.mail.ovh.net ✗mx2.mail.ovh.net ✗mx3.mail.ovh.net ✗	no
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns103.ovh.net ✓dns103.ovh.net ✓	yes

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

https://xn--pokdfense-d4ab.com/ via 2606:50c0:8000::153 → 200

works

What's keeping xn--pokdfense-d4ab.com from an A

Mail servers without IPv6
mx1.mail.ovh.net, mx2.mail.ovh.net, mx3.mail.ovh.net 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--pokdfense-d4ab.com Has IPv6

A (IPv4)	185.199.108.153 185.199.109.153 185.199.110.153 185.199.111.153
AAAA (IPv6)	2606:50c0:8000::153 2606:50c0:8001::153 2606:50c0:8002::153 2606:50c0:8003::153

www.xn--pokdfense-d4ab.com Has IPv6

Alias of	kyfudy.github.io
A (IPv4)	185.199.108.153 185.199.109.153 185.199.110.153 185.199.111.153
AAAA (IPv6)	2606:50c0:8003::153 2606:50c0:8000::153 2606:50c0:8001::153 2606:50c0:8002::153

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--pokdfense-d4ab.com
Measured 2026-10-30 19:50:55 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    185.199.108.153, 185.199.109.153, 185.199.110.153, 185.199.111.153
AAAA (IPv6): 2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153, 2606:50c0:8003::153
www AAAA:    2606:50c0:8003::153, 2606:50c0:8000::153, 2606:50c0:8001::153, 2606:50c0:8002::153

Readiness grade B: Works over IPv6, with one gap: its mail servers lack IPv6.
- Website over IPv6: xn--pokdfense-d4ab.com has 4 IPv6 addresses and answers on every one we tested.
    2606:50c0:8000::153: answers (TCP 443)
    2606:50c0:8001::153: answers (TCP 443)
    2606:50c0:8002::153: answers (TCP 443)
    2606:50c0:8003::153: answers (TCP 443)
- www over IPv6: www.xn--pokdfense-d4ab.com has 4 IPv6 addresses and answers on every one we tested.
    2606:50c0:8003::153: answers (TCP 443)
    2606:50c0:8000::153: answers (TCP 443)
    2606:50c0:8001::153: answers (TCP 443)
    2606:50c0:8002::153: 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--pokdfense-d4ab.com/ via 2606:50c0:8000::153 -> HTTP 200, certificate: valid
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/kfwJgbD-NL

Permanent link: aaaa.bot/r/kfwJgbD-NL · How we measure

Checked 2026-10-30 19:50:55 UTC. Full DNS report: dns.pizza/domain/xn--pokdfense-d4ab.com · JSON: /api/v1/xn--pokdfense-d4ab.com