How to read the result
If the page shows a public IPv6 value, your browser can reach an endpoint that only supports the newer protocol. If it shows none, your connection may still work normally over IPv4, but that path is unavailable from this browser session. Privacy apps, routers, ISP settings, corporate firewalls, and browser security tools can all affect the result.
Why IPv6 matters
IPv6 provides a much larger numbering space than IPv4 and is increasingly common on mobile, fiber, and modern ISP connections. It can coexist with IPv4, which is why one device may show both values on the home page. To learn the basics, read What Is an IP Address?.
Related privacy and routing checks
After testing, you can use the public route checker to inspect any IPv6 value, ASN Finder to identify the route owner, and the WebRTC leak test to see whether your browser exposes additional candidates.
Troubleshooting no IPv6 result
If IPv6 is not detected, check whether your ISP offers it, whether your router has support enabled, and whether a privacy app blocks it to prevent leaks. Some offices and public Wi-Fi hotspots disable the newer protocol even when the device supports it. Testing again on mobile data or a different hotspot can help isolate the cause.
IPv6 and privacy
IPv6 does not automatically make a connection less private, but it can create a second public path that behaves differently from IPv4. When using a privacy tunnel, confirm that both versions are either routed through it or intentionally blocked by the app. For background, read the VPN guide.
What this tool checks
The page checks whether your browser can reach an IPv6-only endpoint and separately checks IPv4 fallback. That matters because many connections are dual stack: one browser request may use IPv4 while another can use IPv6. The result reports the public IPv6 value when available, whether IPv4 still works, and the provider details returned by the data source.
How the test works
The browser requests an IPv6-capable service and waits for a response. If the request succeeds, the page shows the visible result. If it fails or times out, the page reports that the newer protocol was not detected from this browser path. The IPv4 fallback check runs separately so you can tell whether the connection is offline or simply using IPv4 only.
Common use cases
Use this page after changing routers, switching mobile carriers, enabling a privacy tunnel, configuring firewall rules, or troubleshooting a site that behaves differently on one device. It is also useful when comparing home broadband with cellular data, because mobile providers often support IPv6 before some fixed-line providers do.
Limitations
A failed result does not always mean your ISP lacks IPv6. Browser extensions, DNS settings, tunnel leak protection, enterprise firewalls, captive portals, and temporary service issues can all block the check. Likewise, a successful result only confirms browser reachability at the moment of the test; it does not prove every app on the device uses the same route.
Related tools
After confirming IPv6, use the public route checker to inspect the visible value and ASN Finder to understand route ownership. If privacy is the reason for testing, run the WebRTC leak test and compare the results before and after changing tunnel settings.
Frequently asked questions
What does this test check?
It checks whether your browser can reach an IPv6-only service and shows the public value if one is available.
Why do I have IPv4 but no IPv6?
Your ISP, router, privacy app, device, or local policy may not support IPv6. Many connections still work normally over IPv4 only.
Can a privacy app change my result?
Yes. Some services provide IPv6, some block it to prevent leaks, and some route only IPv4. Run the test with protection on and off to compare.
Should IPv6 be disabled for privacy?
Not usually. The safer approach is to make sure IPv6 follows the same privacy policy as IPv4: routed through the tunnel when desired or intentionally blocked by the app.