// per-site profile
what detects you on browserscan.net
browserscan.net is defended by a detection vendor being profiled. below: the layers it enforces and the tool config the matrix predicts survives it.
enforced detection layers
not yet measured: enforced layers on browserscan.net
this entry is in the catalog but carries no scored capability yet. the matrix updates as the benchmark self-heals, so check back or see the capability matrix.
notes
VERDICT FIXED (WP3.10, 2026-07-24). The previous rule was `contains "No bots detected"`, which matched STATIC BOILERPLATE: an explanatory <li> reading "No bots detected - the visitor could be a human using a regular browser.", present on every load regardless of outcome. Matched against whole-page text it was a permanent PASS whenever the page rendered, so a recorded fail meant "did not render / blocked upstream", never "the detector judged us a bot", and every historical pass on this target carries no detection information. The real result renders as `Test Results:` followed by a label (verified live: `Normal`); the anchored regex ties the assertion to that context instead of to any occurrence of a phrase anywhere on the page. SIGNALS: the same anchor captures the label itself, so a future label change shows up as a value rather than as a silent flip to fail. A selector is deliberately NOT used, the result sits in a hashed CSS-module class (`_oxrqr1`) that changes on every redeploy. The four sub-checks (Webdriver / User-Agent / CDP / Navigator) are bare section headings with no adjacent status on load.
questions
- what detects you on browserscan.net?
- browserscan.net's detection vendor is being profiled.
- which config survives browserscan.net?
- no enforced layers are scored yet, so no prediction is available.