A short, checked list of tools, papers and reproducible tests for detecting VPN leaks: DNS, WebRTC, IPv6 and kill-switch failures.
A VPN that leaks your real IP, ISP resolver or location gives a false sense of privacy. This list keeps only entries whose link was opened and whose description was checked against the source (last check: 19 November 2026). Entries we could not verify were removed.
Maintained by the team behind AnonymFlow and VPNSmith. Entries we publish ourselves are marked (ours).
RTCPeerConnection exposes local and public addresses via ICE candidates.| Tool | Detects | Notes |
|---|---|---|
| AnonymFlow DNS leak test (ours) | DNS | Lists the resolvers that answer your queries |
| VPNSmith IP & WebRTC leak test (ours) | Public IP, WebRTC | Compares your public IP with WebRTC candidates |
| BrowserLeaks | Multi-channel | Closed source, broad fingerprinting suite |
| IPLeak.net | DNS, WebRTC, geo | Closed source |
| DNSLeakTest.com | DNS | Closed source, standard and extended test |
| Mullvad connection check | IP, DNS, WebRTC | Works with any VPN, not only Mullvad |
| Project | Language | Scope | License |
|---|---|---|---|
| dnsleaktest | Shell, Batch, Python | DNS (uses bash.ws) | MIT |
| dns-leak-detector-cli (ours) | Python | DNS, optional ASN match against your VPN | MIT |
| webrtc-leak-detector (ours) | JavaScript | WebRTC local and public candidates | MIT |
dig +short @resolver1.opendns.com myip.opendns.com: the address your DNS path is seen from. It should be your VPN exit.curl -6 ifconfig.co: if this answers while your VPN is IPv4-only, IPv6 is leaking.tcpdump -i any 'port 53 and not host <vpn_dns_ip>': DNS queries that leave outside the VPN resolver.ip route and ip -6 route: check that the default routes point to the tunnel interface.media.peerconnection.enabled.webRTCIPHandlingPolicy to block non-proxied UDP. Free, no account.about:config, media.peerconnection.enabled = false.webRTCIPHandlingPolicy to extension pages. With the policy set to disable_non_proxied_udp, a normal tab returns 0 ICE candidates, while an extension page still returns host candidates with raw IPv4 and IPv6 addresses (no mDNS masking). A test run from an extension popup can therefore show a “leak” that websites do not see. Reproducible test with a one-permission probe extension: chrome-webrtc-policy-extension-pages (ours), measured on Chromium 156.0.8078.4. Always confirm with a test served from a normal web page.ping -i 0.2 <host_outside_vpn>.sudo ip link set <vpn_iface> down.Read the contribution guidelines. Each entry must have a working link and a description that matches its source. No affiliate links.
To the extent possible under law, the maintainers have waived all copyright and related or neighboring rights to this work.