IPv6 is the newer internet addressing system, and many mobile and home networks now use it first. This test checks whether a domain is ready for visitors on those networks: whether its website, its mail servers and its nameservers have IPv6 addresses, and whether those addresses actually answer.
What we check
- The website: AAAA and A records for the domain and for its www name. When our IPv6 connection is on, we fetch the home page over IPv6 and over IPv4 and compare the status and the page title, so a site that serves an error or a different page over IPv6 shows up.
- Nameservers: every nameserver in the domain's NS set. Each one's IPv6 addresses are asked for the zone's SOA record directly, to see that it answers with authority.
- Mail servers: each MX host's AAAA records. We don't connect to mail servers.
- The kind of each address: public, private or reserved (unique local, link-local, documentation), or an old transition address (6to4, Teredo, NAT64). Private and reserved addresses are never contacted.
The grade
- Fully reachable: the website has a public IPv6 address that answers the same way as over IPv4, at least one nameserver has a public IPv6 address and every IPv6 nameserver answers, and every mail server has a public IPv6 address.
- Not reachable: neither the domain nor its www name has a public IPv6 address, and no nameserver has one.
- Partly reachable: anything in between. The findings say exactly which part is missing.
When IPv6 connections weren't tested, the grade is based on DNS records only and the result says so.
Common problems
The most frequent finding is a website with no AAAA record at all: the fix is to ask your host for an IPv6 address, or switch it on in your CDN, and publish it. The most harmful is an AAAA record whose address doesn't answer, often left behind after a move: visitors whose networks prefer IPv6 wait for it to time out before they fall back to IPv4. Nameservers without IPv6 are common with older DNS providers; most large providers include it. A private address in public DNS, such as one starting with fd, means an internal record leaked out and should be removed. Each of these has a guide linked from its finding.
Why it matters
Running IPv4 and IPv6 side by side, called dual stack, lets every visitor reach you directly. Networks that only have IPv6 reach IPv4-only sites through translation gateways, which add delay and sometimes fail. Search engines and app stores don't require IPv6 today, but some large mobile carriers are IPv6-only inside, and Apple requires apps to work on IPv6-only networks.
Testing changes
After you add or fix an AAAA record, wait for its old TTL to pass, then run the test again with the fresh option so the cached answer isn't used. If you switched on IPv6 at a CDN, check both the domain and the www name: some providers enable it per host name. When the test runs with IPv6 connections, a server that answers over IPv4 but times out over IPv6 shows up as a failure straight away, which is the problem visitors notice first. A different page title over IPv6 usually means the AAAA record points somewhere else, such as an old host or a parking page, and is worth fixing before anything else.
Using it with other tools
The DNS lookup shows the AAAA records themselves. The ASN lookup tells you which network announces each address. The SSL checker checks the certificate on the same website.
Privacy
We record the domain in your usage history, as with every domain check. The pages we fetch are compared and then discarded: only the status and the page title are kept in the result.