Diagnostic 01 / Fingerprint
What this browser tells a fingerprinter.
Eight collectors, each hashed separately, then folded into one composite value. Nothing runs until you ask for it.
- Signals
- 8 collectors
- Output
- SHA-256 composite
- Executes
- In this browser
- Stored
- Nothing
01Scan
The reading
Run the scan.
The collectors run concurrently, so a full pass takes about as long as its slowest signal rather than the sum of all eight. Font probing and canvas readback are the two you might notice.
This measures canvas, WebGL, WebGPU, audio, installed fonts, screen geometry, client hints and automation tells in this browser. Nothing leaves the page.
Nothing has been measured yet.
A privacy diagnostic that fingerprints you before you ask has already lost its own argument, so this page waits. When you press the button, three things happen.
- 01Eight collectors run at once, each returning either a value or a stated reason it could not produce one.
- 02Every available signal is hashed on its own, so you can see which one moves when you change a setting and run again.
- 03The eight results are folded into one composite hash. A withheld signal contributes the reason it was withheld, because refusing a signal is itself something a site can observe.
02Reading
Interpretation
What the number does and does not tell you.
A fingerprint is only interesting relative to a population, and a page running inside one browser cannot see one. Three things worth knowing before you draw a conclusion.
- 01
Uniqueness and stability are different properties
A hash that changes on every visit is not anonymous, it is unusual. A hash that never changes is trackable. What a fingerprinter wants is a value that is stable across sessions and rare across users, and only the first half of that is measurable from inside a single browser. - 02
Withholding a signal is itself a signal
Blocking canvas or masking the GPU string moves you out of the default population and into a much smaller one. That can be the right trade, but it is a trade rather than a win, which is why the composite hash on this page counts the refusals. - 03
These digests will not match another checker's
Every checker draws a slightly different scene, probes a different font list and hashes a different set of fields. Comparing a hash from here against a hash from elsewhere tells you nothing. Comparing two runs from here tells you something.
These are the signals VeilBrowser controls per profile, so two profiles on one machine do not share them.