What websites see when you open a page
Inspect browser signals locally and compare them with network observations. IP location uses a server lookup; WebRTC may contact a STUN server.
Reports are assembled locally. Optional usage analytics require your consent.
Reading your browser…
Full report
37 checks in 6 groups. Click any row to see why it matters.
Network
What the server sees before any script runs
Browser & identity
Who the browser claims to be, three ways
Hardware
Screen, CPU, memory, GPU as the browser reports them
Rendering fingerprints
Pixel- and sample-level signatures, and whether they behave like real ones
Locale & time
Does the clock agree with the IP?
Automation & privacy
Signs of a driven browser, plus privacy switches
Your fingerprint ID· computed locally from the stable signals above, never stored
FAQ
What is a browser fingerprint?
A set of characteristics a site can read without asking — screen, GPU, fonts, timezone, how your browser draws an image. Combined, they identify a browser far better than a cookie, and they survive clearing cookies.
What does the consistency score mean?
Risk engines rarely care about any single value. They check whether the values agree with each other: does the timezone fit the IP, does the GPU fit the OS, does WebRTC agree with HTTP. The score counts those cross-checks. 100 means every check agreed.
Does this page store my data?
No. Every check runs in your browser and the result stays on this page. The only server call looks up the location of your IP so the timezone check can run. The WebRTC test sends one binding request to a public STUN server.
What can I check in the Lab?
The Lab checks your IP address and WebRTC results, browser identity, hardware, rendering, timezone, language and automation signals. Each result links to an explanation. Unavailable measurements are marked separately and do not count as successful checks.