Skip to main content
Findings arrive in signals:
Use id, tier, and family in code. headline and detail are prose. Read the tier from the finding; a few IDs carry different tiers in different conditions.

Network geometry

The comparison uses the nearest possible point in the claimed timezone, so it never assumes an exact location.

Transport stack

Transport reachability

TLS construction

HTTP construction

Compute

JavaScript automation and integrity

Collector 0.2.5 runs the basic automation, navigator getter and plugin checks even with surface: false. Realm, engine and detailed WebGL checks require their corresponding measurements. Missing evidence never establishes that a browser is unmodified. Fingerprinting coverage explains these limits. The four probe-demo traps above run only on the demo page. Customer pages use passive driver-global checks.

Canvas, permission and media checks

These checks run on customer pages even with surface: false and render: false. All four IDs belong to http-construction and are composite findings. A canvas finding reports altered pixels; it does not identify a GPU or the software that changed them. Permission checks inspect one returned object and never request permission. A denied permission is valid. The media check requires two stable samples and successful stylesheet controls. A blocked stylesheet, unavailable API, changed preference, or failed control leaves that check unavailable. It cannot establish a disagreement. The canvas check similarly requires an unchanged input buffer and a supported, intact drawing context. Each check must report a result or an explicit unavailable/error status. Omitting or corrupting a required section causes identity.measurement-partial and a refused verdict. This completeness requirement also applies when optional collection is disabled.

Rectangle, empty-text font and PNG checks

Collector 0.2.5 adds three checks to activeIntegrity version 2. They run even when optional rendering and surface collection are disabled. Rectangle dimensions can undergo different native rounding and do not trigger this check. PNG compression and encoded length can vary; the PNG check compares decoded opaque sRGB pixels. Unsupported APIs, failed controls and changing layout are reported explicitly. None of these findings identifies a browser vendor or establishes automation by itself.

Engine and device consistency

Display and locale

Measurement arithmetic and protocol consistency

Store provenance.assessment_schema and provenance.ruleset_revision with results you need to compare across releases. Use the tier returned in each result.