Yes — xn----ftbihbaak3acc8ae.store has IPv6.

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

IPv6 readiness

Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.

Website over IPv6 xn----ftbihbaak3acc8ae.store has an AAAA record and answers on it. ✓ 2a00:f940:2:2:1:1:0:191 answers · 443	yes
www over IPv6 www.xn----ftbihbaak3acc8ae.store has an AAAA record and answers on it. ✓ 2a00:f940:2:2:1:1:0:191 answers · 443	yes
Mail servers (MX) have IPv6 None of the mail servers has an AAAA record. mx1.hosting.reg.ru ✗mx2.hosting.reg.ru ✗	no
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:191 isn't valid for xn----ftbihbaak3acc8ae.store: DEPTH_ZERO_SELF_SIGNED_CERT.

https://xn----ftbihbaak3acc8ae.store/ via 2a00:f940:2:2:1:1:0:191 · DEPTH_ZERO_SELF_SIGNED_CERT

problem

What's keeping xn----ftbihbaak3acc8ae.store from an A

The certificate served over IPv6 is wrong
The certificate served over IPv6 at 2a00:f940:2:2:1:1:0:191 isn't valid for xn----ftbihbaak3acc8ae.store: 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:191 serves the same certificate as your IPv4 address.
Mail servers without IPv6
mx1.hosting.reg.ru, mx2.hosting.reg.ru 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.
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----ftbihbaak3acc8ae.store Has IPv6

A (IPv4)	31.31.196.193
AAAA (IPv6)	2a00:f940:2:2:1:1:0:191

www.xn----ftbihbaak3acc8ae.store Has IPv6

A (IPv4)	31.31.196.193
AAAA (IPv6)	2a00:f940:2:2:1:1:0:191

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----ftbihbaak3acc8ae.store
Measured 2026-10-31 15:00:00 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    31.31.196.193
AAAA (IPv6): 2a00:f940:2:2:1:1:0:191
www AAAA:    2a00:f940:2:2:1:1:0:191

Readiness grade C: Works over IPv6, with gaps: its mail servers lack IPv6; its nameservers lack IPv6.
- Website over IPv6: xn----ftbihbaak3acc8ae.store has an AAAA record and answers on it.
    2a00:f940:2:2:1:1:0:191: answers (TCP 443)
- www over IPv6: www.xn----ftbihbaak3acc8ae.store has an AAAA record and answers on it.
    2a00:f940:2:2:1:1:0:191: answers (TCP 443)
- Mail servers (MX) have IPv6: None of the mail servers 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:191 isn't valid for xn----ftbihbaak3acc8ae.store: DEPTH_ZERO_SELF_SIGNED_CERT.
    https://xn----ftbihbaak3acc8ae.store/ via 2a00:f940:2:2:1:1:0:191, certificate: DEPTH_ZERO_SELF_SIGNED_CERT
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/JpTucpU3ij

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

Checked 2026-10-31 15:00:00 UTC. Full DNS report: dns.pizza/domain/xn----ftbihbaak3acc8ae.store · JSON: /api/v1/xn----ftbihbaak3acc8ae.store