Privacy tools
14 tools that run in your browser. Nothing to install, nothing uploaded.
See what your browser reveals to every site you visit — your fingerprint, WebRTC address exposure, and the signals that identify you without a single cookie. These tools compute everything locally and store nothing: a page that collects your fingerprint to warn you about fingerprinting, then keeps it, would be indefensible. They are also honest where competitors are not — a clean WebRTC result covers WebRTC only, and no tool can tell you how "unique" you are without a population to compare against, so this one does not pretend to.
- Ad Blocker DetectorSee the exact technique sites use to detect your ad blocker — without being nagged by it.
- Audio FingerprintSee the audio-stack fingerprint your browser produces — computed silently, never played.
- Bot / Automation SignalsSee the automation signals your browser reports — and why none of them proves anything.
- Fingerprint Uniqueness ScoreSee the signals that identify your browser without a single cookie.
- Storage InspectorSee exactly what this site has stored on your device — and why it cannot see any other.
- Canvas Fingerprint ViewerSee the canvas fingerprint your browser hands to any site that asks.
- DNT / GPC Signal CheckSee whether you are sending Do Not Track or GPC — and why only one of them matters.
- Font FingerprintSee which fonts a site can detect on your machine, and why that identifies you.
- Incognito Mode DetectorCheck for private browsing — and see why browsers deliberately broke this test.
- Language / Locale LeakSee what your language settings reveal — including through a VPN.
- Referrer ViewerSee what the previous page told this one about where you came from.
- Timezone vs IP ConsistencyCompare your browser's timezone against your connection — the cheapest VPN check there is.
- WebGL Fingerprint / GPUSee your GPU vendor, renderer and the WebGL limits any site can read.
- WebRTC Leak TestCheck whether WebRTC is revealing an address your VPN is meant to hide.
Fingerprinting does not need a cookie
Blocking cookies stops one identification technique and leaves a large one untouched. Every page you visit can read your screen dimensions, timezone, language, installed fonts, hardware concurrency, graphics renderer string and the exact way your browser rasterises a canvas or renders audio — and the combination is often unique enough to recognise you across sites with no stored state at all. That is what these tools show you: the actual signal your browser is broadcasting right now, rather than a general warning that fingerprinting exists. Seeing your own values is usually more persuasive than any explanation of the technique.
What a VPN does and does not hide
A VPN changes the address a site sees and encrypts traffic between you and the exit point. It does not change your timezone, your fonts, your screen size, your language settings or your canvas rendering, so a fingerprint follows you straight through the tunnel. It also does not stop WebRTC from exposing a local or real address if the browser is configured to allow it, which is the specific leak the test here checks for — and a leak that was widespread enough that browsers and VPN clients both had to change behaviour to contain it.
Honest limits on a fingerprint report
Two claims are common on pages like these, and both are unsupportable. The first is a uniqueness percentage — telling you that you are one in a hundred thousand requires a population to compare against, and any site quoting a figure is either using a small self-selected sample of its own visitors or making it up. The second is an all-clear: a WebRTC test that passes has cleared WebRTC and nothing else. These tools also refuse the obvious hypocrisy of collecting your fingerprint to warn you about fingerprinting and then keeping it — the values are computed and displayed locally, and stored nowhere.
Frequently asked questions
Does blocking cookies stop me being tracked?
It stops one technique and leaves fingerprinting untouched. Your screen size, timezone, language, fonts, hardware concurrency, graphics renderer and the precise way your browser draws to a canvas combine into a signature that is often unique, with nothing stored on your machine at all. That is why clearing cookies or using a private window changes far less than people expect — the fingerprint is recomputed identically each time.
Does a VPN hide my browser fingerprint?
No. A VPN changes the IP address a site sees and encrypts traffic to the exit point. It does not change your fonts, screen dimensions, timezone, language settings or rendering behaviour, so the fingerprint passes straight through the tunnel unchanged. A VPN is genuinely useful against network-level observation and IP-based tracking, and it is not an answer to fingerprinting. Anti-fingerprinting requires browser-level defences, which is a different tool for a different problem.
Why will you not tell me how unique my fingerprint is?
Because an honest uniqueness figure needs a large, representative population to compare against, and this site does not have one. Any page quoting you a one-in-so-many number is either measuring against its own self-selected visitors — people who went looking for a fingerprint test, which is not the general population — or inventing it. Showing you the actual signals your browser exposes is the part that can be done truthfully.
Are my fingerprint values stored after the test?
No. Collecting a fingerprint in order to warn you about fingerprinting and then keeping it would be indefensible, so the values are computed and displayed in your browser and never transmitted or persisted. Reloading the page recomputes them from scratch. If you want to keep a record for comparison, copy the results yourself — nothing is retained here to come back to.