GATE 04 · DNS LEAK TEST
Which DNS servers answer for you?
Quick answer: A DNS leak means your name lookups go to a resolver you did not intend, such as your internet provider's, instead of your VPN's. This test makes your browser look up six random names on our test domain, notes which resolvers asked our DNS server, and shows who runs them.
Your browser looks up six random names under dnstest.globeproxy.com. Our own DNS server records which resolvers asked, for ten minutes, then forgets them.
IP geolocation by DB-IP (CC BY 4.0). Location is approximate and often points to your provider's nearest hub, not your address.
Every time you open a website, a DNS server turns its name into an address. If you use a VPN or proxy but your lookups still go to your internet provider's DNS, that provider can see which sites you visit.
If a resolver belongs to the same provider as your visible IP, the test flags it. A resolver run by a public service (such as Google or Cloudflare) or by your VPN is not flagged.
What the DNS leak test checks
Every time you visit a website, your device asks a DNS resolver to turn the name into an address. By default the resolver belongs to your internet provider. That means the provider can see every site name you look up, even if the pages themselves are encrypted.
When you use a VPN, the lookups should go to the VPN's own resolver. A DNS leak happens when they still go to your provider or to another resolver you did not intend. This test makes your browser look up six random names on our test domain. Our DNS server notes which resolvers asked, and the page shows who runs them.
How to read the result
- Each row is one resolver that contacted our server, with its address, its operator and its country.
- ISP DNS SEEN means a resolver belongs to the same provider as your visible IP address. If you expected your VPN to handle DNS, this is the sign of a leak.
- CHECKED means no resolver matched your connection's provider. A public resolver such as Google or Cloudflare is not flagged, but that company can still see your lookups, so check that it is the one you chose.
- The test cannot see every path. Treat a clean result as a good sign, not proof.
Common causes and how to fix them
- The VPN's DNS protection is switched off. Turn on the DNS leak protection or custom DNS option in your VPN app, then reconnect.
- Windows can send lookups through every network adapter at once. Use a VPN app that locks DNS to the tunnel.
- IPv6 lookups skip the VPN. Enable IPv6 protection in the app, or disable IPv6 on your device.
- Your router or device has manual DNS servers set, which can override the VPN.
- Your browser uses DNS over HTTPS with a public resolver. This hides lookups from your provider but sends them to that resolver instead. Change it in browser settings if you want your VPN's DNS to be used.
After you fix it
Reconnect your VPN, clear your browser's cache if the result looks stale, and run the test again. A different result each time is normal, because resolvers vary between lookups.
Frequently asked questions
What is a DNS leak?
It is when your DNS lookups go to a resolver you did not intend, usually your internet provider's, while you are using a VPN or proxy. The provider can then see which websites you visit.
Does a proxy prevent DNS leaks?
Not always. A browser proxy may still let the system resolve some names itself. SOCKS5 with remote DNS and VPNs that control DNS handle this better. Test your own setup.
Is it a leak if Google or Cloudflare DNS shows up?
Not by itself. If you chose a public resolver, that is expected. It is only a leak relative to what you intended, and that company can see your lookups. This test only flags a resolver run by the same provider as your connection.
Why do I see several different resolvers?
Large DNS services and some providers use many servers, and each lookup may arrive from a different one. Several rows from the same operator are normal.
Is my DNS test result stored?
Resolver addresses from the test are kept in memory for ten minutes so the page can read them, then discarded. They are not written to disk.
Does the test slow down my browsing?
No. It requests six tiny images from a test name on this site, then reads the list of resolvers.