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

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

This is a saved measurement from 2026-11-02 18:11 UTC. Check xn--80ab8a1ab5e.xn--80asehdb live now

F
IPv6 readiness
Publishes IPv6 but doesn't answer on it — worse than having none.
Website over IPv6
xn--80ab8a1ab5e.xn--80asehdb 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
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--80asehdb from an A

  1. Fix or remove the AAAA record for xn--80ab8a1ab5e.xn--80asehdb
    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.

Check again

xn--80ab8a1ab5e.xn--80asehdb  Has IPv6

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

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

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

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