Quick Navigation
What does your leak-test result mean?
Choose what the test showed. This interpreter uses your answers and performs no network test. Do not enter or share an IP address; answers stay in this tab.
Example outcomes and their limits
Illustrative examples, not measurements from your device.
- VPN connected; public result matches a known non-VPN baseline
- Check for a public-IP bypass. Remove an unintended split-tunneling exclusion, reconnect and retest before relying on the connection.
- Public result matches the expected VPN exit
- This result is consistent with the VPN route. Check the other test types and repeat after changing network, server or VPN settings.
- Only a private address or mDNS name appears in WebRTC
- A local address alone does not establish public-IP exposure. Look for a public WebRTC candidate and compare it with your expected VPN exit. No public candidate is not a complete protection test.
- DNS resolver company or country looks unfamiliar
- The resolver label does not establish the DNS route. Check the VPN DNS setting and browser secure-DNS setting against your provider’s documentation, then rerun the DNS test.
- There is no trustworthy reference address
- A reference address is missing. Check the VPN app’s connection details. Collect a non-VPN baseline only when it is safe to disconnect; otherwise keep the result inconclusive.
- A timeout or unavailable browser feature
- Inconclusive. Retry in a supported browser; a missing result is not a pass.
Sources: IETF WebRTC address handling, Firefox encrypted DNS settings. Source check: September 15, 2026.
IP results — How to read them
A public result matching your expected VPN exit is consistent with that route for this browser. A public result matching a known non-VPN baseline while connected suggests a bypass to investigate. A location label alone is insufficient; without a reference, keep the result inconclusive.
- Fix fast: Enable kill switch, switch protocol (WireGuard/OpenVPN), reconnect to a different server, update the VPN app.
- IPv6 tip: If unsupported by your VPN, disable IPv6 at OS level to prevent bypasses.
What is an IP leak? • How to fix IP leaks
DNS results — How to read them
A resolver name does not prove how requests traveled from your device. Check your VPN’s documented DNS behavior and browser secure-DNS settings. An ISP or unfamiliar resolver is a reason to investigate; a provider-branded resolver is not proof that every request stayed in the tunnel.
- Fix fast: Turn on your VPN’s DNS leak protection. Clear DNS cache. On Windows, disable Smart Multi‑Homed Name Resolution; ensure no split‑tunnel app bypasses DNS.
- Alternative: Use your VPN’s DNS or DoH/DoT inside the tunnel (not system/ISP DNS).
DNS leak guide • DNS vs IP vs WebRTC
WebRTC results — How to read them
Compare public WebRTC candidates with your known VPN exit and non-VPN baseline. A private address or mDNS host name alone does not establish public-IP exposure. An empty result, timeout or unsupported API must not be treated as a protection guarantee.
- Fix fast: Check whether the browser is excluded by split tunneling. Follow documented browser and VPN controls, then retest. Disabling WebRTC can break calls and does not repair every routing problem.
- Tip: Different browsers handle WebRTC differently — retest after any browser change.
Speed/latency — Interpreting results
- What’s normal: There is no universal acceptable latency penalty. Compare the same destination under similar conditions; server distance and congestion affect the result.
- Optimize: Switch to the nearest server, try WireGuard, avoid congested locations, and verify no other apps are saturating bandwidth.
Platform‑specific quick links
- Windows IP leak test
- Mac IP leak test
- iPhone/iPad IP leak test
- Linux IP leak test
- IPv6 leak test
- VPN kill switch test
- Torrent IP leak test
FAQ
My VPN is connected but I still fail the IP test — why?
Likely causes: brief reconnection without kill switch, IPv6 bypass, split‑tunneling misconfig, or a buggy server. Enable kill switch, switch protocol/server, and retest.
Do I need to worry about IPv6?
Yes if your VPN doesn’t support it. Either use a VPN that fully handles IPv6 or disable IPv6 at the OS until supported.
Which VPNs avoid leaks consistently?
Consistency depends on client versions and settings. See our top picks below and always retest after changes.
