DNS Leak Test
Check if your DNS requests are leaking and exposing your real location
What is a DNS Leak?
A DNS leak occurs when your DNS queries go to your ISP's DNS servers instead of your proxy provider's. That exposes the list of domains you open and your approximate location, even when the traffic itself goes through a proxy.
Even when traffic goes through a proxy, DNS queries can go straight to your ISP. It then sees every domain you open — the pages are encrypted, their names are not. This check shows which DNS servers answer your queries.
What a DNS leak is
Before opening a site, your device asks a DNS server which IP a domain maps to. If that query escapes the tunnel — to your ISP or a public resolver — a full record of who visited which sites remains, regardless of the proxy.
How to read the result
Look at who owns the servers found. If it is your home ISP while traffic is supposed to run through a proxy in another country, you have a leak. If they belong to the proxy provider or a public resolver such as Cloudflare, queries are going where they should.
Frequently asked questions
Why is a DNS leak a problem?
Your provider gets the history of domains you visited even though page contents are encrypted. Where the address is changed deliberately, this undoes the change: the source of the queries stays the same.
How do I fix a leak?
Set DNS servers manually in system or browser settings, enable DNS-over-HTTPS, or use a client that tunnels DNS alongside the traffic.
Why does the result list several servers?
Systems usually query several resolvers for redundancy, and large DNS providers answer from multiple addresses in one network. Several rows are normal; what matters is who owns them.
Does changing DNS affect speed?
Barely. The difference between resolvers is tens of milliseconds and only on the first lookup for a domain — after that the answer is cached.
Work through proxies without leaks
Rotating proxies over HTTP and SOCKS5: DNS is resolved on the proxy side, not at your ISP.
See pricing