Yes — clients-qba.site has IPv6.

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

This is a saved measurement from 2026-11-01 13:10 UTC. Check clients-qba.site live now

IPv6 readiness

Works over IPv6, with one gap: its nameservers lack IPv6.

Website over IPv6 clients-qba.site has an AAAA record and answers on it. ✓ 2a00:f940:2:2:1:1:0:256 answers · 443	yes
www over IPv6 www.clients-qba.site has an AAAA record and answers on it. ✓ 2a00:f940:2:2:1:1:0:256 answers · 443	yes
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 No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS. ns1.hosting.reg.ru ✗ns2.hosting.reg.ru ✗	no

HTTPS over IPv6 · not part of the grade yet
The certificate served over IPv6 at 2a00:f940:2:2:1:1:0:256 isn't valid for clients-qba.site: ERR_TLS_CERT_ALTNAME_INVALID.

https://clients-qba.site/ via 2a00:f940:2:2:1:1:0:256 · ERR_TLS_CERT_ALTNAME_INVALID

problem

What's keeping clients-qba.site from an A

The certificate served over IPv6 is wrong
The certificate served over IPv6 at 2a00:f940:2:2:1:1:0:256 isn't valid for clients-qba.site: ERR_TLS_CERT_ALTNAME_INVALID. Often the IPv6 address points at a different server (or an old one) than IPv4 does. Make sure 2a00:f940:2:2:1:1:0:256 serves the same certificate as your IPv4 address.
Nameservers without IPv6
ns1.hosting.reg.ru, ns2.hosting.reg.ru all have no AAAA record, so a resolver that only speaks IPv6 can't look your domain up. Most DNS providers offer IPv6 nameservers; ask yours, or move DNS to one that does.

Check again

clients-qba.site Has IPv6

A (IPv4)	31.31.196.17
AAAA (IPv6)	2a00:f940:2:2:1:1:0:256

www.clients-qba.site Has IPv6

A (IPv4)	31.31.196.17
AAAA (IPv6)	2a00:f940:2:2:1:1:0:256

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: clients-qba.site
Measured 2026-11-01 13:10:51 UTC by aaaa.bot (one server on Fly.io, region iad)

A (IPv4):    31.31.196.17
AAAA (IPv6): 2a00:f940:2:2:1:1:0:256
www AAAA:    2a00:f940:2:2:1:1:0:256

Readiness grade B: Works over IPv6, with one gap: its nameservers lack IPv6.
- Website over IPv6: clients-qba.site has an AAAA record and answers on it.
    2a00:f940:2:2:1:1:0:256: answers (TCP 443)
- www over IPv6: www.clients-qba.site has an AAAA record and answers on it.
    2a00:f940:2:2:1:1:0:256: answers (TCP 443)
- 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: No nameserver has an AAAA record — an IPv6-only resolver can't reach this domain's DNS.

Reachability = a TCP connection opened on port 443 (or 80).

HTTPS over IPv6 (not graded): The certificate served over IPv6 at 2a00:f940:2:2:1:1:0:256 isn't valid for clients-qba.site: ERR_TLS_CERT_ALTNAME_INVALID.
    https://clients-qba.site/ via 2a00:f940:2:2:1:1:0:256, certificate: ERR_TLS_CERT_ALTNAME_INVALID
DNS answers via DNS-over-HTTPS (Cloudflare). Method: https://aaaa.bot/method
Permanent link: https://aaaa.bot/r/BYG-gRHckJ

Permanent link: aaaa.bot/r/BYG-gRHckJ · How we measure

Checked 2026-11-01 13:10:51 UTC. Full DNS report: dns.pizza/domain/clients-qba.site · JSON: /api/v1/clients-qba.site