Skip to content
Back to the fingerprint testReference · 271 checks

Browser fingerprint checks: the full index

A subsystem-by-subsystem index of all 271 checks in the Clearcote browser fingerprint test. Each check has its own page explaining what a detector infers when it fails, what an ordinary unmodified browser yields, and how to resolve it. 159 of them also name the anti-bot systems documented to read the signal, with the published artifact behind each attribution.

What this audit checks, and why each signal is legible

Almost every check below is self-referential: it asks this browser the same question through two independent APIs and reports whether both answers can be true at once. That is why it needs no baseline corpus — a contradiction is visible from inside the page. The WebRTC address check is the lone exception, and the only one that makes a network call: comparing where your media exits against where your page arrived from is not answerable from inside. Open any check for the full mechanism, what an ordinary unmodified browser yields, how to resolve it, and which detectors are documented to read it.

HTTP request vs the runtime

Screen & display

Navigator identity

Engine & OS oracles

Worker realms

Network & WebRTC

Clocks & ledgers

Automation surface

the browser will not resolve a filesystem path the page inventedsynthesized-path-entry-sandboxThis row does not measure a fingerprint. It measures whether the browser will help a page enumerate what is installed on the machine, and it comes from the most invasive technique in a deployed…

Error subsystem

Native function integrity

Render & GPU

Capability surfaces

Environment & locale

TLS & the network layer

Connection & locale

Input & behaviour