IPv6 Test
Six probes, run from your own browser, that show whether your network can reach the IPv6 internet — and whether it would still work if a site dropped IPv4 tomorrow.
Checking how your connection reaches the internet…
Six probes are running against hosts locked to one protocol each. Nothing here is measured on our server — only your own browser can prove which protocols your network really carries.
What was tested
- Queued: IPv4 connectivityLoads a host that publishes an A record and nothing else.Queued
- Queued: IPv6 connectivityLoads a host that publishes an AAAA record and nothing else.Queued
- Queued: Protocol preferenceBoth addresses on offer — this is the one your browser picked.Queued
- Queued: IPv6 without DNSConnects straight to an IPv6 literal, so no name has to resolve.Queued
- Queued: Large packets over IPv6Pulls back more than one packet to catch a broken path MTU.Queued
- Queued: AAAA-only name resolutionWhether your resolver can return a name that has no IPv4 address.Queued
Your IPv6 address
TestingYour IPv4 address
TestingWhy any of this matters
IPv4 has about 4.3 billion addresses and ran out years ago. The gap is papered over with carrier-grade NAT, which puts you behind an address shared with hundreds of other subscribers — the reason you hit CAPTCHAs someone else earned, and the reason inbound connections to your machine mostly do not work any more.
IPv6 has enough addresses that every device gets a real one again. Most large networks now carry it, so if your connection has it, a good share of your traffic is already using it without you noticing.
How the test works
Each probe is aimed at a hostname that publishes records for one protocol only. A host with just an AAAA record can only be reached over IPv6, so a reply from it is proof — no guessing from the shape of an address.
It all runs in your browser, never on our server. Our front door answers on IPv4, so the server's view of you would say “no IPv6” for every visitor. Only your own stack can answer the question honestly.
The one that catches people out
The large-packet test looks strange until it fails. IPv6 has no in-flight fragmentation: when a packet is too big for a link, the router is supposed to send back an ICMPv6 Packet Too Big so the sender tries again smaller.
Firewalls that block all ICMP break that conversation. Small requests succeed, so IPv6 looks fine — then anything substantial stalls forever. Pages begin loading and hang. If that test failed, set your router's IPv6 MTU to 1280 and try again.
If you have no IPv6
Nothing is wrong with your computer, and there is no browser setting to change. IPv6 has to be delivered by your ISP and then passed on by your router — both have to agree.
Worth checking in this order: whether your ISP offers IPv6 on your plan at all, whether your router has it enabled (often off by default, or disabled on an ISP-supplied box), and whether a VPN is active — many VPNs carry IPv4 only and deliberately switch IPv6 off to stop it leaking around the tunnel.