Read browser signals
The report lists values a normal page can access, such as language, screen size, and timezone.
Browser privacy check
Review the information this page can read from your browser.
The report stays on this device
Running the report makes no extra request, and your values are not compared against other visitors.
Report
Run the exposure check
The report reads browser and device properties that any page can already reach. Running it does not change them, and closing the tab discards the result.
What this browser reports
No checks run yet.
Reading it
What the values mean
- Common values, such as a popular screen size, are shared by millions of people
- Uncommon combinations, such as an unusual window size with a rare time zone, narrow the field
- A graphics renderer name can narrow the field, so the report shows it without creating a canvas hash
- Blocking one signal rarely helps, because the others still agree with each other
This is a demonstration, not a defence Seeing the values does not hide them. Reducing fingerprinting needs a browser that normalises these signals, or a network that many people share.
How fingerprinting works
A cookie can be deleted. A profile built from dozens of small, stable details is harder to reset, because each detail looks harmless on its own. The report lists the ones a page can read without asking permission.
What usually gives you away
An uncommon screen resolution, a rarely used language combination, an unusual graphics renderer, and a time zone that does not match your apparent location. Individually these are ordinary; together they can stand out.
What helps
Use a mainstream browser on a mainstream device and keep it updated, so your values look like everyone else's. Resist installing dozens of extensions, which change the very signals being measured. For anything that matters, separate your identities instead of trying to scrub one of them.
How it works
Keep the report here
The values are assembled in this browser and are not saved to your account or a visitor history.
Review what stands out
Use the explanations to understand exposure without treating any single value as proof of tracking.
Is my report sent to the server?
No. The values are read and displayed in the page. There is no upload, and no comparison against other visitors, because that comparison would need a server and would defeat the purpose.
Does the "do not track" setting help?
The report shows whether your browser sends the signal. Whether it is respected depends on the site you visit, so treat it as a request rather than a control.
Why do graphics details matter?
Browsers can expose a graphics vendor and renderer through WebGL. This report lists those names when available, but it does not draw and hash a canvas or turn the values into an identifier.
Can I stop fingerprinting entirely?
Not with settings alone. The practical options are a browser built to normalise these signals, a network shared by many users, or accepting that a determined site can still tell visitors apart.