Yes — xn--7lqs8uilq.com has IPv6.

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

IPv6 readiness

Works over IPv6, with one gap: www doesn't fully work over IPv6.

Website over IPv6 xn--7lqs8uilq.com has an AAAA record and answers on it. ✓ 240e:978:6402::b461:c629 answers · 443	yes
www over IPv6 www.xn--7lqs8uilq.com 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.22.cn ✓ns2.22.cn ✓	yes

HTTPS over IPv6 · not part of the grade yet
The certificate served over IPv6 at 240e:978:6402::b461:c629 isn't valid for xn--7lqs8uilq.com: ERR_TLS_CERT_ALTNAME_INVALID.

https://xn--7lqs8uilq.com/ via 240e:978:6402::b461:c629 · ERR_TLS_CERT_ALTNAME_INVALID

problem

What's keeping xn--7lqs8uilq.com from an A

Add IPv6 for www.xn--7lqs8uilq.com
www.xn--7lqs8uilq.com 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--7lqs8uilq.com's AAAA record(s) for www. How to add an AAAA record
The certificate served over IPv6 is wrong
The certificate served over IPv6 at 240e:978:6402::b461:c629 isn't valid for xn--7lqs8uilq.com: ERR_TLS_CERT_ALTNAME_INVALID. Often the IPv6 address points at a different server (or an old one) than IPv4 does. Make sure 240e:978:6402::b461:c629 serves the same certificate as your IPv4 address.

Check again

xn--7lqs8uilq.com Has IPv6

Alias of	xn--7lqs8uilq.com.a.bdydns.com → opencdnkav6.jomodns.com
A (IPv4)	180.97.198.41
AAAA (IPv6)	240e:978:6402::b461:c629

www.xn--7lqs8uilq.com No address

A (IPv4)	none
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--7lqs8uilq.com
Measured 2026-10-30 16:04:21 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    180.97.198.41
AAAA (IPv6): 240e:978:6402::b461:c629
www AAAA:    none

Readiness grade B: Works over IPv6, with one gap: www doesn't fully work over IPv6.
- Website over IPv6: xn--7lqs8uilq.com has an AAAA record and answers on it.
    240e:978:6402::b461:c629: answers (TCP 443)
- www over IPv6: www.xn--7lqs8uilq.com 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).

HTTPS over IPv6 (not graded): The certificate served over IPv6 at 240e:978:6402::b461:c629 isn't valid for xn--7lqs8uilq.com: ERR_TLS_CERT_ALTNAME_INVALID.
    https://xn--7lqs8uilq.com/ via 240e:978:6402::b461:c629, certificate: ERR_TLS_CERT_ALTNAME_INVALID
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/li39bBElt0

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

Checked 2026-10-30 16:04:21 UTC. Full DNS report: dns.pizza/domain/xn--7lqs8uilq.com · JSON: /api/v1/xn--7lqs8uilq.com