IPv6 Compatibility Test
Does your site actually work over IPv6?
Most IPv6 checkers stop at "does an AAAA record exist". That misses the failure that actually costs you visitors: an AAAA record pointing at an address that does not answer. Browsers on a dual-stack connection try IPv6 first, so a dead AAAA means every one of those visitors waits for a timeout before falling back — and IPv6-only visitors never get through at all. This tool resolves both families, opens a real connection to each, and checks whether your nameservers can be reached over IPv6.
Frequently asked questions
Is having no IPv6 a problem?
Not in itself — the overwhelming majority of the web is still reachable over IPv4, and a v4-only site works for almost everyone. It matters most on mobile networks, several of which are IPv6-only internally and depend on carrier translation to reach you, which adds latency and one more thing that can break.
Why is a broken AAAA worse than no AAAA?
Because clients prefer IPv6 when both are available. Publishing an AAAA is a promise that the address answers; if it does not, every dual-stack visitor pays a connection timeout before retrying over IPv4, and that happens on each new connection, not once per visit.
Why do you check my nameservers?
DNS comes first. If none of your nameservers has an AAAA record, a resolver running on an IPv6-only network cannot look your domain up at all — so the AAAA on your web server never even gets read. It is a common gap, because the two are usually configured by different people.
What if the test says IPv6 could not be tested?
That means the machine running the check had no IPv6 route of its own at the time, so no connection could be attempted. We report that as untested rather than failed, because calling your working AAAA record broken would be worse than saying nothing.