Skip to main content

Complete Privacy Test

Run all privacy checks at once — IP address, DNS leak, WebRTC leak, and browser fingerprint analysis in a single test.

Last updated: August 25, 2026

Not measured

IP Address

Not measured
Not measured
View full details

DNS Leak Test

Not measured
Not measured
View full details

WebRTC Leak Test

Not measured
Not measured
View full details

Browser Fingerprint

Not measured
Not measured
View full details

What we measure here

Results from every real session measured with this tool. Automated traffic is excluded.

MeasurementResultSessions measured
Sessions that passed every check6.9%1,350

Measured on ipdrop.io between 2026-06-07 and 2026-09-01. See all privacy statistics

How This Test Works

Four checks run in parallel the moment the page loads — no button, no queue. Each is the same measurement its dedicated tool page performs, so the results here and the results there agree.

The IP check reads your public address and the organisation it is registered to, which is what separates a consumer ISP from a datacentre or VPN provider. The DNS check asks several independent resolvers what they see and compares their answers against the tunnel you appear to be using. The WebRTC check opens a peer connection and inspects the ICE candidates the browser offers before any page has asked for them. The fingerprint check samples the attributes a tracking script would read and estimates how far they narrow the field.

Nothing is averaged into a single verdict. Each check passes, fails, or comes back inconclusive on its own, and the score is simply how many passed — so three-of-four tells you exactly which layer to open next. The individual tool pages carry the deeper output for whichever one failed.

What Each Check Actually Measures

The IP check reads your public address and the organisation that owns it, then judges whether the exit looks like a VPN or your own ISP. The DNS check resolves a set of unique hostnames and reports which resolvers answered, which reveals whether your queries are leaving the tunnel. The WebRTC check asks your browser for its ICE candidates, the mechanism that historically exposed real addresses from behind a VPN. The fingerprint check samples the properties sites use to recognise a browser — canvas and WebGL rendering, fonts, hardware hints — and estimates how rare that combination is.

Every check has three outcomes, not two. A probe that was blocked, timed out, or could not run is reported as inconclusive and excluded from the score rather than counted as a pass. This matters most on exactly the networks where guessing is most tempting: censored connections and restrictive corporate proxies routinely block the endpoints leak tests depend on, and a tool that treats silence as success hands out a clean bill of health precisely where the risk is highest.

What a Browser Test Cannot See

These four checks describe what your browser and your network reveal to a website right now. They cannot see the larger part of tracking: data brokers merging records you never submitted, the accounts you are signed into, tracking pixels in your email, telemetry from your operating system, or the connection metadata your ISP retains regardless of what any page can observe. A perfect score here means this browser, on this network, at this moment, leaks nothing detectable from the client side. That is a useful floor, not a complete privacy audit.

Not every VPN protects the same things

IPv6 handling, DNS leak protection, and real-world speed vary widely between providers. Compare the two we recommend.

Proton VPN vs NordVPN

Frequently Asked Questions

What does this privacy test check?
Four measurements, all taken in your browser the moment this page loaded. Whether your public IP belongs to a VPN or hosting provider rather than a consumer ISP; whether DNS queries resolve through servers outside your tunnel; whether WebRTC volunteers an address the page never asked for; and how unusual your browser's measurable attributes are next to everyone else's. Each is scored on its own, so a failure tells you which layer leaked rather than only that something did.
How is the privacy score calculated?
The score is based on four individual tests. Each test either passes or fails: IP test passes if a VPN is detected, DNS test passes if no leaks are found, WebRTC test passes if no public IPs are exposed, and fingerprint test passes if your uniqueness is below 50%. Your overall score is the number of tests passed out of four.
Do I need a VPN to pass all tests?
For the IP check, yes — it looks for a connection terminating somewhere other than a residential ISP, and only a VPN or proxy produces that. DNS and WebRTC usually improve alongside it, though a misconfigured client can leak on both while the IP check still passes, which is the exact failure this page exists to surface. The fingerprint check is untouched by any of it: that one is decided by your browser build and settings, and no tunnel will move it.
Is this test safe to run?
Yes. All tests run entirely in your browser using JavaScript. No data is stored on our servers, and no personally identifiable information is collected. The DNS leak test makes requests to public IP detection services, and the WebRTC test uses standard browser APIs — neither sends your data to us.
How often should I run this test?
After anything that changes the path your traffic takes, or the browser it takes it from: a new network, a different VPN server or protocol, a browser update, a freshly installed extension. Updates are the usual culprit — WebRTC and privacy preferences are occasionally reset to defaults, and nothing announces it when they are. On a stable setup weekly is plenty; the value is in catching the change you did not know you had made.
What does an inconclusive result mean?
It means the probe could not complete — the endpoint was blocked, the request timed out, or your browser refused the API. Inconclusive is deliberately not a pass, and it is excluded from the score entirely, because reporting an unmeasured check as green is how privacy tools give false reassurance on restricted networks.
Why did my score change when I changed nothing?
Results are measured fresh on every run and nothing is cached, so ordinary variation shows up: a VPN reconnect can change your exit server, your resolver set can differ between networks, and browser updates reset fingerprinting surfaces. If a single check flips between runs, run it twice more before treating it as a real change.
Is a perfect score enough to be anonymous?
No. Passing all four means nothing detectable leaks from your browser at this moment. Anonymity also depends on what you do while connected — signing into accounts, reusing usernames, or keeping an unusual browser setup will identify you regardless of a clean leak test. Treat the score as a baseline for the connection, not a verdict on your identity.

All tests run locally in your browser. No personal data is stored or transmitted to our servers.