Run an IPv6 test from this browser
An IPv6 test checks whether a specific connection can use Internet Protocol version 6. This tool sends one request to an IPv4-only address endpoint and another to an IPv6-only endpoint. Run the test to see which requests succeed and the public address each endpoint observes. The IPv6 test runs in your browser, because a request made by our server would measure our server's connection instead of yours.
Read more
You do not need an account, a browser extension, or camera permission. The two requests run independently, and each has an eight-second timeout. The IPv6 test names the external endpoints before you run it: api.ipify.org for IPv4 and api6.ipify.org for IPv6. Those services receive the source address used to connect to them. Results describe the current browser path and should be refreshed after a relevant network change.
Select Run test after noting your connection and VPN state. Stop cancels waiting; Clear removes results. Change one network setting at a time when comparing runs, so differences have a clear context.
Interpret an IPv6 test result
If the IPv6 request succeeds, the browser reached the IPv6-only endpoint during this measurement. The displayed address is the source observed at that endpoint. A successful IPv6 test is useful evidence of usable IPv6 on that path. It does not establish that every IPv6 destination is reachable, that every application uses IPv6, or that the connection has a particular speed or security level.
Read more
If both requests succeed, both address families were usable for these destinations. That is consistent with a dual-stack connection, although translation and other network mechanisms can complicate the complete architecture. The IPv6 test cannot inventory all of those mechanisms from two HTTP responses. Treat the measured reachability as the direct observation and any explanation of the wider network as something to confirm separately.
Why does the homepage show IPv4 when this IPv6 test works?
A website that supports both families can be reached over either. The browser and operating system choose a connection according to availability and timing. One request showing IPv4 does not mean the device lacks IPv6. Conversely, one IPv6 result does not establish that IPv4 is unavailable. This IPv6 test uses separate family-specific endpoints to make that distinction clearer than a single dual-stack request can.
What does “endpoint not reached” mean?
It means the relevant request did not produce a valid successful result within the test conditions. Possible causes include unavailable IPv6 routing, a DNS problem, a firewall, an extension, a VPN policy, or an endpoint outage. A failed IPv6 test should not be rewritten as “your device has no IPv6 address.” A device can have IPv6 configured locally while lacking a working route to this destination.
The summary distinguishes IPv6 observed, IPv4-only observed and insufficient evidence. Each endpoint retains its own source and error; one valid reply cannot erase the other request’s failure.
What this IPv6 test does not measure
This measures browser HTTP reachability, not ICMP, traceroute or throughput. Displayed request durations include browser and endpoint work and are not a network-quality score. The eight-second deadline bounds each request; it is not a latency rating.
Read more
Temporary addresses and changing results
IPv6 interfaces can have temporary outbound addresses and several scopes. Changed results can therefore be normal. Record the time, network and VPN state. A link-local fe80 address is different from the public address observed here.
NAT64 and translated connections
Translation can let IPv6 clients reach IPv4 services, so an IPv4 endpoint response does not prove a public IPv4 address is configured locally. The report states endpoint observations without reconstructing DNS64, NAT64 or other transition mechanisms.
Sources
The family-specific endpoint behavior is documented by ipify. IPv6 addressing is described in RFC 4291, normalized text representation in RFC 5952, and connection selection behavior in RFC 8305. These references explain mechanisms; the IPv6 test above supplies a current observation with a deliberately limited scope.