Browser Privacy Check

See what your browser leaks: fingerprint surface, exposed APIs, and privacy signal irony, all analyzed on your device.

Nothing runs until you press the button. Every probe below is collected and analyzed on this device: your files and inputs never leave your device.

Nothing has run yet

Press "Run privacy check" to collect every probe below from this browser and see what it reveals.

Related tools

What it does

Browser Privacy Check runs a set of fingerprinting probes in your browser, the same kind of signals tracking scripts use, and explains in plain English what each one reveals: your user agent, screen and hardware details, canvas and WebGL fingerprints, font list, WebRTC local IP exposure, and privacy signals like Do Not Track. It then adds up a rough entropy score across every probe that returned a value and classifies your fingerprint surface as low, moderate, or high.

How to use it

Run the probe collector panel on this page; it gathers each signal from your live browser and produces a small JSON report. That report is analyzed instantly into labeled rows grouped by category, plus flags for automation detection and WebRTC IP leaks. You can also paste a JSON report by hand if you already have one, for example one exported from another device.

Why this one

Panopticlick and AmIUnique compare you against a database on their server, which means your fingerprint has to leave your machine first. This tool never sends a single probe result anywhere: the analysis, the entropy scoring, and the flags all run in your browser, so the one thing being measured for leakiness does not itself leak.

FAQ
Is any of this data sent to you or anyone else?
No. The probe collector runs in your browser, the JSON report stays on your device, and the analysis on this page reads that JSON locally. Nothing is uploaded, logged, or sent to a server.
Why does blocking trackers sometimes make me MORE identifiable?
Most fingerprinting entropy comes from being unusual, not from being tracked. Turning on Do Not Track or Global Privacy Control is rare enough that it can narrow you down to a smaller group of browsers, and an unusual combination of blocked APIs can be its own fingerprint. Blocking helps against the specific signals you block, but a rare configuration is still a configuration.
How accurate is the entropy score?
It is a rough estimate, not a measurement. Each probe is assigned a fixed number of bits based on how much variation similar signals showed in older public fingerprinting studies, then the bits for whatever you actually collected are added up. Your real uniqueness depends on how many other visitors share your exact combination of values today, which no offline page can know, so treat the low, moderate, and high labels as a general sense of exposure rather than an exact number.

Keyboard shortcuts: press ? anywhere on this page to see them.