Skip to main content
Free Tool - No Signup Required

DNS Leak Test

See which DNS resolvers really handle your lookups, and whose network they are in. On a VPN, that tells you whether your DNS stays inside the tunnel.

Takes about eight seconds. Run it once with your VPN off and once with it on to compare.

How the test works

  1. The page asks this site for a handful of host names made for this one test. They exist nowhere else, so no resolver has them cached.
  2. Your browser looks them up the way it looks up any site: through whatever resolver your device, VPN or browser is set to use.
  3. Those names sit under a zone that only our own name server answers for, so each resolver has to come to us. We note the address each question came from.
  4. The page shows those addresses with the network each belongs to, next to the network of your own IP address.

The names do not resolve to anything, on purpose: the lookup itself is the measurement. Your browser’s developer console therefore shows a few failed requests while the test runs.

How to fix a DNS leak

Turn on the VPN’s own DNS protection
Most VPN apps have a setting named “DNS leak protection”, “use VPN DNS” or “block outside DNS”. Switch it on, reconnect and run the test again.
Check IPv6
A VPN that only tunnels IPv4 leaves IPv6 lookups on your normal connection. Either use a VPN that carries IPv6, or let the app block IPv6 while it is connected.
Check the browser’s secure DNS
Firefox (“DNS over HTTPS”) and Chrome, Edge and Brave (“Use secure DNS”) can send lookups to their own resolver, past the VPN’s. That is encrypted, so your provider cannot read it, but it is a third party you may not have meant to use. The setting is under Privacy and security.
Windows: several network adapters
Windows can ask the resolvers of every adapter at once and use the fastest answer, so the Wi-Fi adapter’s resolver still gets your lookups. A VPN app with leak protection blocks port 53 outside the tunnel to stop this.
Router or manual settings
A resolver typed into the network settings of the device, or handed out by the router, stays in use when the VPN does not replace it. Remove the manual entry or set it to the VPN’s resolver.

Related checks

  • Domain scan: DNS, DNSSEC and email security of a domain you run.
  • WHOIS lookup: who a domain is registered to and when it expires.
  • SSL checker: the certificate a server really presents.

Frequently Asked Questions

What is a DNS leak?

Every site you open starts with a DNS lookup: your device asks a resolver for the address behind the name. A VPN is meant to send those lookups through its tunnel to its own resolver. A DNS leak is a lookup that goes around the tunnel, usually to the resolver of your internet provider. The provider then still sees every name you visit, even though the traffic itself is encrypted.

How does this DNS leak test work?

The page makes your browser look up a few host names that were created for this one test and exist nowhere else. They sit under a zone that only our own name server answers for, so whichever resolver your device uses has to come to us to ask. We list the addresses those questions came from, with the network each address belongs to.

How do I read the result?

Ask who you expect to handle your DNS. With a VPN on, every resolver listed should belong to the VPN provider or to a public resolver you chose; one from your own internet provider is a leak. Without a VPN, seeing your provider’s resolver is normal. Seeing Google, Cloudflare or Quad9 means your device, router or browser is set to use that public resolver.

Why does a resolver belong to a different network than my IP address?

Because the resolver is not run by whoever gives you your address. That is the case when you set a public resolver such as 8.8.8.8 or 1.1.1.1, when your browser uses DNS over HTTPS (Firefox and Chrome can do this on their own), or when a VPN app sends DNS to a third party. It is only a problem if you did not choose it.

Why do I see more than one resolver?

Large resolvers are pools of machines, and each lookup can leave from a different one, so several addresses in the same network are one resolver service. Addresses in different networks mean your device really uses more than one service, for example an IPv4 and an IPv6 path with different settings.

Why did the test find no resolver?

The lookups never reached our name server. A filtering resolver, a company network or an ad blocker may refuse unknown names, or the browser blocked the requests. Try another browser or switch the blocker off for this page. The test cannot say anything about your DNS in that case, which is not the same as “no leak”.

What do you store?

For ten minutes: the random test id and the resolver addresses that asked for its names. After that both are deleted. Your own IP address is read from the request to compare networks and is not stored with the test.