awesome-vpn-leak-detection

Awesome VPN Leak Detection Awesome

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).

Contents

Leak categories

  1. DNS leaks: your ISP resolver answers queries while traffic goes through the tunnel.
  2. WebRTC leaks: RTCPeerConnection exposes local and public addresses via ICE candidates.
  3. IPv6 leaks: the tunnel carries IPv4 only and IPv6 traffic goes out directly.
  4. Kill-switch failures: traffic leaves unprotected while the tunnel drops or reconnects.
  5. DNS-over-HTTPS bypass: an application resolves through its own DoH provider instead of the VPN resolver.

Browser-based testers

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

Open-source detection tools

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

Command-line checks

Browser extensions

Known browser pitfalls

Kill-switch validation

  1. Connect the VPN.
  2. Run ping -i 0.2 <host_outside_vpn>.
  3. Bring the tunnel interface down: sudo ip link set <vpn_iface> down.
  4. Pings must fail at once. Any reply means the kill switch let traffic out.
  5. Bring the interface back. Pings should resume only once the tunnel is up.

Research

Contributing

Read the contribution guidelines. Each entry must have a working link and a description that matches its source. No affiliate links.

License

CC0

To the extent possible under law, the maintainers have waived all copyright and related or neighboring rights to this work.