Open the page and let the verifier run a clean scan automatically.
This page immediately collects browser-visible fingerprint signals, combines them with server-observed headers and TLS metadata, and explains which parts of the session look coherent, spoofed, proxied, automated, or internally inconsistent. The default path is zero-input: just visit the page and let it analyze the session.
Automatic Clean Scan
The verifier runs automatically on load and re-runs with a clean no-store request path whenever you press the button below. The page also clears same-origin cache and storage state before each scan so previous visits are less likely to contaminate later checks.
Advanced Overrides (Optional)
The normal workflow needs no pasted input. These fields are only for debugging, replaying a sample report, or mixing in upstream data such as forwarded JA3 / JA4, ASN, or a claimed host baseline.
What The Automatic Scan Uses
1. Browser JavaScript signals such as UA, hardware, canvas, audio, WebGL, WebRTC, and screen traits.
2. Server-observed request headers, IP, and TLS details.
3. JA3 and JA4 when the app terminates TLS directly or an upstream forwards them.
4. Browser transport observations such as HTTP/1.1, HTTP/2, or HTTP/3 usage.
5. Optional advanced overrides only if you need to inject claimed host or proxy intelligence.