IPv6 Connectivity Test
Check IPv6 readiness the way test-ipv6 does: probe IPv4-only, IPv6-only and dual-stack hosts plus a large-packet transfer, then report a score out of 10, an itemised check list, your public addresses and their type (native, tunnel or NAT64).
Not tested yet
Press test again to start.
IPv4
Unreachable
—
IPv6
Unreachable
—
IPv6 readiness score
0/ 9
Out of 10, weighted across 8 checks; untestable ones are left out of the denominator
Check details
| Check | Result | Points | Why it matters |
|---|---|---|---|
| IPv4 sites reachable | Fail | 0 / 1 | Verified with a host that publishes only an A record, so it can only be reached over IPv4. |
| IPv6 sites reachable | Fail | 0 / 2 | Verified with a host that publishes only an AAAA record. A quick failure is normal without IPv6; hanging until timeout looks more like a firewall that allows the address but not the traffic. |
| Dual-stack sites reachable | Fail | 0 / 2 | A host publishing both A and AAAA. This is the most important check: failing usually means the browser or an intermediate device mishandles protocol selection. |
| Large packets transfer intact | Fail | 0 / 1 | Receives a full 256 KB. Small requests working while this fails usually means a path MTU black hole (ICMPv6 packet-too-big filtered), common on tunnel links. |
| Public IPv6 address obtained | Fail | 0 / 1 | Echoed by an IPv6-only endpoint. Missing means the ISP hands out no IPv6, or only a local-only address. |
| IPv6 is native | Fail | 0 / 1 | Teredo, 6to4 and NAT64 do provide connectivity, but with higher latency or instability, so they do not count as properly ready. |
| This domain has IPv6 | Skipped | — / 1 | Looks up the AAAA record of this site. Without AAAA you can only reach us over IPv4 even if your own network has IPv6. |
| This visit is over IPv6 | Fail | 0 / 1 | The address family our server saw for this request. |
Your addresses
- IPv4 address
- —
- IPv6 address
- —
- Address type
- —Connection protocol：—
Probe targets
0/9 probes finished| Target | Family | Status | Address read | Time |
|---|---|---|---|---|
| ipv4.icanhazip.com | IPv4 | Waiting | — | — |
| v4.ident.me | IPv4 | Waiting | — | — |
| api4.ipify.org | IPv4 | Waiting | — | — |
| ipv6.icanhazip.com | IPv6 | Waiting | — | — |
| v6.ident.me | IPv6 | Waiting | — | — |
| api6.ipify.org | IPv6 | Waiting | — | — |
| ipv6.test-ipv6.com | IPv6 | Waiting | — | — |
| cloudflare / ipify | Dual | Waiting | — | — |
| cloudflare 256 KB | Large | Waiting | — | — |
How it works: hosts such as ipv4.icanhazip.com publish only A records while ipv6.icanhazip.com publishes only AAAA records. Only a network with the matching protocol can connect, which separates a broken IPv6 from a broken IPv4.
A result of reachable without an address means the connection was established but the host does not allow cross-origin reads. Availability is therefore judged by whether the connection is made.
Probes go straight from your browser to public endpoints. This site only provides the verdict logic and does not log which targets you used.
Comments
No comments yet — be the first to say something