Implementation, deployment, signing, submission, approval, and public listing are separate states. A public key directory is not the same as a verified live request.
Web Bot Auth implementation
implementedSource implementation present; runtime and external recognition are separate evidence gates.
Public directory deployment
deployedPublic key directory state: reachable.
Directory response signing
live proof requiredA release is valid only when the HTTP response carries one independently verified signature per published key.
Live request signing
sign requiredEach eligible request, redirect, and browser document navigation requires a fresh identity-aligned signature.
Cloudflare application submission
submittedProofStrikeRD4Crawler was submitted 2026-07-06 using Web Bot Auth / Request Signature. Route Agent submission is deferred after a duplicate Signature-Agent response; no external case ID is recorded.
Cloudflare approval
pendingApproval is an external state. No direct-versus-intermediary designation is recorded or inferred.
BotBase / Radar listing
not independently evidencedNo public catalog listing is claimed without separate, current evidence.
Research is limited to public route information and conducted with conservative, observable controls.
Public surfaces only
Public pages and public policy documents
Robots instructions honored
Reasonable per-site request rates
No circumvention
No CAPTCHA or challenge solving
No access-control bypass
No accounts, credentials, or private sessions
Research, not dispatch
No notice submission during research
No form submission
No media harvesting
Data handling
ProofStrike minimizes what it retains while preserving enough public evidence and provenance to explain a route recommendation.
Bounded public data
Public response metadata and route URLs
Content hashes and bounded route-context snippets
Access, extraction, and verification diagnostics
Provenance needed to audit route intelligence
Never collected for this research
Private user content or credentials
Account sessions, cookies, or CAPTCHA tokens
Private messages or non-public profiles
Media libraries or bulk media content
Website-owner controls
Ask for a correction, a lower request rate, blocking, or an allowlisting discussion. Privacy and security reports use the same accountable public channel.
Correct or reduce
Report inaccurate route data or request a lower research rate.