MyIPScan
Browser privacy review

Check My Browser Privacy Signals

Fingerprinting does not read anything you stored. It reads what the browser volunteers on every page load - rendering behavior, installed fonts, hardware bands, locale - and combines them into something recognizable. Clearing cookies changes none of it, which is why it needs a different kind of check.

Run Browser Fingerprint Test Run full report
Visible signals Safe receipt Not a certification

Start with the surface estimate

Run the combined view across browser basics, screen, timezone, canvas, WebGL, audio, fonts, Client Hints and storage first. Open the single-module subtests afterwards, once you know which module you want to move.

Separate what you can change from what you cannot

Timezone, language and privacy-preference headers are settings. Canvas, WebGL, audio and font results come out of your GPU, drivers and installed software, and no amount of clearing data touches them.

Change one thing per run

Two changes in one run give you a different surface and no way to attribute it. Change one, rerun in the same profile, and compare against the saved baseline.

Why the usual habits do not help

Why a fingerprint survives everything you clear

A cookie is data a site stored on your device, which is what makes deleting it meaningful. A fingerprint is not stored anywhere: it is assembled at read time out of values the browser exposes through ordinary web APIs, so there is nothing on your device to remove.

Private windows do not reset itA private window withholds existing cookies and discards new ones. The values a fingerprint is built from are reported identically, because they describe the browser and the machine rather than the session.
It crosses browsers, in partThe hardware-derived signals - GPU rendering, audio processing, core count, screen - are properties of the machine. Two different browsers on one computer share them, which is why switching browser alone is a weaker move than it feels.
It is read by third parties, not just the siteA fingerprinting script loaded from an embedded third party sees the same values on every site that embeds it, which is how the technique produces cross-site recognition without storing anything.

The long-form background, including how much of the population a combined fingerprint separates, is in the fingerprinting explainer.

Trait by trait

Which traits carry the weight, and what you can do about each

Ordered by how much they are worth changing. The distinction that matters is between traits that are settings and traits that are hardware, because only the first kind responds to a preference.

Canvas, WebGL and audio renderingThe same drawing or audio buffer resolves differently across GPU, driver and OS combinations. Nothing clears these. What changes them is a browser that randomizes or standardizes the output - Brave's fingerprinting protections, or Firefox's resist-fingerprinting mode. Isolate one at a time with the canvas, WebGL and audio subtests.
Installed fontsWhich fonts resolve reflects your operating system plus whatever software installed more, which is what separates two otherwise identical machines. Little to change here short of a browser that restricts font enumeration. Font subtest.
Timezone and language listTwo of the highest-value traits that are pure settings, and the two most likely to contradict a VPN exit in another country. Worth aligning deliberately rather than by accident.
Hardware concurrency and device memoryLogical core count and a rounded memory band. Hardware-fixed and reported coarsely, so they narrow the field rather than identify you alone.
User-Agent and Client HintsChromium sends the low-entropy hints - brand list, mobile flag, platform - on every request by default. Model, full version list, architecture and platform version are withheld until a site requests them through an Accept-CH header or calls getHighEntropyValues(). Compare what yours discloses with the Client Hints Checker and the User-Agent Checker.
Global Privacy Control and Do Not TrackThese express a preference worth expressing, but they cut both ways: few enough people set them that having them on is itself a distinguishing trait. Check what yours sends.

Reading the number honestly

What the surface estimate is not

The test returns a surface estimate for this browser. Three things it deliberately does not claim are worth knowing before you act on a result.

Not a uniqueness scoreIt describes how much recognizable surface this browser presents. It is not a measurement of how many other people share your configuration, and it does not identify a person.
Not a tracking detectorIt reports what is available to a site that chooses to fingerprint you. It cannot tell you whether any particular site is doing so.
Local, and reduced before sharingValues are generated in this browser. Safe Copy removes the full User-Agent string, exact screen details and raw hashes before you paste a result anywhere.

For the network side of the same session - public route, resolver, WebRTC and IPv6 alongside these traits - the Public Exposure Report runs them together. For the plain inventory of what a site receives without asking, see what websites can see about you.

Safe Receipt limits

Safe Copy replaces the identifying values with categories: the full User-Agent string, exact screen dimensions, raw fingerprint hashes and raw module values are removed. That makes a fingerprint result safe to paste into a forum thread or a bug report.

Review the Safe Privacy Receipt model before sharing diagnostics.

FAQ

Questions this page answers

Does clearing cookies change my browser fingerprint?

No. Cookies are stored data, so deleting them removes stored data. A fingerprint is assembled when a site reads it, out of values the browser reports by design - rendering behavior, fonts, hardware bands, locale - and none of those live on disk in a form you can clear.

Does turning on Do Not Track make me harder to recognize?

Not by itself, and it can work against you. The header expresses a preference that sites are free to ignore, and because relatively few people enable it, having it set adds a distinguishing bit to your fingerprint rather than removing one.