Specimen registry · v0.1

Browser bot
detection harness.

One vendor per page. Identical skeleton — only the vendor script differs. Run automation tools against each page in isolation to attribute which signal triggered which detector.

Test-mode URL params

Append to any live vendor page to force a known state — useful when validating your own captcha-presence detector against ground truth. Flags are orthogonal and may be combined with , or repeated params.

?captcha=on — default; render widget normally
?captcha=off — skip widget mount entirely
?captcha=visible — force checkbox / visible variant
?captcha=invisible — force invisible + auto-execute
?captcha=expired — mount, then drop token to expired
?captcha=failed — mount, route success to error
?delay=2000 — defer mount by N ms (timing tests)

Combos: ?captcha=invisible,expired · ?captcha=invisible&captcha=failed · ?captcha=invisible,failed&delay=2000

Run tracking

Each page load gets a request ID (rid) shown in the banner. Pass ?rid=<id> from your worker (or let it auto-generate). Identify the worker with extra params.

?rid=<id> — request ID (auto-generated UUID if absent)
?worker=<name> — e.g. playwright-stealth
?run=<batch-id> — batch / sweep identifier
?tag=<comma-list> — free tags (headless,proxy-us)
?w.<anything>=<value> — arbitrary metadata under worker.extra

Events stream to logs/events.jsonl. Browse the run log at /runs/.

Captcha-style vendors

Fingerprinting

Public test pages (external)

Public bot-detection playgroundslinks

Behavioral · enterprise

Field sightings · live production deployments

Real sites believed to use each enterprise vendor. Labels rotate — confirm via cookies / response headers / JS bundle URL before trusting. One request per check; do not pound.