Dashboard · Configuration
Security
The blocklist: by visitor, by address, by hardware.
The blocklist: where a person's decision is recorded.
Why it outranks every measurement#
Every other reason comes from a measurement. The blocklist belongs to the operator category, the only one that can overturn what was measured, because a person decided it.
Entries are applied at both /api/v1/collect and /api/v1/verdict.
Three scopes#
| Scope | Blocks | When to use it |
|---|---|---|
| Visitor | One browser profile | The most precise. The default choice. |
| Address | One IP address | Broader, an office NAT is many people |
| Hardware | One family of hardware measurements | The broadest, and only when the two above are not enough |
Blocking by hardware#
A hardware key describes a device rather than a browser profile, so it reaches someone who keeps minting fresh profiles on the same machine.
A WebGL parameter hash is a graphics card plus a driver, which is a model of laptop. Before a wide entry is written, the system counts how many people it would refuse and refuses the value outright past a limit. Nothing in 32 hex characters tells you which kind of value it is.
Hardware entries expire, 30 days by default.
Blocks belong to a workspace#
An entry belongs to the workspace that created it and applies only to that workspace's sites.
Notes#
Give every entry a note. Six months later, "blocked after 40 cards on 2026-03-11" is what separates a decision you can defend from a line nobody dares remove.