VPN security testing

Open source tools and references for verifying VPN integrity: DNS leaks, WebRTC leaks, throughput overhead.

Why this exists

Most "VPN leak testers" you find online either ship heavy analytics scripts or hide their methodology. The tools listed here all share three properties: zero dependencies, MIT license, auditable in under 15 minutes. They were built to complement the in-depth methodology write-ups maintained at anonymflow.com, independent VPN and privacy tooling research.

Whether you are a developer integrating leak checks into a CI pipeline, a security professional auditing a VPN provider, or just a user wanting to verify your tunnel actually does what it claims, these tools are useful as-is.

Tools

dns-leak-detector-cli

Python 3.8+CLIMITZero deps

Command-line DNS leak detector. Probes the OS-level resolver via getaddrinfo() plus an external probe domain, then compares each detected resolver's ASN against your expected VPN provider. Detects Windows SMHNR leaks, IPv6 leaks, and ISP-resolver fallback that web testers commonly miss. Cron-ready with exit-code thresholds.

Companion methodology: Test a DNS leak in 2 minutes: complete methodology.

webrtc-leak-detector

HTMLBrowser onlyMITNo tracking

Single HTML file (12 KB) that detects WebRTC IP leaks in your browser. Runs entirely client-side via RTCPeerConnection probing. Classifies each ICE candidate as loopback / local / mDNS-obfuscated / public, then cross-checks with an HTTP-egress lookup to flag real leaks.

Open the file locally or host it anywhere. No analytics, no third-party scripts, auditable in 10 minutes.

vpn-speed-tester

Python 3.8+CLIMITCron-ready

CLI that measures VPN overhead on download, upload, latency, and jitter. Baseline-vs-VPN comparison persisted to disk. Threshold-based exit codes for cron monitoring (alert when overhead exceeds a configurable percentage).

Companion methodology: Real-world VPN speed test methodology. Dataset: 95-session VPN streaming study.

Browser tools and curated lists

Hosted versions that run in the browser, plus reading lists. Each page states what it does and does not test.

Planning and budgeting calculators

Measured: what DNS over HTTPS actually costs

One evening of timing from a datacenter VPS (Contabo, AS51167, France), 1 November 2026: 3 resolvers, 3 runs each, 5 queries per HTTP/2 connection, 45 queries in total (example.com A, RFC 8484 wire format, curl 8.5.0).

Resolver1st query (3 runs)Warm queries, median
Cloudflare47.6 / 28.3 / 28.9 ms4.8 ms
Google36.1 / 39.0 / 49.9 ms5.6 ms
Quad939.8 / 38.0 / 52.4 ms7.7 ms

The first query pays for the TLS handshake (finished 24 to 41 ms after the start); once the connection is open, a lookup costs a few milliseconds. The cost of DoH is per connection, not per query. Same evening, dig @9.9.9.9 isitblocked.org returned NXDOMAIN: Quad9's filter canary is live. Limits: one vantage point, one cached domain, no home ISP path, no HTTP/3. Full write-up with the curl command: dev.to. To turn DoH on in Chrome, Firefox, Edge, Brave and Safari: DNS over HTTPS browser setup guide.

Methodology references

Every tool above is distilled from a longer methodology write-up. The full references are maintained at AnonymFlow:

Affiliation disclosure

These tools are released under MIT license and were built and are maintained by the same team behind AnonymFlow, an independent VPN and privacy research site. AnonymFlow operates affiliate partnerships with several VPN providers covered in its reviews: the testing methodologies linked above include a dedicated section on how those conflicts are addressed.