Browserleaks
One page per interface, with the raw values each one hands over.
BrowserLeaks scores nothing. It gives a page per web API — canvas, WebGL, WebRTC, fonts, audio, TLS, DNS — and prints what that API returns on your machine, next to the hash a tracker would store. It is the reference tool for checking what a change to a browser actually changed.
What it checks
- Canvas, WebGL and audio fingerprint hashes
- WebRTC addresses, including the local one
- Installed fonts and the font rendering fingerprint
- TLS, HTTP/2 and DNS details as the server sees them
How to read the result
Open the same page twice — in two browsers, or before and after a setting change — and compare the hashes. A value that moves between two visits from one machine is noise; a value that stays put is an identifier.
What it does not prove
A rare hash is not a problem by itself: every real machine is unusual in some way. What matters is whether the values are consistent with each other and whether they stay stable, which a single visit cannot tell you.
These tools are run by their own operators, not by us. Opening one sends your IP address and browser details to that site.
