Browser Fingerprint Test - Identify Your Unique Browser ID | IPOK

A browser fingerprint is the set of characteristics a site can read from your browser without setting a cookie and without asking you to log in. It is not one value — it is dozens of small values combined into a profile that is often stable enough to recognise you across sessions, across cookie clears, and sometimes across networks.

What a fingerprint is made of

The signals fall into three groups. None of them is unique on its own; the combination is what identifies you.

Group	Examples	Stability
Declared	User-Agent, Accept-Language, timezone, screen size, colour depth, hardware concurrency, device memory	Changes rarely; identical across millions of users
Rendered	Canvas output, WebGL vendor and renderer strings, font metrics, audio processing output	Depends on GPU, driver, OS, and installed fonts — this is where most of the entropy lives
Behavioural and network	Request header order, TLS handshake shape, HTTP/2 frame settings, IP address, ASN	Changes with browser version, VPN, and network path

The rendered group is the important one. Two machines running the same browser version on the same OS can still produce visibly different Canvas and WebGL output because the GPU, the driver version, and the installed font set all feed into the rendering. That is why a fingerprint can survive a cookie wipe but break when you update a graphics driver.

Why incognito mode does not help

Private browsing clears local storage, cookies, and history when the session ends. It does not change your User-Agent, your screen size, your timezone, your fonts, your canvas rendering, or your TLS handshake. A site that fingerprints you in incognito mode sees the same profile it saw in normal mode — it simply has no cookie to attach it to. The profile is rebuilt from scratch and matched against whatever it stored server-side last time.

This is also why clearing cookies between visits does not break tracking in practice. The cookie is a convenience, not the identifier.

How few signals you need

Uniqueness comes from multiplication, not from any single rare value. If a signal splits the population in half, twenty such signals give 2^20 combinations. Real-world distributions are far from even — some values are common, some are near-unique — but the effect is the same: a handful of ordinary-looking attributes narrows you to a very small group. The EFF's Panopticlick research demonstrated this publicly in the 2010s, and browsers have only become more readable since.

The practical consequence: you cannot defeat fingerprinting by changing one setting. Changing your User-Agent while leaving Canvas, fonts, and timezone untouched produces an obviously inconsistent profile that is often more distinctive than doing nothing.

Browser fingerprint vs network fingerprint

These are separate layers and they are detected by different means:

• Browser layer — everything JavaScript can read: canvas, WebGL, fonts, audio, declared settings. Detected on the page, in milliseconds.
• Network layer — TLS ClientHello shape, HTTP/2 settings, header order, IP and ASN. Detected at the edge, before your JavaScript even runs.

A VPN changes the network layer completely and the browser layer not at all. That is the core problem with "VPN plus clean browser" advice: the tunnel hides where you connect from, while the fingerprint still says it is the same person every time.

What actually reduces identifiability

• Use a browser that ships a uniform fingerprint — Tor Browser is the reference implementation; it makes every installation look alike rather than random. Randomisation per session is weaker, because it produces improbable combinations that stand out.
• Keep one browser for one identity — separate profiles or separate browsers per account type costs nothing and prevents cross-contamination.
• Do not mix manual spoofing with real settings — a Chrome UA on a Firefox TLS handshake is a red flag, not camouflage.
• Accept that you cannot be invisible — the realistic goal is blending into a large group, not becoming unique.

Reading the IPOK fingerprint result

Each section answers a different question, so read them together rather than in isolation:

1. Canvas and WebGL — if these differ between two devices that "should" be identical, the difference is hardware or fonts, not the browser.
2. Timezone versus IP location — a mismatch is the single most common tell that a VPN is in use.
3. Language versus IP country — same idea, and it is what makes a foreign exit node obvious.
4. Hardware concurrency and memory — coarse buckets, but they narrow the device class considerably.

FAQ

Is a browser fingerprint illegal?

No. It is built from data your browser sends voluntarily. Whether it is appropriate depends on consent law and jurisdiction, but the technique itself is ordinary web engineering.

Does a VPN hide my fingerprint?

No. A VPN changes your IP and possibly your TLS path. It leaves canvas, fonts, timezone, language, and screen geometry untouched.

Does clearing cookies reset it?

Only the cookie part. The fingerprint is regenerated from the same inputs and matches the previous profile.

Can I test whether my fingerprint is unique?

Run the check on two devices in the same household. If the output is identical, your setup is uniform — which is good for blending, bad for differentiation. If it differs, note exactly which fields differ; those are your identifiers.