VPN Leak Test
Run the broader multi-signal privacy check.
Open VPN Leak Test
DNS Privacy Test
DNS Leak Test
See which DNS resolvers your connection is actually using and whether they appear consistent with your current network.
No installation Temporary test Usually completes in seconds
Your connection
Detecting
…
Detecting your connection…
DNS Resolver Check
Ready to test
Connection
Detecting…
Resolver
Not tested
Mode
Quick Test
Status
Waiting to run
Checking your DNS path
- Starting secure test
- Creating unique DNS hostname
- Waiting for DNS resolver
- Comparing network
0 / 0 probes observed
0 resolver endpoints discovered
We couldn’t complete the DNS observation.
Try the test again.
Deep scan complete
Connection ↔ resolver
Your connection
DNS resolver
DNS resolvers observed
Resolver endpoints observed by our authoritative DNS during this scan.
| Resolver | Provider | Network | Type |
|---|
Why did the scan find multiple endpoints?
DNS providers often use pools of recursive resolver endpoints for redundancy, load distribution and IPv4/IPv6 connectivity. Multiple observed IP addresses do not necessarily mean that your device has multiple DNS servers configured.
What we observed
Technical details
A new temporary test will be created
Understand your DNS privacy
What a DNS leak test can tell you about your connection — and what it can’t.
DNS basics
What is a DNS leak?
DNS turns the domain names you visit into addresses your device can connect to. A leak occurs when those lookups are answered by a resolver outside your expected setup — for example, your ISP’s resolver responding even though a VPN is active.
VPN context
What should this test show?
With no VPN active, ISP or network resolvers are completely normal. A recognized public service isn’t automatically a leak either. With a VPN active, resolvers that don’t match the VPN provider are worth a closer look. Geography alone never proves a leak.
Infrastructure
Why can multiple DNS servers appear?
Large resolver operators run pools of servers across regions for redundancy, so a single test can legitimately observe more than one address. Separate IPv4 and IPv6 queries may also be answered by different resolver instances within the same provider.
Limitations
Does this prove my VPN is secure?
No. DNS is only one privacy signal among several, and a clean result here doesn’t mean your traffic is fully protected. A complete check should also look at your visible public IP, IPv6 behavior, and browser-level signals such as WebRTC.
How this test works
- 01 Unique hostname A temporary hostname is generated for this test.
- 02 Browser query Your browser attempts to resolve it.
- 03 Resolver observed Our authoritative DNS sees which resolver asks.
- 04 Network comparison Resolver metadata is compared with the public connection.
- 05 Result A cautious verdict is produced.
Continue checking your connection
Each tool inspects a different part of what your connection or browser can reveal.
WebRTC Leak Test
Check browser-level IP exposure.
Open WebRTC Leak TestIP Lookup
Inspect the public IP or network provider.
Open IP Lookup