About this tool
Enter a domain to audit its IPv6 readiness. The tool checks AAAA records for the apex and www hosts, verifies that nameservers and mail servers are reachable over IPv6, and produces a 0–4 score so you can see at a glance where the gaps are.
How to check IPv6 connectivity
- Open the page — the test runs automatically and probes IPv6 reachability.
- Review your IPv4 and IPv6 addresses side by side with reachability status.
- If IPv6 is missing or unreachable, the tool indicates whether the issue is OS-level, router-level or ISP-level.
- Use the output to decide whether to enable IPv6 on a server or adjust your network.
Common use cases
- Verifying IPv6 rollout before enabling AAAA records on a production domain.
- Diagnosing why a site serves IPv6 traffic slower than IPv4 for some users.
- Checking whether a mobile network provides IPv6 for a mobile-first launch.
- Confirming a VPN preserves IPv6 connectivity rather than forcing IPv4-only.
Frequently asked questions
Why do I only have IPv4?
Either your ISP has not rolled out IPv6, your router blocks it, or your OS has IPv6 disabled. The tool distinguishes between these by checking each layer.
Is IPv6 faster?
Not inherently. IPv6 can be slightly faster because it avoids NAT translation, but routing quality matters more — a poorly peered IPv6 path can be slower than a well-optimised IPv4 one.
Should I enable IPv6 on my server?
Yes if your target audience is increasingly mobile — mobile carriers roll out IPv6 aggressively. Dual-stack is the safe default.
Is my data logged?
No. The test runs in your browser and results are not stored.
Why IPv6 readiness matters
Mobile networks, datacentres, and many enterprise ISPs are IPv6-only or IPv6-first. If your nameservers or mail servers lack AAAA records, those users depend on NAT64 or DNS64 which is slower and can silently break mail delivery and DNS lookups. IPv6 parity is about reach and performance, not ideology.
- Apex and www AAAA check
- Nameserver AAAA coverage
- Mail server AAAA coverage
- 0–4 readiness score
- Powered by Cloudflare DNS-over-HTTPS
Free. No signup. Browser tools (subnet, JWT, password strength) run locally; lookup tools query public APIs (Cloudflare DoH, RDAP, certificate logs). Full per-tool breakdown at /methodology/.
Sources (3)
- Hinden, R., & Deering, S. (2006). IP Version 6 Addressing Architecture. RFC 4291, IETF.
- Mockapetris, P. (1987). Domain Names — Implementation and Specification. RFC 1035, IETF.
- Hoffman, P., & McManus, P. (2018). DNS Queries over HTTPS (DoH). RFC 8484, IETF.
These are the IETF RFCs, NIST publications, and W3C standards the tool implements or queries. Locate them on the IETF Datatracker (datatracker.ietf.org) or the official standards body.
By Marco B. ·