Your bot protection challenged our scan
Likely cause
Your site's own Cloudflare bot protection (Managed Challenge, Bot Fight Mode, or a similar rule) responded to our scan with a challenge page instead of serving the actual site.
Check
Check your Cloudflare dashboard's Security settings (Bot Fight Mode, Super Bot Fight Mode, or any custom Firewall/WAF rules) to see what's challenging this traffic.
Fix
If this is intentional, no action is needed — it's working as designed. If you'd like to allow this scanner specifically, add a rule matching the User-Agent "OriginError-Scan" (sent on every scan) rather than trying to allowlist by IP — Cloudflare Workers share IP ranges across many unrelated services, so an IP-based allow rule wouldn't reliably target just this tool.
Verify
If you believe real visitors are also affected, describe what's happening instead of relying on this automated scan — bot protection is specifically designed to treat automated requests differently from real visitors.