Dashboard

Browser Intelligence

Definition. Browser Intelligence is the signal-collection layer: the evidence Noxtica reads from the browser before any decision is made. It is the intelligence half of the two-layer browser story — collection here, enforcement in the other layer.

This layer only reads. It gathers the many small, inert characteristics a browser naturally exposes, and hands them — sealed — to the scoring engine. Nothing is challenged or blocked at this stage; that is a separate, explicitly-policy-driven step.

How Noxtica does it

Collection runs inside the Sealed Runtime, the tamper-resistant runtime, on the device. It gathers signals across several categories:

  • Rendering signals — canvas, WebGL, and audio characteristics that describe how a device draws and processes media.
  • Environment signals — fonts, hardware markers, and platform details that, taken together, describe a device without identifying a person.
  • Consistency signals — whether the browser’s self-description agrees with what it actually does. Contradictions here are a well-known automation tell.
  • Network context — derived at the edge (the kind of network, the country, whether it looks like a datacenter), never the raw address.

The signals are inert and non-personal: harmless details that describe a device, not a human. They are wrapped in a sealed result so the picture can’t be quietly rewritten after collection. The reads are transparent and explainable — every signal that contributes to a score is documented and traceable.

Where it fits

Browser Intelligence is the collection layer of the Intelligence pillar. It feeds Know Your Device, which condenses these signals into a fingerprint and a score. It pairs with Browser Security, the enforcement layer that acts on the results — the two layers together are what “Browser Intelligence + Browser Security” means.

Read deeper

  • Detection signals — the full 30+ probe list, the entropy each contributes, and the scoring weights.
  • Browser runtime — how the Sealed Runtime collector behaves at collection time.
  • Know Your Device — how these signals become a fingerprint and a score.
  • Browser Security — the enforcement layer that pairs with this one.