Yes — xn--p1aecc.com has IPv6.

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

IPv6 readiness

Works over IPv6, with one gap: its nameservers lack IPv6.

Website over IPv6 xn--p1aecc.com has an AAAA record and answers on it. ✓ 2a00:f940:2:2:1:1:0:262 answers · 443	yes
www over IPv6 www.xn--p1aecc.com has an AAAA record and answers on it. ✓ 2a00:f940:2:2:1:1:0:262 answers · 443	yes
Mail servers (MX) have IPv6 Every mail server has an AAAA record. mx.yandex.net ✓	yes
Nameservers have IPv6 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns1.hosting.reg.ru ✗ns2.hosting.reg.ru ✗	no

HTTPS over IPv6 · not part of the grade yet
The certificate served over IPv6 at 2a00:f940:2:2:1:1:0:262 isn't valid for xn--p1aecc.com: DEPTH_ZERO_SELF_SIGNED_CERT.

https://xn--p1aecc.com/ via 2a00:f940:2:2:1:1:0:262 · DEPTH_ZERO_SELF_SIGNED_CERT

problem

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

The certificate served over IPv6 is wrong
The certificate served over IPv6 at 2a00:f940:2:2:1:1:0:262 isn't valid for xn--p1aecc.com: DEPTH_ZERO_SELF_SIGNED_CERT. Often the IPv6 address points at a different server (or an old one) than IPv4 does. Make sure 2a00:f940:2:2:1:1:0:262 serves the same certificate as your IPv4 address.
Nameservers without IPv6
ns1.hosting.reg.ru, ns2.hosting.reg.ru all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

xn--p1aecc.com Has IPv6

A (IPv4)	31.31.196.9
AAAA (IPv6)	2a00:f940:2:2:1:1:0:262

www.xn--p1aecc.com Has IPv6

A (IPv4)	31.31.196.9
AAAA (IPv6)	2a00:f940:2:2:1:1:0:262

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

A (IPv4):    31.31.196.9
AAAA (IPv6): 2a00:f940:2:2:1:1:0:262
www AAAA:    2a00:f940:2:2:1:1:0:262

Readiness grade B: Works over IPv6, with one gap: its nameservers lack IPv6.
- Website over IPv6: xn--p1aecc.com has an AAAA record and answers on it.
    2a00:f940:2:2:1:1:0:262: answers (TCP 443)
- www over IPv6: www.xn--p1aecc.com has an AAAA record and answers on it.
    2a00:f940:2:2:1:1:0:262: answers (TCP 443)
- Mail servers (MX) have IPv6: Every mail server has an AAAA record.
- Nameservers have IPv6: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): The certificate served over IPv6 at 2a00:f940:2:2:1:1:0:262 isn't valid for xn--p1aecc.com: DEPTH_ZERO_SELF_SIGNED_CERT.
    https://xn--p1aecc.com/ via 2a00:f940:2:2:1:1:0:262, certificate: DEPTH_ZERO_SELF_SIGNED_CERT
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/6UdDu6ULc1

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

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