Exposure Report
One click runs every passive check on this site. Nothing is stored, and no score is made up.
The email breach check, the registration lookup and the Link Checker send data to others and need your consent, so they are not part of this run: see the Data Breach Check, IP Leak Test and Link Checker pages.
Learn more
Guide and answers to common questions about Exposure Report
What the Exposure Report is
Most of the tests on this site answer one question each. Is my IP address leaking? Does WebRTC show my real address? Is my browser out of date? The Exposure Report asks all of them at once. You press one button, the page runs every check that needs no input and no consent from you, and you get one page: what was seen, a plain rating for each area, and a link to the full test where you can read the detail.
It is meant for the first visit and for a quick re-check. Run it once on your normal connection, then again after you turn a VPN on, change a browser setting or install a blocker, and see what moved. The report does not replace the single tests. It shows you where to look, and each area links to the test that explains it in full.
What runs when you press the button
Nothing runs while the page is open and you only read. The checks start when you press Run all checks, so a visitor who just wants to read this guide, or a search engine crawler, triggers no requests at all. Before you press, the page lists exactly who will be contacted. The eight areas then run side by side, each with its own time limit, and they fill in as they finish. If one check fails or hangs, only that area says so; the rest of the report still arrives.
- Your address: the public IPv4 and IPv6 address that websites see, the network and place each one belongs to, and whether the two belong to the same network.
- WebRTC: whether your browser hands a page a public address that is different from the one websites see.
- VPN and Tor hints: whether your address is a Tor exit or sits in a hosting or VPN network, and whether your time zone and browser languages fit the country of your IP address.
- IP reputation: whether your address is on the blocklists our server keeps.
- Browser up to date: your browser version against the current stable release.
- Fingerprint: how many of the strongest identifying signals a page can read, and whether your browser adds noise to canvas.
- Tracker blocking and cookies: whether a content blocker stops bait files on our own site, and whether third-party cookies are blocked.
- What the browser reveals: sensitive permissions granted to this site, motion sensors that answer without asking, and the privacy signals your browser sends.
How each area is judged
Every area gets one of four ratings. Good means the check ran and found nothing to worry about. Warning means something to look at that is not a leak by itself. Problem means a leak or a listing. Not checked means the check could not run or could not tell, for example because a list was not loaded yet or a request was blocked. Not checked is never shown as good, because a check that did not happen proves nothing.
Your address is rated good when it can be looked up, because every site sees your address and that is how the internet works. It turns into a warning when your IPv4 and IPv6 addresses belong to different networks, which is what a VPN that tunnels only IPv4 looks like. WebRTC is a problem only when it shows a public address that websites do not already see. A public address that matches the one sites see is not a leak, and WebRTC switched off counts as good.
The VPN and Tor area is a warning when a hint is found: a Tor exit address, a hosting or VPN network, a time zone that does not fit the country of your address, or languages that point to another country. These are hints a website could use to guess that you use a VPN or are not where your address says. Without a VPN, a mismatch can be perfectly normal, for example when you travel, so it is a warning and never a problem. IP reputation is a problem when your address is on a serious list, a warning on a weaker one, and good when it is on none of the lists that could be checked.
The browser area compares your version with the current stable release: the same major version is good, one behind is a warning, more than one behind is a problem. For Safari and a few others no public feed exists, so the area says it could not tell. The fingerprint area is good when your browser adds noise to canvas or when at most one of the three strongest signals, canvas, graphics card and fonts, can be read, and a warning otherwise. It is never a problem, because this page cannot measure how rare you are.
Tracker blocking is good when at least one bait file was blocked or third-party cookies are blocked, and a warning when neither was seen. The last area is a warning when a sensitive permission is granted to this site or a motion sensor answers without a prompt. Do Not Track and Global Privacy Control are shown, but they do not change the rating, because nobody has to honour them.
The overall rating at the top
The rating at the top follows the worst area. One problem makes the whole report a problem, whatever else is good. If there is no problem but there are warnings, the report is a warning. If every area that ran is good but some could not be checked, the report says so in plain words, with the number of areas that could not be checked, and it is not shown as good. Only when all eight areas ran and found nothing does the report say that no problem was found, and even then it adds that this is not a guarantee.
Why there is no privacy score
You will not find a number such as 73 out of 100 here. A score looks precise, but every weight behind it is a guess. Is a leaking WebRTC address worth fifteen points or twenty? Is an old browser worse than a readable canvas? Nobody can measure that, and two tools that disagree on the weights would give the same person two different grades. A score also invites you to chase the number instead of fixing the thing that matters. The report gives plain statements about what was seen, so you can decide what is worth your time.
What the report cannot see
The report covers what a web page and our server can observe passively. It does not look at your email address, so it cannot tell you about data breaches. That check needs your address to be sent to a breach service, and it only runs after you tick a consent box on the Data Breach Check page. The same goes for the registration record of your address on the IP Leak Test page and for the Link Checker: they send data to others, so they stay separate and ask first.
It does not test which DNS servers your device uses. A DNS leak needs a dedicated test, and the DNS Leak page explains what it can and cannot show. It cannot see tracking protection that works by domain, such as Brave Shields, Firefox Enhanced Tracking Protection or a DNS filter, because the bait files it uses live on our own domain. A pattern-based blocker such as uBlock Origin is visible to it; the others are not, and the report says so when it sees no blocking. It cannot see malware, an unsafe Wi-Fi network, your passwords, or what apps on your phone do. And it knows nothing about your accounts.
Some results are best guesses. Location comes from a free database that is accurate to the country and often to the city, but not to the street. The list of VPN and hosting networks is not complete: a VPN with fresh addresses may be known to paid detection services and still pass here. A browser older than the release feed we read may be rated one version behind when it is only waiting for a restart.
Your privacy while you use it
The report runs in your browser and nothing is stored. There are no accounts, no analytics, and no copy of the result on our side. The calls that leave your browser are the ones the single tools already make and the privacy policy names. Your browser asks our own server for the location of your address, the blocklists, the VPN and Tor signals and the current browser versions. It asks the public address services icanhazip.com and ipify.org for your address, as any website could. The WebRTC check contacts Google and Cloudflare STUN servers, because that contact is the thing being tested. The third-party cookie check loads a small page from cookie.exposy.workers.dev, this site’s own test page on Cloudflare Workers. The page lists these before you start.
The Copy as text button builds a plain text report from what is on the screen and puts it on your clipboard. It contains your IP address, the network it belongs to and the version of your browser. Treat it like any other personal data: take care where you paste it, for example in a public forum or a support ticket, and remove the address first if you only need to show someone the ratings.
What to do with the result
Start with the worst area and open its full test. A WebRTC problem has a fix in your VPN app or your browser settings, and the WebRTC page shows which. An old browser is fixed by updating it and restarting. A listed address is usually the address of your provider or VPN, so it is a reason to try another server rather than to worry. Warnings in the fingerprint and tracker areas are best answered with a browser that limits them, or with a content blocker. Run the report again afterwards to confirm that the area changed.
Frequently asked questions
Does the Exposure Report store or send my results?
No. The report is built in your browser and nothing about you is stored on our server. The only requests that leave the page are the ones listed above the Run button: our own server, the two public address services, the STUN servers for WebRTC and the second domain for the cookie check.
Why does it not give me a score out of 100?
Because the weights behind a score are guesses. The report gives a plain rating per area and an overall rating that follows the worst area, so you can see exactly what is wrong and where.
What does "not checked" mean?
The check could not run or could not tell, for example because a request was blocked, a list was not loaded yet, or your browser does not offer the information. It is never counted as good, and the overall rating says how many areas were affected.
Can it tell me whether my email was in a data breach?
No. That check has to send your address to a breach service, so it lives on the Data Breach Check page behind a consent box. The report links to it instead of running it for you.
Why did I get warnings with a VPN turned on?
Most likely the hints. A VPN address often sits in a hosting network, and the VPN cannot change your time zone or browser languages. Set your system time zone to the VPN location and put the VPN country language first to reduce them, or accept them if you only need privacy from your provider.
Does it see my DNS servers?
No. DNS leaks need their own test, which is on the DNS Leak page. The report covers your address, WebRTC and the other areas listed here.
Is it safe to share the copied text?
It contains your IP address and browser version, so share it only with people you trust, or delete those lines first. It holds no cookies, passwords or personal files.