No — xn--tsrr36hwng.ink is IPv4 only.

Has an IPv4 address but no IPv6 (AAAA) record. IPv6-only visitors can't reach it directly.

Measured 2026-11-01 08:32 UTC. We reuse a result for up to a week, so we aren't testing the same site over and over. Check xn--tsrr36hwng.ink now

D
IPv6 readiness
The website has no IPv6.
Website over IPv6
xn--tsrr36hwng.ink 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 no AAAA record.		no
Nameservers have IPv6
2 of 2 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up.
ns2.myhostadmin.net ✓ns1.myhostadmin.net ✓
yes

First measured 2026-11-01; last confirmed 2026-11-01.

What's keeping xn--tsrr36hwng.ink from an A

  1. xn--tsrr36hwng.ink is an alias of aqsmjvy2.cdnfly8dns123.com, which has no IPv6
    xn--tsrr36hwng.ink is a CNAME, so it can't also have its own AAAA record. Ask whoever runs aqsmjvy2.cdnfly8dns123.com to enable IPv6 there — or replace the alias with the A and AAAA records they give you. Why some hosts don't offer IPv6
  2. Mail servers without IPv6
    Your domain's mail goes to its own address, which has no AAAA record.

Check again

xn--tsrr36hwng.ink  IPv4 only

Alias ofw2jp9csg.cdnfly8dns123.com → aqsmjvy2.cdnfly8dns123.com
A (IPv4)61.111.252.187
AAAA (IPv6)none

What this means

Visitors on IPv6-only networks (many mobile carriers) can still reach it, but only through a translator their carrier runs (NAT64). The site itself has no IPv6 address — and you can't make one up from the IPv4. Why some hosts don't offer it

Copy the evidence — a citation-ready record of this measurement

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

Checked 2026-11-01 08:32:29 UTC. Full DNS report: dns.pizza/domain/xn--tsrr36hwng.ink · JSON: /api/v1/xn--tsrr36hwng.ink