| [ Web Proxy ] |
| Viewing: https://developers.cloudflare.com/waf/troubleshooting/fake-bot-managed-rules/ | [Back] [Original] |
The Cloudflare Managed Ruleset includes rules that detect requests impersonating well-known bots such as Googlebot and Bingbot. These rules compare the request's User-Agent header against known bot patterns and then verify the source using methods like reverse DNS lookup or IP validation. If the User-Agent matches a known bot but the source cannot be verified, the rule flags the request as a fake bot.
The following table lists the fake bot detection rules in the Cloudflare Managed Ruleset:
| Rule name | Rule ID |
|---|---|
| Anomaly:Header:User-Agent - Fake Google Bot | ...6aa0bef8 |
| Anomaly:Header:User-Agent - Fake Bing or MSN Bot | ...c12cf9c8 |
Fake bot rules may trigger false positives for legitimate services that share infrastructure or user agent patterns with known bots but use different IP ranges. Common examples include:
User-Agent header from IP addresses outside the standard Googlebot range. These requests fail the IP verification check and are flagged as fake Google bots.User-Agent header may also be flagged.If a fake bot rule is blocking legitimate traffic, create an exception to skip the specific managed rule for the affected requests.
When defining the exception expression, use request properties that identify the legitimate traffic without broadly disabling the rule. For example:
The exception must appear in the rules list before the rule that executes the Cloudflare Managed Ruleset, or it will have no effect.
For instructions on creating exceptions, refer to Create exceptions.
| Web Proxy Viewer | New URL | Original Page |