cityxing.top publishes IPv6 but doesn't answer on it.

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

This is a saved measurement from 2026-11-01 03:32 UTC. Check cityxing.top live now

IPv6 readiness

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

Website over IPv6 cityxing.top has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb no answer	broken
www over IPv6 www.cityxing.top has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4. ✗ 240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb 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 3 of 3 nameservers checked have an AAAA record, so IPv6-only resolvers can look the domain up. ns1.dnsowl.com ✓ns2.dnsowl.com ✓ns3.dnsowl.com ✓	yes

What's keeping cityxing.top from an A

Fix or remove the AAAA record for cityxing.top
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.
Fix or remove the AAAA record for www.cityxing.top
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

cityxing.top Has IPv6

A (IPv4)	113.116.17.86
AAAA (IPv6)	240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb

www.cityxing.top Has IPv6

Alias of	cityxing.top
A (IPv4)	113.116.17.86
AAAA (IPv6)	240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb

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: cityxing.top
Measured 2026-11-01 03:32:44 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    113.116.17.86
AAAA (IPv6): 240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb
www AAAA:    240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb

Readiness grade F: Publishes IPv6 but doesn't answer on it — worse than having none.
- Website over IPv6: cityxing.top has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb: no answer
- www over IPv6: www.cityxing.top has an AAAA record, but nothing answered on ports 443 or 80. IPv6 visitors wait for a timeout before falling back to IPv4.
    240e:3b1:32a1:cb0:2584:a3d3:2ef2:95eb: no answer
- 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: 3 of 3 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/EsdP9FDTLb

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

Checked 2026-11-01 03:32:44 UTC. Full DNS report: dns.pizza/domain/cityxing.top · JSON: /api/v1/cityxing.top