b2KIT

Browser Privacy Tester

Comprehensive privacy audit testing tracking protection, cookie handling, fingerprinting resistance, and API exposure.

Tested tool guide Tested browser tools Checked August 16, 2026

What Browser Privacy Tester does and how it behaves

Runs a privacy audit inside the browser you currently have open and reports how that browser measures up on four fronts: tracking protection, cookie handling, fingerprinting resistance, and exposure of privacy-sensitive APIs. The probes execute in the live session, so they see the browser exactly as a visited website would, and each area is reported on its own rather than folded into one composite verdict. The most common surprise is scope: the report describes one browser profile at one moment. It does not cover your network, your VPN, or your DNS, and an extension or update can change the results tomorrow.

How the result is produced

1

What the probes exercise

The audit runs entirely inside the open page, so each test sees the same surface a visited site would. Cookie checks set and read back cookies to test persistence and whether cross-site contexts are blocked. Fingerprinting checks read browser-exposed signals such as canvas output, fonts, and WebGL information. API checks probe which sensitive interfaces exist, and tracking protection is judged by how cross-site requests are treated.

2

How the verdicts come about

Results are compared with the expected behavior of a cleanly configured browser and grouped by the four audited areas, each with its own outcome. Because the tests execute in the current session, every result reflects the live combination of browser version, profile settings, and installed extensions. Re-running the audit after a settings change is the intended way to confirm that the change actually took effect.

Good uses

  • Record a baseline before tightening privacy settings or switching browsers, then re-run the audit to confirm the change actually moved the measured behavior.
  • After installing or updating tracker-blocking extensions, verify they alter measurable cookie and fingerprinting behavior instead of trusting the label.
  • When a site keeps logging you out or misbehaves in one browser but not another, audit to see whether strict cookie or API blocking is what the site trips over.

Limits and checks

  • A single run is a snapshot of one session. Version updates, extension changes, and profile differences all move the results, so the report can go stale within weeks and is not a standing verdict for the browser.
  • The audit is browser-side only. VPN leaks, DNS behavior, and ISP visibility are all outside what in-page probes can measure, so a clean report says nothing about your connection or your network.
  • Resistance is not anonymity. A browser that hides or noises fingerprinting signals can still be identifiable by other characteristics, and the report measures the hiding itself, not how unique your overall setup is.

Common questions

Does a clean report mean my browsing is private?

No. The audit tests how the browser handles a fixed set of tracking, cookie, fingerprinting, and API probes. It says nothing about network traffic, DNS, or what sites learn from your accounts and behavior. Treat a clean report as evidence about browser configuration, not as a general privacy guarantee.

Why does my result differ from someone running the same browser?

Because two copies of the same browser usually differ in practice: version, operating system, profile settings, and installed extensions all shape the measured surface. Tracker blockers in particular can interfere with the audit's own probes, and that interference itself shows up in the results.

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