Browser fingerprint test
Test which browser, screen, language, time-zone, and platform signals ordinary JavaScript can observe.
- JavaScript
- Waiting for browser…
Quick answer
The exposure report lists signals available through ordinary browser APIs, including the user agent, language preferences, platform, screen dimensions, time zone, processor-thread count, coarse device memory, cookie support, and Do Not Track preference. It intentionally does not turn those observations into a universal identity score.
Review browser fingerprint signals in their real context
This report demonstrates what ordinary JavaScript can read in this browser visit. It has no comparison population, long-term identifier history, or cross-site account data, so it cannot honestly calculate global uniqueness. Use it to understand categories of exposure and evaluate browser modes under controlled conditions.
Compare privacy modes
Keep the device and browser version stable, then note which signals are reduced or standardized by a built-in privacy mode.
Audit unnecessary exposure
Review whether extensions and custom settings add rare characteristics without assuming that hiding one field prevents correlation.
Explain fingerprinting
Use the visible fields as examples of combined signals while distinguishing uniqueness, stability, cookies, and authenticated accounts.
Follow the result into the next relevant page
Read browser fingerprinting guide because it explains combination, stability, and defenses; Read IP exposure guide because it separates browser signals from network metadata; Read VPN IP address check because it shows the different public-address layer.
How to interpret the output
A fingerprint depends on distinctiveness and stability across a comparison population. No single field has to be unique. Browser updates, resized windows, privacy defenses, and shared device configurations can change or normalize signals, while unusual combinations of extensions and spoofed values may make a browser stand out.
A reliable checking workflow
Review which fields are exposed, decide whether each is necessary for sites you use, and compare normal and privacy-oriented browser modes. Limit unnecessary scripts and extensions, keep the browser updated, and prefer built-in anti-fingerprinting protections that make users look similar instead of inventing a rare custom profile.
Key ideas behind browser fingerprint test
A browser fingerprint is a combination of ordinary signals. Its value to a tracker depends on how unusual the combination is and how long it stays stable.
Observable signals
Screen size, language, time zone, platform, and supported features can all add context.
Combination
Several common values may become distinctive when joined together.
Stability
Updates, privacy defenses, and normal device changes can make a previous combination less reliable.
Example: a rare customization can stand out
Changing a browser to report an unusual language, tiny window, and rare platform may hide some real values but create a less common combination. Built-in defenses often work by making many users look alike. This report has no global population with which to calculate uniqueness.
The boundary that matters
This page sees only signals available to this origin during this visit. It has no global comparison dataset, advertising identifier history, canvas test, or account information. A short list cannot prove that a browser is unique, anonymous, tracked, or safe from correlation.
How the main entities relate
| Subject | Relationship | Object |
|---|---|---|
| Browser API | exposes | a device or software signal |
| Tracker | combines | several observable signals |
| Anti-fingerprinting design | reduces | distinctive differences among users |