Published versions
Crawlerrd4.crawler_identity.v1.1
Route Agentrd4.route_agent_identity.v1.1
Etiquetterd4.crawler_etiquette.v1
Evidence-separated state
Identity status
A source implementation, a deployed endpoint, a valid signature, and external approval are different facts.
- 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.
The Cloudflare crawler application was submitted on 2026-07-06 and is recorded as pending. ProofStrikeRouteAgent remains deferred/not submitted after a duplicate Signature-Agent response. No approval, direct/intermediary classification, provider case ID, universal site access, or Radar listing is claimed.
How to verify
Retrieve the public directory over HTTPS, confirm its exact media type, compute each public JWK thumbprint, and independently verify every response signature and its covered request authority.