Recognized legacy pattern
Label a tracked visit only when its browser and screen inputs match one of the narrow patterns supported by the current parser.
Limited privacy-browser heuristic
Understand the limits of Tor Browser detection
Hitsteps can label a narrow set of historically recognized Tor Browser patterns. Modern, modified, or otherwise unrecognized Tor visits can remain classified as an ordinary browser, so the result is context rather than complete coverage.
- Flag only the narrow legacy browser patterns currently recognized by Hitsteps
- Expect modern or modified Tor Browser visits to remain unclassified
- Avoid asserting an underlying operating system from spoofed browser details
What it does
Know what the current heuristic can and cannot recognize
Privacy browsers deliberately standardize identifying details, and their releases evolve. The current Hitsteps parser can label only its recognized patterns; it must not be treated as authoritative Tor traffic measurement.
Hitsteps Tor Browser detection is a legacy browser-and-screen heuristic for a small set of recognized patterns. It is not a live Tor exit-node check, it does not cover every Tor Browser release, and it cannot reveal who a visitor is or why Tor is being used.
Unknown device details
Avoid relying on an apparent browser version or operating system when privacy software can standardize or spoof those values.
Journey context
Review the same permitted page and action data as other tracked visits without using the Tor signal as a behavioral verdict.
Product proof
Hitsteps is a maintained analytics product, not a throwaway script.
Use it when you need live visitor context, practical installation routes, and action tools around the traffic you already have.
Maintained for real websites
Hitsteps has kept evolving across website platforms, browser changes, analytics shifts, and store workflows.
Works where your site already lives
WordPress, Shopify, Wix, Google Tag Manager, HTML, CMS, commerce, browser, and desktop setup paths are documented from one hub.
From tracking hit to next action
Live dashboard, visitor profiles, heatmaps, chat, triggers, uptime, reports, and alerts stay connected after tracking is installed.
Practical context
Tor use does not identify a person or motive
People use Tor for privacy, safety, research, access, testing, and many other reasons. A possible Tor signal neither proves abuse nor reveals the visitor behind the connection.
The current heuristic does not claim coverage of modern Tor Browser releases. Evolving browser values and screen behavior can create missed, uncertain, or incorrect classifications.
Workflow
How to interpret a possible Tor visit
Treat the flag as an inference
Recognize that the legacy heuristic has narrow coverage and becomes less complete as Tor Browser and mainstream browser releases change.
Leave unsupported attributes unknown
Do not report an underlying operating system, precise location, or stable identity when the available data cannot support it.
Review actual tracked behavior
Use requested pages, completed actions, and direct customer communication rather than judging a visit from the privacy signal.
Apply neutral security controls
Base fraud or abuse decisions on rate limits, authentication, transaction evidence, and concrete behavior that applies consistently to all visitors.
Use cases
Responsible uses for a possible Tor signal
Browser report accuracy
For a recognized legacy pattern, avoid presenting the standardized user agent as a confidently identified mainstream browser and operating-system combination.
Privacy-aware support
Understand that approximate location and device details may be unavailable when assisting a visitor who contacts you directly.
Traffic quality review
Compare actual actions and outcomes for flagged visits without assuming that use of a privacy network is harmful.
Questions and answers
Tor Browser Detection FAQ
Clear answers about what this feature reports, how to use it, and where its limits are.
Can Tor Browser detection identify the visitor?
No. A possible Tor signal describes technical context available to a tracked visit. It does not reveal the person's identity, original network address, precise location, or reason for using Tor.
Is Tor Browser detection always accurate?
No. Hitsteps currently recognizes only a narrow set of legacy browser-and-screen patterns. Modern, modified, or otherwise unmatched Tor Browser visits may not receive the label, and a match should still be treated as an inference.
Should I block every visit flagged as Tor?
A Tor signal alone is not evidence of abuse. Use neutral controls based on concrete behavior, authentication, rate limits, transaction risk, and applicable policy rather than privacy-tool use by itself.
Keep exploring
Related Hitsteps features
Connect this report with the surrounding visitor, acquisition, and workflow context.
See it on your own website
Start free
Turn tor browser detection into a working analytics workflow
Create a free account, install the Hitsteps tracking code, and confirm your first visit before choosing the plan that fits your traffic and reporting needs.