xn--80ab8a1ab5e.xn--80aswg publishes IPv6 but doesn't answer on it.

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

IPv6 readiness

Publishes IPv6 but doesn't answer on it — worse than having none.

Website over IPv6 xn--80ab8a1ab5e.xn--80aswg has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 2a03:6f00:1::5c35:60c9 no answer	broken
www over IPv6 www.xn--80ab8a1ab5e.xn--80aswg has no AAAA record.	no
Mail servers (MX) have IPv6 No MX records, so mail goes to the domain's own address (implicit MX). It has an AAAA record.	yes
Nameservers have IPv6 2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns1.reg.ru ✓ns2.reg.ru ✓	yes

What's keeping xn--80ab8a1ab5e.xn--80aswg from an A

Fix or remove the AAAA record for xn--80ab8a1ab5e.xn--80aswg
Something published an IPv6 address but nothing answers on it, so IPv6 visitors wait for a timeout first. Either make the server listen on IPv6 (and allow ports 443/80 through its firewall), or delete the AAAA record until it does.
Add IPv6 for www.xn--80ab8a1ab5e.xn--80aswg
www.xn--80ab8a1ab5e.xn--80aswg has no AAAA record. Get www's IPv6 address from whoever hosts www and add it as an AAAA record. If the same server already serves both names (and its certificate covers www), you can reuse xn--80ab8a1ab5e.xn--80aswg's AAAA record(s) for www. How to add an AAAA record

Check again

xn--80ab8a1ab5e.xn--80aswg Has IPv6

A (IPv4)	92.53.96.201
AAAA (IPv6)	2a03:6f00:1::5c35:60c9

www.xn--80ab8a1ab5e.xn--80aswg IPv4 only

A (IPv4)	92.53.96.201
AAAA (IPv6)	none

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--80ab8a1ab5e.xn--80aswg
Measured 2026-11-03 02:55:58 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    92.53.96.201
AAAA (IPv6): 2a03:6f00:1::5c35:60c9
www AAAA:    none

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: xn--80ab8a1ab5e.xn--80aswg has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    2a03:6f00:1::5c35:60c9: no answer
- www over IPv6: www.xn--80ab8a1ab5e.xn--80aswg has no AAAA record.
- Mail servers (MX) have IPv6: No MX records, so mail goes to the domain's own address (implicit MX). It 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).
No TLS or HTTP request was made.
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/9XvcZA7hQZ

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

Checked 2026-11-03 02:55:58 UTC. Full DNS report: dns.pizza/domain/xn--80ab8a1ab5e.xn--80aswg · Age, certificate and blocklists: how.is/xn--80ab8a1ab5e.xn--80aswg · JSON: /api/v1/xn--80ab8a1ab5e.xn--80aswg