Use it in two ways: run a quick standalone check to see your current IP, DNS, IPv6 and WebRTC exposure, or save a baseline first and compare it with a VPN session. The verdicts explain what changed, what that means and what to fix next.
These cards stay hidden until you run the test. Use the first tab for a standalone privacy check, or switch to the comparison tab after you save baseline and test again with VPN.
Run the test once and this card will explain what your current network exposes right now.
Save baseline first, then run the test again with VPN enabled. This card becomes the plain-English comparison layer.
These are VPN providers we test regularly for DNS handling, route stability and leak resistance. Use them as a next step only after you read your result and decide you want to retest with a stronger or cleaner setup.
One of our most consistent picks when you want stable DNS routing, fast reconnects and a clean follow-up retest after a suspicious result.
A strong value option when you want to compare DNS behavior across several devices and check whether the same issue repeats everywhere.
A privacy-focused comparison point when you want to verify whether a leak survives after browser DNS, IPv6 or app-level changes.
This is the advanced layer of the leak tool. Instead of checking one DNS request, it fires a burst of 20 unique probes, waits for the resolver path to stabilize, then explains whether you are seeing a single clean resolver cluster, mixed ownership, or partial DNS behaviour that deserves closer review.
Some queries follow one path, later queries follow another. A quick test can miss that.
Only part of the burst returns before timeout. That often points to unstable DNS routing or filtering.
The dangerous pattern is not “many IPs”, but “different networks or providers in the same burst”.
After the result, the lab explains what the pattern means in technical terms and in plain language.
—
This board lists every resolver IP seen during the burst. What matters most is whether they stay on one stable DNS path or split across different groups.
| Result | Run Deep DNS Sweep to generate your advanced breakdown. |
|---|---|
| Why it matters | This table translates the burst into a user-facing explanation and a technical interpretation. |
| Risk level | Waiting for data. |
| Next step | No action yet. |
Technical details will appear here after the burst. The lab will explain probe completion, resolver ownership, and whether the result looks like one stable DNS path or a mixed route.
Simple explanation will appear here after the burst. This tab turns the result into plain language and a clear next action.
What DNS leaks are, why they happen, and which settings usually fix them.
Open DNS leak guideUse this when the burst shows partial or unstable behaviour and you need a structured fix path.
Open troubleshooting guideIf DNS looks clean but browsing still feels slow or unstable, cross-check latency, download and upload performance.
Open speed testUseful if the burst was run from a café, hotel, airport or shared network with unusual DNS handling.
Open public Wi‑Fi guide—
These recommendations stay hidden until the deep test finishes. They are shown only after the diagnostic result, so the recommendation comes after the evidence—not before it.
Strong DNS consistency, fast apps, and a good default choice when you want fewer surprises across desktop and mobile.
Good value for users who need multiple devices and want to compare DNS behaviour across phone, laptop and TV.
Good for users who care about a more privacy-focused stack and want another reference point when comparing resolver behaviour.