An anonymity check reports what a service can observe during a particular browser visit. It may show the public IP address, a network or VPN classification, browser properties and, if the test supports it, characteristics that can make the browser recognizable. It cannot certify that a person is anonymous across other sites, logged-in accounts, applications or future visits.
Use the public checker directory to choose a test, then read the result by what was measured. If your practical question is whether your VPN route works, follow the separate IP, DNS and browser checklist.
Four different observations behind an anonymity check
| Observation | What it can tell you | What it cannot establish |
|---|---|---|
| Public IP and network | The address and approximate network visible to that service now | The path taken by every application on your device |
| VPN, proxy or relay label | Whether the provider classifies the current address as a privacy network | Whether the connection belongs to a particular person or is abusive |
| Browser characteristics | Settings and properties this test's browser can expose | A universal identity shared by every browser and site |
| Account state | Whether you logged in to the tested service | Whether you are anonymous to that service after login |
The categories are intentionally separate. A VPN can change the visible public address while a browser still presents distinctive properties. The Electronic Frontier Foundation's Cover Your Tracks is a browser tracking and fingerprinting test; EFF explicitly says that it does not measure every tracking technique or protection. It is not a test of every application's VPN route.
An IP address is also an imperfect stand-in for a user. Apple explains that a Private Relay address may be shared by multiple people in the same area. A checker that calls such an address a relay has classified a connection, not linked all of those people into one account.
Run a repeatable check without overreading the result
- Record the browser, network, time and public IP before changing anything. Do not publish the address or account details in a public forum.
- Run the same checker with the VPN or privacy service disconnected and connected. Note the observed address, provider label and any browser details.
- Repeat in the actual browser or application that matters. If a VPN uses split tunneling, a browser result does not describe an excluded application.
- If you see an unexpected WebRTC address, identify whether it is a private local address, a relay or a publicly routable address before calling it a leak. MDN's WebRTC candidate reference explains why candidate addresses require care.
- Recheck after reconnecting or switching networks. A single snapshot cannot describe later sessions.
For a network operator, the same sequence is a way to compare detection tools, not a benchmark of their production accuracy. Our VPN detection comparison separates IP lookup products from tools that add device and account context. The proxy API guide covers the implementation details behind a real product decision.
Why a clean-looking check is not a safety guarantee
An empty proxy flag can mean the observed IP was not classified, that the provider lacks a category on the tested plan, or that the address changed after its last data update. It does not establish that no other signals exist. Conversely, a VPN flag is compatible with legitimate work, travel and privacy use.
For abuse prevention, examine the event and its context. A signup from a shared relay is different from repeated signup attempts linked by device or account history. A visit-level risk result can combine network and identity evidence, while an IP-only label describes the connection. See the IP fraud score explainer before treating those two numbers as interchangeable.
If you need to validate your own privacy configuration, use several tests for their stated purposes: route, DNS, browser exposure and account login. If you are choosing a detection vendor, run a pilot with legitimate corporate VPN and Private Relay users as well as known proxy connections. Our false-positive guide shows how to record customer impact.
FAQ
Can an anonymity checker prove that I am anonymous online?
No. It reports observations from one test and cannot account for every site, logged-in account, application or later visit. Read its scope and repeat the test where your real traffic runs.
What is the difference between an IP check and a browser fingerprint test?
An IP check describes a network address and its classification. A browser fingerprint test looks at characteristics exposed by the browser. EFF's Cover Your Tracks focuses on tracking and fingerprinting, while a VPN checker focuses on the observed connection.
Does a VPN change my browser fingerprint?
A VPN changes the route and usually the visible exit IP; it does not automatically replace every browser property. Check browser exposure separately and avoid reading one test as proof about another.
Why does a checker still recognize my VPN?
The exit address may be known to a VPN detection provider. Recognition does not mean the VPN failed to route your tested request or that the checker learned the original public IP. Compare the observed route with your VPN's documented behavior using the VPN checklist.
Sources
Sources reviewed October 21, 2026.