# Error 1010: The owner of this website has banned your access based on your browser's signature.

- **ID:** `policy/cloudflare-waf-custom-rule-blocked-legitimate-traffic`
- **Domain:** policy
- **Category:** network_error
- **Error Code:** `1010`
- **Verification:** ai_generated
- **Fix Rate:** 85%

## Root Cause

A Cloudflare WAF custom rule or firewall rule is blocking traffic based on a specific browser signature or user-agent, incorrectly classifying legitimate requests as malicious.

## Version Compatibility

| Version | Status | Introduced | Deprecated |
|---------|--------|------------|------------|
| Cloudflare WAF 2023-01-01 | active | — | — |
| Cloudflare Firewall Rules 2023-03-01 | active | — | — |

## Workarounds

1. **Identify the specific WAF rule causing the block via Cloudflare Analytics: Log in to Cloudflare dashboard > Security > Events > Filter by RayID. Then modify or disable that rule. For example, if the rule blocks User-Agent 'BadBot', update it to allow 'Mozilla/5.0'.** (85% success)
   ```
   Identify the specific WAF rule causing the block via Cloudflare Analytics: Log in to Cloudflare dashboard > Security > Events > Filter by RayID. Then modify or disable that rule. For example, if the rule blocks User-Agent 'BadBot', update it to allow 'Mozilla/5.0'.
   ```
2. **Add a firewall rule to bypass WAF for specific trusted IPs or user-agents: `curl -X POST https://api.cloudflare.com/client/v4/zones/ZONE_ID/firewall/rules --header "Authorization: Bearer API_TOKEN" --data '{"filter":{"expression":"(ip.src eq 192.0.2.1)","paused":false},"action":"bypass","priority":1}'`.** (80% success)
   ```
   Add a firewall rule to bypass WAF for specific trusted IPs or user-agents: `curl -X POST https://api.cloudflare.com/client/v4/zones/ZONE_ID/firewall/rules --header "Authorization: Bearer API_TOKEN" --data '{"filter":{"expression":"(ip.src eq 192.0.2.1)","paused":false},"action":"bypass","priority":1}'`.
   ```
3. **Use Cloudflare's 'Under Attack' mode temporarily and then switch to a custom rule that uses rate limiting instead of browser signature checks: `curl -X PATCH https://api.cloudflare.com/client/v4/zones/ZONE_ID/settings/security_level --header "Authorization: Bearer API_TOKEN" --data '{"value":"under_attack"}'`.** (75% success)
   ```
   Use Cloudflare's 'Under Attack' mode temporarily and then switch to a custom rule that uses rate limiting instead of browser signature checks: `curl -X PATCH https://api.cloudflare.com/client/v4/zones/ZONE_ID/settings/security_level --header "Authorization: Bearer API_TOKEN" --data '{"value":"under_attack"}'`.
   ```

## Dead Ends

- **** — This removes all security protections, leaving the site vulnerable to attacks. It also does not address the root cause of why legitimate traffic was blocked. (70% fail)
- **** — The block is based on the browser's signature (e.g., User-Agent, TLS fingerprint), which is not affected by cache or cookies. (90% fail)
- **** — If the rule is based on browser signature rather than IP, changing the IP will not bypass the block. (60% fail)