What is browser fingerprinting?
A fingerprint combines values your browser exposes—such as rendering, screen, language, and API support—into a diagnostic snapshot. Try a scan, then inspect what changed.
Browser evidence
Live fingerprint
Run browser checks locally and see the identifier this browser produces. The results stay on this page. One check, WebRTC, contacts a public STUN server to see which network addresses your browser exposes.
Read your first result
- Run the scan. It returns a diagnostic ID, collector coverage, and timing. The raw report is not uploaded from this page.
- Inspect individual values. Open the full checker for rendering, device hints, language, storage, and API support.
- Change one setting and rerun. Compare local scans to identify which observed fields changed.
Clearing cookies removes stored identifiers. It does not necessarily change rendering or other values a site can read. A fingerprint can also change without clearing any storage.
Choose a question to investigate
Did rendering change?
Keep a Canvas result, change one graphics or privacy setting, then rerun in that tab.
What does a privacy setting expose?
Inspect named resistance and consistency flags, then compare a second scan.
Does my preference reach the browser?
Change a system motion preference and verify the value returned by the browser.
What a fingerprint cannot establish
- Coverage is not uniqueness
- Coverage counts returned collectors. A complete scan can resemble many other browsers; an incomplete scan is not a privacy score.
- A matching ID is not a person
- Shared configurations can produce similar observations. A browser update, display change, or different API availability can change the snapshot.
- Heuristics are not proof
- Resistance flags and consistency checks are clues. Browser differences, accessibility settings, and privacy tools can all affect them.
Compare a protection setting
Use the same browser and change one setting at a time. Start with a default scan, change the relevant built-in setting, then rescan and compare fields. More returned values or a different ID alone do not tell you whether tracking became easier.
A VPN changes network routing, while browser signals such as fonts and rendering may stay the same. Use the IP tool for network context and the browser checker for local values. Keep privacy protections enabled when a check is unavailable.
What leaves this browser
A full scan includes a WebRTC request to Google STUN servers, which can observe your IP. The local collector report stays in this browser unless you explicitly use an API submission or comparison feature. The full checker saves sanitized local history that you can clear.
Population comparison is optional and sends only its disclosed comparison subset. IP lookups send the queried address to the API and its provider. Review data handling and your choices.
When a result is missing or keeps changing
Inspect the unavailable collector rather than guessing a value. Retry only that signal, keep the same display and settings for a comparison, and check the timing and status. A blocked API can be an expected outcome. It does not require disabling a protection or granting media permissions.
Find a signal’s method and limits