Hello …
Looking up your connection…
Standard is quick. Extended runs more rounds to catch load-balanced resolvers.
WebRTC leak not run
WebRTC can reveal your real IP even behind a VPN, straight from the browser.
| Local IPs | — |
| Public IPs | — |
Location consistency not run
Mismatches between your IP's country, your timezone and your browser language are classic de-anonymisers.
| IP country | — |
| Timezone | — |
| Browser language | — |
What is a DNS leak?
Every website you visit starts with a DNS lookup that turns a name like example.com into an IP address. Whoever runs the DNS resolver that answers those lookups can see the name of every site you connect to. If you use a VPN but your lookups still go to your ISP's resolver — or any resolver outside the tunnel — that's a DNS leak: your VPN hides your traffic, but not the list of places you go.
This test gives your browser a set of one-time hostnames to resolve. Because they're unique, the resolver you're actually using has to ask our name server directly — which lets us show you exactly which DNS servers see your activity, and give you a straight pass or leak answer instead of a table to decode.
How to fix a DNS leak
- Make sure your VPN is configured to use only its own DNS servers, and enable its kill-switch.
- Turn off "secure DNS" / DNS-over-HTTPS in your browser if your VPN or router is meant to handle DNS.
- On desktop, remove any hard-coded DNS servers from your network adapter so the VPN's DNS is used.
- Disable WebRTC in the browser (or use an extension) if the WebRTC test above exposed your real IP.