Free network diagnostics
See the browser characteristics any website can read about you. The page reads roughly 40 distinct fingerprint signals plus two active demonstrations — all locally, with zero network requests after the page loads. Nothing is stored, nothing is transmitted, and the page has no memory of you between visits.
Result
Reading browser signals…
Collecting fingerprint surfaces from your browser. No network requests are made.
Reading browser signals…
These are two classic fingerprinting techniques actually running on your browser right now. They are computed locally and discarded. Nothing leaves your device.
The canvas hash above is the first 16 hex characters of a SHA-256 of a small drawn canvas. Real fingerprinters use the full hash to recognize you across sites. If the hash changes on every Re-run, your browser has canvas randomization enabled (Tor Browser, Firefox with privacy.resistFingerprinting) — that's excellent. If the WebGL fields say “restricted by browser”, your browser is hiding the driver string — also excellent.
What this shows (and doesn't)
This page reads fingerprint signals from your browser via standard JavaScript APIs. Each signal alone doesn't identify you, but together they form a profile that fingerprint trackers can use to recognize you across sites — even without cookies.
This page does not compute a uniqueness score (we have no comparative database), does not store the canvas hash or WebGL renderer string, does not transmit anything to a server, and does not track you across visits. For a real comparative score against millions of other browsers, see the EFF's coveryourtracks.eff.org ↗ — they run the comparative database that this kind of score requires. For maximum protection, use Tor Browser or Brave with Shields up.
How this page works
Unlike the other diagnostics tools in our cluster, this page makes zero network requests after the page loads. Every signal shown was read directly from your own browser via the navigator, screen, matchMedia, and Web Crypto APIs. The canvas hash is computed locally with SubtleCrypto.digest and discarded. The WebGL renderer string is read from a temporary canvas context and discarded. Nothing leaves your device.
Everyday Tools Hub does not log, store, or transmit any of the information shown on this page. The page has no cookies, no localStorage writes, and no memory of you between visits.
See which browser characteristics any website can read about you, with zero network requests after the page loads.
These cover what a browser fingerprint actually is, why this page doesn't pretend to compute a uniqueness score, and what concrete steps reduce your fingerprint surface.
FAQ
A browser fingerprint is the combination of properties your browser exposes to websites — your user agent, screen size, timezone, language, hardware details, supported APIs, and so on. None of these uniquely identify you on their own, but together they form a profile that tracking systems can use to recognize you across sites, even without cookies. This page reads the same signals that fingerprinting libraries read, so you can see them yourself.
FAQ
No — and we want to be honest about that. Computing a true uniqueness score requires comparing your signals against a database of millions of other browsers. We don't have one. What this page can honestly show is the count of distinct fingerprint signals your browser exposes, plus the actual values for each one. For a comparative score against a real research database, see the EFF's coveryourtracks.eff.org — they run that database and we don't.
FAQ
No. This is the only diagnostics tool in our cluster that makes zero network requests after the page loads. Every signal shown is read directly from your own browser via the navigator, screen, matchMedia, and Web Crypto APIs. The canvas hash is computed locally and discarded. The WebGL renderer string is read locally. Nothing is stored, nothing is transmitted, and the page has no memory of you between visits.
FAQ
It's an example of a classic fingerprinting technique. Your browser is asked to draw a small set of text and shapes to a canvas; the resulting pixels are hashed. Different browsers, operating systems, and graphics chips produce subtly different pixel patterns, so the hash is stable on your machine but varies across machines. We show only the first 16 hex characters as a demonstration — fingerprinters use the full hash to track users across sites. We compute it, show it, and discard it.
FAQ
WebGL exposes a string identifying your graphics hardware and driver — for example, 'ANGLE (Apple, Apple M2 Pro, OpenGL 4.1)'. It's one of the highest-information single signals on the open web and a popular fingerprinting input. Some privacy-focused browsers (Tor Browser, Firefox with privacy.resistFingerprinting, Brave with Shields up) hide or spoof this string. If you see '(restricted by browser)' or a generic value, your browser is doing the right thing.
FAQ
The most effective changes are: use a hardened privacy browser (Tor Browser is the gold standard, Brave with Shields up is excellent for everyday use, Firefox with privacy.resistFingerprinting is good), avoid installing browser fonts and extensions you don't need, keep your browser updated so you blend in with the latest baseline rather than standing out as old, and consider blocking JavaScript on sites that don't need it. There is no perfect solution — fingerprinting is fundamentally a side effect of browsers being useful — but each step shrinks your unique surface.
Explore other utilities in the Everyday Tools Hub library.