b2KIT

Privacy Score Checker

Get an overall privacy score for your browser setup based on fingerprint uniqueness, leak tests, and security headers.

Tested tool guide Tested browser tools Checked August 16, 2026

What Privacy Score Checker does and how it behaves

This tool runs a battery of privacy checks inside your browser and combines them into a single score. It probes how uniquely your browser can be fingerprinted, runs leak tests that look for ways your real identity can escape the browser, and evaluates security-header exposure. The checks run locally; nothing is uploaded. The thing people most often get wrong is reading the number as a verdict on their whole online privacy: it is a snapshot of one browser profile on one machine at one moment, and the fingerprint-uniqueness figure is an estimate, not a count of other people who match you.

How the result is produced

1

Fingerprint uniqueness probe

The tool collects the signals a tracker would collect: user agent, screen and window metrics, timezone and language, installed font list, and the pixels your GPU renders for canvas and WebGL tests, which are hashed. Combining these produces a fingerprint hash, and the uniqueness figure estimates how much information that hash carries about your device. More distinct signals with more variation produce a higher estimated uniqueness.

2

Leak tests, header checks, and scoring

Leak tests look for channels through which your real identity reaches the network without your configured protections, most notably WebRTC, where a peer-connection request to a STUN server can reveal your IP even when a VPN or proxy is active. The header component inspects the security headers a tested server returns. Each component is scored and combined into the overall number, with per-component breakdowns shown so you can see which area dragged the total down.

Good uses

  • Comparing a default browser profile against a hardened one, for example Firefox with strict tracking protection or a fingerprinting-resistant mode, to see which configuration actually scores better before you switch.
  • After changing privacy settings or installing extensions (disabling WebRTC, blocking third-party cookies, enabling fingerprint resistance), re-running the check to confirm the change moved the score in the direction you intended.
  • When a site keeps blocking you or demanding verification, using the fingerprint view to see which of your identifiers are exposed and stable enough for the site to pin you to a profile.

Limits and checks

  • The uniqueness figure is an estimate. True uniqueness is a property of a population (how many other people's browsers share your fingerprint), and a client-side run cannot count that population. Treat the number as indicative of your exposure, not as a global ranking.
  • The three components measure different subjects. Fingerprint and leak results describe your browser and network; the security-header result describes the server that answered the request. A low header score does not mean your setup is broken, and you cannot raise it by changing browser settings.
  • The score is a snapshot that drifts. OS updates change rendering and font lists, browser updates change default behaviors, and a VPN or network switch changes leak-test results. Re-running later can produce a different number without anything you did; and chasing a higher number is not the same as protecting yourself, since a high score says nothing about what you install tomorrow or where you log in.

Common questions

Can a site still identify me if I block cookies and use a VPN?

Yes. Cookie blocking stops state stored on the site, but the fingerprint is derived from what your browser renders and reports on every visit (canvas pixels, fonts, screen metrics, language), which survives cookie clearing and can be correlated across sites. A VPN changes the IP-leak result but does nothing to the fingerprint hash, which is why fingerprint-based tracking works in private mode on most browsers.

Why is the uniqueness number different from what other privacy-test sites report?

There is no standard fingerprint. Every testing service chooses a different set of signals, some including audio processing or battery status and some ignoring fonts or WebGL, and hashes them with different code, so each one produces a different fingerprint for the same browser. Compare the qualitative findings (which checks pass or fail) across services rather than the numeric scores.

References and verification

The behavioral notes were checked against the browser implementation. Standards and primary references below define the relevant format, formula, or platform behavior.

Related Tools