cloudflare-workers-bot-scan-defense

Automated bot scans target Cloudflare Worker deployments after HTTPS exposure because the Certificate Transparency Log publicly exposes newly registered domains, triggering scanners to probe unauthenticated expensive routes. This Skill analyzes the scanner pipeline and identifies which paths create compute costs.

To add rate limiting to a Hono application on Cloudflare Workers, this Skill guides you through configuring rate limit bindings, integrating Hono middleware, and establishing verification workflows to protect unauthenticated expensive routes from automated probing.

Yes, you can use this Skill to audit exposed Cloudflare Worker routes for unauthenticated expensive paths. It analyzes deployments using Wrangler, Hono, D1, and R2 to identify which public HTTPS endpoints lack authentication and consume high compute resources.

The best way to configure Workers Observability for bot protection is to integrate it with rate limit bindings and route analysis. This Skill provides a deployment verification workflow to ensure your observability setup correctly tracks and mitigates malicious probing.

Yes, Workers Observability is required to effectively defend against bot scans. This Skill requires Workers Observability configuration alongside rate limit bindings and middleware integration to audit exposed routes, add targeted protections, and verify the deployed defense configuration.