DNS Leak Tester to Check If Your VPN Leaks DNS Queries

You can do everything right — connect to a VPN, check that your IP address has changed — and still quietly give away your real location with every website you visit. That is a DNS leak, and this DNS leak tester exists to catch it: run one test and see exactly which DNS servers your device is actually using, and who operates them.

What a DNS Leak Is, in Plain Terms

Every time you visit a website, your device first asks a DNS server to translate the site's name into an IP address. Those queries are revealing: whoever runs the DNS server can see which sites you look up, and the server's location often betrays yours. Normally the queries go to servers run by your internet provider.

When you use a VPN, the idea is that all of this traffic — DNS queries included — travels through the encrypted tunnel to the VPN's own resolvers. A DNS leak happens when the queries slip outside the tunnel and still reach your provider's servers, often because of an operating-system setting, a router configuration, or a VPN app that handles web traffic but forgets DNS. Your browsing still looks protected on the surface, while the lookup trail points straight back to your real network.

What This DNS Leak Tester Checks

• The DNS servers your connection really uses — the test triggers lookups and records which resolvers answer them.
• Who operates those servers — results are shown with the organisation behind each server, so you can tell at a glance whether they belong to your VPN, your internet provider, or a public resolver you chose yourself.
• Server locations — the countries the resolvers sit in, which is what makes a leak a location problem rather than a minor technicality.
• A repeat test on demand — after changing a setting, run the check again to confirm the leak is gone.

For background, it helps to know your visible address too: the What's My IP tool shows the IP websites see, and the IP information lookup adds location and network details for any address.

How to Run the DNS Leak Test

1. Connect to your VPN first, if you use one — the point is to test the setup exactly as you normally browse.
2. Open the DNS Leak Tester page.
3. Click Run DNS Leak Test and wait a few moments while the test triggers its lookups.
4. Read the list of DNS servers that responded, along with their owners and locations.
5. Compare the results with what you expect: servers from your VPN provider or a resolver you deliberately chose are fine; servers from your home internet provider, while the VPN is on, indicate a leak.
6. After changing any setting, click Re-test to run the check again and confirm the results have changed.

Three Testing Scenarios and What the Results Mean

VPN connected, provider's DNS showing. This is the classic leak. Your web traffic goes through the tunnel, but name lookups do not — your provider can still log every domain you visit. The fix lies in the VPN or system settings described below.

VPN connected, VPN's DNS showing. This is the healthy result: lookups resolve through the VPN's resolvers, consistent with the location your IP address suggests.

No VPN, public resolver showing. If you deliberately set your device or router to a public DNS service, its servers in the results are expected — not a leak, just your chosen configuration, which you can verify further with a DNS lookup on any domain.

If the Test Finds a Leak: Fixes, Limits and Mistakes

Start with the VPN app: look for settings labelled DNS leak protection, or an option to force the VPN's own DNS servers, and switch them on. If the app offers its own DNS, avoid mixing it with manually set system DNS servers — a common mistake is setting a custom resolver in the operating system and forgetting the VPN cannot override it. Restarting the VPN connection after changing settings matters too; many apps only apply DNS changes on a fresh connection.

Router-level settings cause subtler leaks: a router handing out the provider's DNS to every device will undermine one carefully configured laptop. Check the router's DHCP and DNS settings if the leak appears on all devices.

Be honest about limits: this test shows which servers answer your lookups at the moment of testing. It cannot audit your VPN's logging policy, and a clean result today does not prove a provider keeps no records — it proves only that your queries are not leaking to your internet provider right now.

Questions About DNS Leaks and This Test

What does a DNS leak reveal, exactly?

It reveals the domains you look up to your internet provider (or whoever runs the leaking resolver), and the resolver's location can indicate your real location even while a VPN hides your IP address.

I don't use a VPN. Should I still test?

Yes, once. The results confirm which DNS servers your network uses — useful if you set a custom resolver, suspect your router was reconfigured, or want a baseline before changing anything.

The test shows many DNS servers. Is that normal?

It can be. Large providers run clusters of resolvers, and several addresses belonging to the same operator are not a problem. What matters is who operates them.

Can a browser cause a DNS leak on its own?

Yes. Some browsers use their own encrypted DNS settings that bypass system and VPN resolvers. If results look wrong, check the browser's DNS or "secure DNS" option and test again.

How often should I re-test?

After installing or updating a VPN app, changing routers, or altering network settings — any change to how your device connects is a good moment to click Re-test.

Does a clean test mean I am anonymous online?

No. It means DNS queries are not leaking. Your IP visibility, browser fingerprint and account logins are separate matters that a DNS test does not judge.

Test Before You Trust the Tunnel

A VPN earns your trust only when every part of your traffic uses the tunnel, and DNS is the part most often left behind. Run this test after every VPN install, update or settings change, and treat a clean result as your baseline: your lookups going where you chose, and nowhere else.