// per-site profile
what detects you on fingerprint.com
fingerprint.com is defended by fingerprintjs, which declares native js fingerprint (3/3), partial server coherence (1/3) capability. below: the layers it enforces and the tool config the matrix predicts survives it.
enforced detection layers
| detection layer | capability | what it covers |
|---|---|---|
| tls / network fingerprint | unaddressed | the ja3/ja4 clienthello and http/2 settings signature the edge reads before any javascript runs. |
| ip reputation | unaddressed | asn, proxy-class, and abuse-history scoring of the connecting address. |
| js fingerprint | 3/3 native | canvas, webgl, navigator, font, and audio signals collected in-page. |
| behavioral | unaddressed | mouse, keyboard, and timing biometrics read from interaction cadence. |
| challenge | unaddressed | interactive or invisible captcha and proof-of-work gates. |
| attestation | unaddressed | hardware or os-backed integrity checks (webauthn, play integrity, device attestation). |
| server coherence | 1/3 partial | cross-checking headers, tls, ip, and js for internal consistency. |
unaddressed means this tool type does not operate at that layer, so it is not a failing score. a red 0/3 is a real, declared score of zero. both are declared capability, not live pass-rates.
recommended config (matrix-predicted)
| enforced layer | argmax tool |
|---|---|
| js fingerprint | CloakBrowser (stealth Chromium) |
| server coherence | nothing catalogued |
public-matrix prediction (argmax capability per layer), free. the benchmarked winning bundle for fingerprint.com, the one verified against a live run and kept fresh, is metered: see what a lookup costs.
notes
VERDICT FIXED (WP3.10, 2026-07-24). The previous rule was `notContains '"bot":"bad"'`, testing a literal string that NEVER appears in the rendered page, the demo renders labelled sections, not raw JSON. So the condition was vacuously true on every load and this target has never produced a real pass/fail. READ THE NEW RULE CAREFULLY: it asserts the identification block rendered (a CONFIDENCE SCORE is present), i.e. "we loaded the demo and it identified us". It is NOT a human-vs-bot judgement, because none is available on load: the 3-way bot label (bad|good|notDetected) lives behind the `BROWSER SMART SIGNALS` tab and needs interaction to reach. `scored` is therefore false. This target cannot rank tools by stealth and must not appear as a detectors-matrix column until the Smart-Signals tab can be driven. The verdict exists so trials stay DEFINITIVE rather than ambiguous; the value is in the signals. `browserVerdict` is Fingerprint's browser identification in prose and is the closest thing to a detection tell available on load (observed: `Chromium-Based Browser Not Available on Windows (10)`, an impossible browser/OS combination it called out); `visitorId` is the identity-stability input.
questions
- what detects you on fingerprint.com?
- fingerprint.com is defended by fingerprintjs, which declares native js fingerprint (3/3), partial server coherence (1/3) capability.
- which config survives fingerprint.com?
- matrix-predicted per enforced layer: js fingerprint → CloakBrowser (stealth Chromium). this is a public-matrix prediction, not a metered recipe.