Browser privacy diagnostic

Browser Fingerprint Check

Inspect fingerprintable browser characteristics such as rendering behavior, WebGL, audio, fonts, locale, storage, permissions, client hints, and consistency signals in this session.

Fingerprint stability guide

How to compare browser fingerprint signals without overclaiming

Creep++ inspects many browser-exposed surfaces locally, groups higher-impact findings first, and creates a session comparison token. Use labeled baselines and the optional three-scan stability check to see which individual signals change.

How to use the result

  1. Run one scan in the browser profile and connection state you want to understand.
  2. Label that baseline, change one setting or route, and scan again.
  3. Use the three-scan check when you need to separate stable signals from normal variation.

What it means

A changed token or signal is evidence that the observed browser profile changed; it is not proof of anonymity or tracking. Stable signals may still be shared by many users, while changing signals can still contribute to correlation.

Important limits

  • The result is local to this browser and session.
  • No scan can reproduce every tracker’s collection or model.
  • A high exposure score is guidance, not a universal uniqueness measurement.
Useful next checks Review simple privacy settingsLearn how fingerprinting works

Common questions

Does a unique-looking fingerprint identify me by name?

No. It can help correlate browser sessions, but identity requires additional data and context.

Why do signals change between scans?

Timing, rendering, device state, permissions, browser updates, and privacy defenses can introduce variation. The three-scan view helps expose that instability.