Self-fingerprint inspector other environment
The signals a tracker could read to identify your browser, shown only to you and computed only here.
What 'other' means here
This tool lives in the green room because its input is your BROWSER AND DEVICE - the output legitimately differs for every visitor, so there is no fixed correct answer for golden vectors to assert. It is the privacy thesis made visible.
Click below and this page computes, in your browser, the signals a fingerprinting script would read. This tool sends none of it anywhere - the reading is shown only to you.
Every signal is computed in your browser and displayed here only. Nothing is uploaded, stored, or compared against anyone else.
Fingerprinting does not need cookies. A script can combine your user agent, screen geometry, installed fonts, and the exact way your GPU renders a hidden canvas into an identifier that follows you across sites without any stored ID. This tool computes those same signals so you can see the surface for yourself.
This tool runs locally and shows the reading only to you - it uploads and retains nothing. But that is a fact about the tool, not about the signals, and the difference is the real lesson. Your user agent and the other HTTP request headers, along with your TLS handshake (the basis of JA3 and JA4), are already sent to every server you connect to; passive fingerprinting is just servers reading what you send. Whether a given server keeps it is up to that server. The other signals here - the canvas and WebGL hashes, the font probe, the screen metrics - are not in the request at all; they sit in your browser until a script on a page you load reads them and sends them back. So the surface splits in two: what you broadcast on every connection, and what a script can collect if you let its page run.