DNS leak test

See where the DNS servers resolving your domain lookups are, and whether they match the exit your web traffic uses. If your proxy is on but your local ISP still resolves your lookups, the sites you visit are exposed outside the proxy.

Not tested yetResults in seconds

See who resolves your domain lookups

In a few seconds, lists every DNS resolver that looks up domains for you and compares each one with your web exit.

Web exit
Fetching…
DNS resolver
—
Shown after the test
Possible leak
—
Shown after the test
01

DNS exits

Every resolver that queried our authoritative server for you in this test, with location, provider and verdict.

After the test, this lists each DNS exit's location, network and verdict.

02

How the test works

No third-party "DNS leak" API: our own authoritative DNS server directly sees who comes to look up these one-time random domains.

STEP 1Generate random domains

Each test generates a set of never-before-seen subdomains, so no resolver can have them cached.

STEP 2The browser visits them

When the browser visits these domains, the system or proxy app hands the lookup to a DNS resolver.

STEP 3The authoritative server logs the visitors

The resolver eventually asks our authoritative server. The visiting addresses it records are the DNS exits resolving for you.

This test

Seen by authoritative server
Shown after the test
Completion
Shown after the test
DNS exits
Shown after the test
Duration
Shown after the test
Tested at
Shown after the test

Web exit used for comparison

Exit IP
Fetching…
Country and city
Fetching…
Network
Fetching…
Network type
Fetching…
03

How we judge

The rule is simple: a resolver that is public DNS such as Google or Cloudflare, or is in the same country or region as your web exit, is considered normal; the rest are marked as possible leaks.

Possible DNS leakSome resolvers are neither public DNS nor in the same country or region as your web exit. Domain lookups may be bypassing the proxy and going to your local network.
No DNS leak detectedThe DNS exits are in the same region as your web exit, or are public DNS such as Google or Cloudflare.
Not enough informationSome requests didn't reach the authoritative server, or a resolver has no ownership information, so no conclusion can be drawn yet.
Test failedThe test didn't complete, perhaps because of a network interruption or the DNS observation service being temporarily unavailable. Please test again.
04

How to prevent DNS leaks

If you want domain lookups to go through your proxy too, start with these three things. Exact names vary by app.

Let your proxy app handle DNS

Turn on DNS hijacking, Fake-IP or "remote resolution" in your proxy app so domain lookups take the same route as your web traffic.

Use encrypted DNS

Turn on DNS over HTTPS (secure DNS) in your system or browser, and make sure it also goes through the proxy, so your ISP can't see your lookups directly.

Close paths that bypass the proxy

Check IPv6 and system settings such as "smart multi-homed name resolution", which can send some lookups around the proxy. After changing them, come back and test again.

05

FAQ

Common questions about DNS leaks, how the test works and how to read the results.

What is a DNS leak?

Before visiting a website, your device first resolves the domain name to an IP address. If your proxy only handles web traffic but lookups still go to your local ISP's DNS, the ISP can see which domains you visit. That's a DNS leak.

How do DNS leaks relate to AI services?

Lookups for ChatGPT, Claude and other services also go through DNS. If they go through the local network, results in some regions may be tampered with or point to unreachable addresses, showing up as failed or flaky connections.

What does it mean if I see Google or Cloudflare DNS?

This is a public DNS service on an anycast network: many data centers worldwide share the same address, so the registered location doesn't reflect where your lookup was actually handled. This page doesn't treat it as a leak.

What's the difference between the quick and deep tests?

A quick test gives results in a few seconds and is fine for everyday checks. A deep test sends more lookups and is better at catching split routing or rotating resolvers, but takes a bit longer. Use the deep test when the result is uncertain.

Why does it say "Not enough information"?

Browser prefetching, system caches or network filtering can stop some random-domain lookups from reaching the authoritative server, and a resolver with no ownership information can't be judged. Try again with a deep test.

Does the test record the websites I visit?

No. The test only uses random domains generated for this test. The authoritative server only records which resolver looked them up and has nothing to do with other sites you visit. See Privacy.

Resolver ownership: IP Geolocation by DB-IP (CC BY 4.0) · ASN data from IPtoASN · All data sourcesDNS observations are made by our own authoritative server