What these checks can and cannot see
Honesty first, because DNS leak pages overpromise. A browser page can detect WebRTC IP exposure (a related leak), read the web exit IP this page sees, and look up who owns it — that is what the button above does. A browser page cannot see which DNS resolver your operating system uses or catch it in the act of leaking: that requires watching your lookups from the authoritative side. The section below explains exactly how that full test works and where to run it. Anyone claiming a pure-JavaScript DNS leak test is measuring your system resolver is selling something.
What a DNS leak actually is
DNS turns names into addresses, and by default it does so in plain text. When you connect a VPN, the intent is that all your traffic — including lookups — exits through the tunnel. A leak is when the operating system quietly keeps asking your old ISP resolver, or the VPN client fails to take over DNS. The result: your web traffic is hidden, but the list of domains you visit is an open book to your ISP and to anyone on the path between you and the resolver. For privacy-minded users that is the whole ballgame; for journalists and activists it can be a safety issue.
DNS leaks have cousins worth checking at the same time: WebRTC leaks (browser peer-to-peer API exposing your real IP behind a VPN — detected above), IPv6 leaks (VPN covers IPv4 only, traffic escapes via IPv6), and split-tunneling accidents (an app or VM routing outside the tunnel). A careful privacy pass tests all four.
How the full test works (and why it needs help from the other side)
The technique every real DNS leak test uses: the page contains a batch of unique random subdomains,
like a7f3.example-test.net. Your browser must resolve them to load anything. The site's
authoritative name server logs which resolver IP asked for each one. If you're on a VPN in
Berlin and the resolvers asking are your ISP in another country — leak confirmed. The extended mode
repeats this across dozens of lookups to catch multi-resolver setups, where some queries go one way
and some another. Run it at dnsleaktest.com
(the standard), then compare the resolver list against your VPN provider's published resolver owners.
Re-test after every VPN or router configuration change — leaks come back with updates.
How to fix a DNS leak
- VPN DNS lock (first): modern clients (WireGuard-based apps, Mullvad, Proton) have a DNS/kill-switch setting that forces all lookups through the tunnel. Turn it on — this alone fixes 90% of leaks.
- Encrypted DNS at the OS: enable DNS-over-HTTPS or DoT so plain-text port 53 has nothing to leak. Android Private DNS, iOS/macOS profiles, Windows 11 native DoH, or browser-level “secure DNS”.
- Router-level enforcement (strongest): on OpenWrt, intercept all LAN port-53
traffic and redirect it through
https-dns-proxyto a DoH provider you chose. No device on the network can leak around it — phones included. DNS fits alongside SQM tuning in the same router pass. - After fixing: re-run the full test until the resolver owners consistently match your VPN provider or chosen DoH provider, not your local ISP.
DNS leaks vs the other leaks people test for
| Leak type | What escapes | Detected by |
|---|---|---|
| DNS leak | Domains you visit (plain-text lookups) | Authoritative-side test (dnsleaktest.com) |
| WebRTC leak | Your real/local IP behind a VPN | This page — instant, above |
| IPv6 leak | Traffic bypassing an IPv4-only tunnel | Compare IPv4 vs IPv6 exit on a dual-stack test page |
| App split-tunnel | Selected apps outside the tunnel | Router traffic monitor / per-app VPN rules |
Related tools on this site
Once your DNS path is sealed, tune the rest of the connection: DNS resolver speed comparison (pick the fastest DoH endpoint before you commit), bufferbloat test, ping and jitter checks.
FAQ
What is a DNS leak?
A DNS leak happens when your DNS lookups bypass the tunnel you expect them to use. The classic case: you connect a VPN, web traffic exits through the VPN — but the operating system keeps sending DNS queries in plain text to your local ISP resolver. Every domain you visit is then visible to your ISP (or to anyone watching that hop), defeating a main reason for using a VPN.
How do I run a full DNS leak test?
A proper test needs to see your lookups from the other side. Sites like dnsleaktest.com generate a page of unique random subdomains; when your browser resolves them, their authoritative name server records which resolver IP asked. If the resolvers listed belong to your local ISP while your IP shows the VPN exit, you have a leak. Their extended test shows each resolver and its owner. The WebRTC and exit-IP checks on this page cover the browser-side half instantly.
Can a browser test detect a DNS leak by itself?
Not the DNS part — browsers deliberately cannot see which resolver the operating system uses, and JavaScript cannot trigger a system lookup and observe who answered. That requires the authoritative-server technique above. What a browser CAN detect: WebRTC IP exposure (a different leak class), and your web exit IP and its owner for comparison. Treat any page claiming otherwise with suspicion.
How do I fix a DNS leak?
In order of preference: (1) enable your VPN client's DNS/DNS-lock feature so the tunnel captures all port-53 traffic; (2) turn on DNS-over-HTTPS in browser or OS so lookups are encrypted to a resolver you chose; (3) on OpenWrt, redirect all LAN DNS to the router and forward it via https-dns-proxy, so no device can leak around it. Then re-test: resolvers listed should match your VPN provider, not your ISP.