ISP address visible
Checkingweight
- What was measured
- measuring
- How to improve
- waiting
One number for how exposed this browser and connection are right now, built from the tests on this site: VPN detection, DNS and WebRTC leaks, IPv6, time zone and blocklists. Every point you lose comes with the fix that gets it back.
Running the checks. Every deduction below names the test, the weight and the fix.
Checking
ISP address visible
Checkingweight
DNS leak
Checkingweight
WebRTC leak
Checkingweight
IPv6 leak
Checkingweight
Time zone mismatch
Checkingweight
Blocklist listing
Checkingweight
Browser fingerprint
Checkingweight
Tell the page whether you are on a VPN (the checks mean different things with and without one), then run the tests. A score of 90 or more means nothing we can detect gives away more than your public address itself; 70–89 means one thing to fix; 40–69 means a leak or a listing that websites can see; below 40 means the VPN or proxy you rely on is not doing its job.
Each check is one of the site's tools run with the same settings, so the detailed result is one click away.
Is the address websites see a home or mobile ISP, or a VPN, proxy, Tor or hosting address? In VPN mode an ISP address is the biggest deduction, because it means the tunnel is not carrying your traffic. Details: proxy and VPN checker.
Which resolvers handled lookups for our unique test hostnames and whether any of them belongs to your ISP or forwarded your real network. Details: DNS leak test.
Whether your browser's STUN result reveals a public address different from the one websites see. Details: WebRTC leak test.
Whether an IPv6 address from a different network than your VPN is reachable. Details: IPv6 test.
Whether your device's clock disagrees with the time zone of your address — a classic giveaway that the address is not where you are.
Whether the address is on any of the ten DNS blocklists we query; a listing makes sites treat you as suspicious regardless of what you do. Details: IP blacklist check.
How unique the combination of your browser's properties is. The browser fingerprint test ships with an entropy estimate first; the score will include it once we have enough anonymous samples to measure real uniqueness.
The fix list under the score is ordered by points. Typical items: enable the VPN app's DNS leak protection and kill switch; set the browser's WebRTC policy to disable non-proxied UDP; enable the VPN's IPv6 protection or disable IPv6 while tunneled; set the device clock to the VPN location's time zone, or pick a server in your own time zone; request delisting from a blocklist (the removal guide has the steps). Re-run the test after each change — the score updates immediately.
The score starts at 100 and subtracts fixed amounts per finding, with no hidden weighting. In VPN mode: −40 ISP address visible, −25 DNS leak, −20 WebRTC leak, −15 IPv6 leak, −10 time-zone mismatch, −10 blocklisted. In normal mode: −10 local network visible through WebRTC, −10 time-zone mismatch, −20 blocklisted; the fingerprint check is an estimate and is not deducted in this version. Bands: 90–100 excellent, 70–89 good, 40–69 fair, 0–39 poor. The same formula is published on the methodology page, and the what websites can see about you page shows the raw data behind every deduction.
Reduce what you reveal rather than chasing invisibility: use a VPN that passes all four leak tests here, keep the browser's WebRTC policy restricted, block third-party cookies, use a browser with tracking protection and avoid logging into accounts you want kept separate. A high score here means the network side is in order; cookies and logins are the other half.
A common framework lists information privacy (your data), communication privacy (your messages), territorial privacy (your space) and bodily privacy. This page measures the first two on the network level: what your connection and browser reveal, and whether your DNS and traffic stay inside the tunnel you chose.
Our tools check your connection, not other websites. To check a site, look it up on a reputation service such as Google Safe Browsing or VirusTotal, verify the certificate, and be suspicious of unexpected downloads. Our HTTP headers checker shows what a server sends, which helps with technical analysis but is not a malware verdict.
Rankings change with every release, so we do not keep one. What matters more than the brand is the configuration: cookie and tracker blocking enabled, WebRTC restricted, fingerprinting protections on. Run this test and the browser fingerprint test in the browser you actually use.
Formula: /methodology#privacy-score (fixed weights, two modes, unavailable checks excluded). Inputs: the lookup service (connection type, blocklists), our DNS zone and STUN server (DNS, WebRTC, IPv6), your browser clock and properties.