How to interpret a Tor Browser fingerprint test

Updated October 17, 2026 · Independent guidance

Tor Browser aims to reduce how distinguishable its users are. A test may still read browser signals; that alone does not show that you are identifiable. This tool cannot measure the size of your anonymity set.

Check Tor Browser without chasing a score

1. Record the Tor Browser version and security level you already use.
2. Open the browser fingerprint test. Its automated local scan requires JavaScript.
3. If your security configuration blocks the scan, the explanatory content remains readable. There is no need to lower your security level to obtain a result.
4. If the scan runs, inspect the raw values and unavailable rows. Record them along with your settings so you can interpret later changes.

Why can reported values differ from my device?

Tor's official documentation explains that its defenses reduce variation across users. They include standardized user-agent values, limits on font enumeration and letterboxing to group window dimensions. Reported values therefore need not expose the device's exact underlying configuration.

What if canvas or another API is unavailable?

The report uses “Unavailable” when a value could not be read. That is a description of this attempt, not a diagnosis of a broken browser. Tor documents restrictions on canvas image extraction among its defenses. A blocked drawing output can prevent this test from producing a canvas digest while other rows remain readable.

Does a timezone warning mean Tor is leaking?

The site's consistency checks compare observations; they do not validate Tor routing. A difference between browser timezone and IP-derived timezone is not sufficient evidence of a leak. The network panel reports what this site's endpoint sees, and its location estimate is approximate.

The optional WebRTC check is a separate, user-initiated check using Google's STUN server. It is not required to read the local fingerprint results and is not a comprehensive Tor, DNS or network leak audit.

What should I compare between runs?

Compare individual rows while holding the browser version, security level and window conditions constant. If you change several conditions, you cannot isolate why the report changed. An identical digest does not establish identical users, and a different digest does not certify anonymity.

This site has no population database and cannot determine whether you blend in with other Tor users. It also does not inspect your circuit, test all network traffic or assess risks from signing into an account. Treat the output as one set of browser observations.

Read the results guide for field-by-field interpretation, or compare the testing approach in the Brave guide. This independent site is not affiliated with the Tor Project.