What an IPv6 leak is
Your device can speak two internet protocols at once: the older IPv4 and the newer IPv6. A lot of VPN software was built for IPv4 and only routes that traffic through the tunnel. If your ISP also gives you IPv6, requests can quietly go out over the IPv6 address — outside the VPN — exposing an address the tunnel was meant to hide.
This test reports how your request actually reached our server. A green result means this connection arrived over IPv4, so IPv6 didn't leak to this endpoint. It does not prove every app on your device behaves the same way — it's one honest data point about your browser's path here.
Who this matters for
- VPN users on IPv6-enabled ISPs, where the VPN only tunnels IPv4.
- Anyone whose VPN app lacks an IPv6 kill switch or IPv6 leak protection.
How to fix an IPv6 leak
- Use a VPN that tunnels or blocks IPv6. The cleanest fix — the app handles both protocols so nothing slips out.
- Disable IPv6 at the OS level if your VPN can't handle it. Effective but heavy-handed, and it can break IPv6-only networks.
Common questions
I got IPv4 — am I safe from all leaks?
This check only covers IPv6. Your DNS or WebRTC could still expose you separately. Run the other tests in the suite for the full picture.
Why was the test inconclusive?
The server-side check couldn't be reached or the deployment isn't configured for it. That's not a verdict either way — we only report what we could actually measure.
Related checks
IPv6 is one path out. These cover the others: