Cloudflare Docs
Bots
Visit Bots on GitHub
Set theme to dark (⇧+D)

Bot Feedback Loop

The Bot Feedback Loop is a way for customers to send Cloudflare direct feedback in the case of Bot Management potentially scoring a request incorrectly. When a customer submits a False Negative or a False Positive report, Cloudflare manually analyzes this data and uses it as a training dataset for our next Machine Learning model.

​​ Availability

Anyone who has access to Bot Analytics is able to submit feedback. This includes Enterprise Bot Management customers, as well as Business and Enterprise customers who use Super Bot Fight Mode. Visit Plans for more information.

​​ False Positive

A false positive can happen if Cloudflare scores a request from a person using a browser, mobile application or desktop application in the automated or likely automated range.

​​ False Negative

If Cloudflare is unable to detect a portion of automated traffic on your site, submitting a False Negative report will help us catch it in the future.

​​ Subtypes

SubtypeDefinition
Account Creation AbuseThe automated creation of many new accounts in order to gain access to site resources.
Ad FraudFraudulent increase in the number of times an advertisement is clicked on or displayed.
Credit Card AbuseAttempts to repeatedly validate many credit card numbers or the same credit card number with different validation details.
Cashing OutAbusing the target Internet application to obtain valuable goods.
Login AbuseAttempts to gain access to a password protected portion of an Internet application using many different combinations of usernames and passwords.
Inventory AbuseAutomated abuse related to purchasing limited stock inventory or holding inventory to prevent others from making transactions.
Denial of ServiceAutomated requests with the intent of exhausting server resources to prevent the Internet application from functioning.
ExpeditingAutomating the use of an Internet application to make transactions faster than a human visitor to gain unfair advantage.
FuzzingFinding implementation bugs through the use of malformed data injection in an automated fashion.
ScrapingAutomated retrieval of valuable or proprietary information from an Internet application.
SpammingThe abuse of content forms to send spam.
Token CrackingIdentification of valid token codes providing some form of user benefit within the application.
Vulnerability ScanningSystematic enumeration and examination of identifiable, guessable and unknown content locations, paths, file names, parameters, in order to find weaknesses and points where a security vulnerability might exist.

​​ Submit a report

  1. Log in to the Cloudflare dashboard and select your account and domain.
  2. Go to Security > Bots.
  3. Apply one or more bot score filters.
  4. Select Report incorrect data and fill out the form.
  5. Select Submit.

​​ Via the API

​​ Create a feedback report

curl -X POST 'https://api.cloudflare.com/client/v4/zones/023e105f4ecef8ad9ca31a8372d0c353/bot_management/feedback' \
-H "X-Auth-Email: [email protected]" \
-H "X-Auth-Key: c2547eb745079dac9320b638f5e225cf483cc5cfdda41" \
-H "Content-Type: application/json" \
-d '{
"type": "false_positive",
"description": "Legitimate customers having low score",
"expression": "(cf.bot_management.score le 46 and ip.geoip.asnum eq 132892 and http.host eq \"api-discovery.theburritobot.com\" and cf.bot_management.ja3_hash eq \"3fed133de60c35724739b913924b6c24\")",
"first_request_seen_at": "2022-08-01T00:00:00Z",
"last_request_seen_at": "2022-08-10T00:00:00Z",
"requests": 100,
"requests_by_score": {
"1": 50,
"10": 50
},
"requests_by_score_src": {
"heuristics": 25,
"machine_learning": 75
},
"requests_by_attribute": {
"topIPs": [
{
"metric": "10.75.34.1",
"requests": 100
}
],
"topUserAgents": [
{
"metric": "curl/7.68.0",
"requests": 100
}
]
}
}'
# Output
Null

​​ List feedback reports

# Command
curl -X GET 'https://api.cloudflare.com/client/v4/zones/4e6d50a41172bca54f222576aec3fc2b/bot_management/feedback' \
-H "X-Auth-Email: [email protected]" \
-H "X-Auth-Key: c2547eb745079dac9320b638f5e225cf483cc5cfdda41" \
-H "Content-Type: application/json" \
# Output
[
{
"created_at": "2022-08-19T00:05:24.749712Z",
"type": "false_positive",
"description": "Legitimate customers having low score",
"expression": "(cf.bot_management.score le 46 and ip.geoip.asnum eq 132892 and http.host eq \"api-discovery.theburritobot.com\" and cf.bot_management.ja3_hash eq \"3fed133de60c35724739b913924b6c24\")",
"first_request_seen_at": "2022-08-01T00:00:00Z",
"last_request_seen_at": "2022-08-10T00:00:00Z",
"requests": 100,
"requests_by_score": {
"1": 50,
"10": 50
},
"requests_by_score_src": {
"heuristics": 25,
"machine_learning": 75
},
"requests_by_attribute": {
"topIPs": [
{
"metric": "10.75.34.1",
"requests": 100
}
],
"topUserAgents": [
{
"metric": "curl/7.68.0",
"requests": 100
}
]
}
}
]

​​ API Fields

FieldTypeDescriptionValue Example
typestringThe feedback report type.false_positive
descriptionstringThe feedback report description with more details on the issue.Legitimate customers having low scores.
expressionstringThe wirefilter expression matching reported requests.(cf.bot_management.score le 46 and ip.geoip.asnum eq 132892 and http.host eq "app.example.com" and cf.bot_management.ja3_hash eq "3fed133de60c35724739b913924b6c24")
first_request_seen_atstringThe time range start when the first request has been seen, RFC3339 format.2022-08-01T00:00:00Z
last_request_seen_atstringThe time range end when the last request has been seen, RFC3339 format.2022-08-10T00:00:00Z
requestsintegerThe total number of reported requests.100
requests_by_scoreobjectThe requests breakdown by score.See example below.
requests_by_score_srcobjectRequests breakdown by score source.See example below.
requests_by_attributeobjectRequests breakdown by attribute (optional).See example below.

requests_by_score

{
"1": 50,
"10": 50
}

requests_by_score_src

{
"machine_learning": 75,
"heuristics": 25
}

requests_by_attribute

{
"topIPs": [
{
"metric": "10.75.34.1"
"requests": 100
}
],
"topUserAgents": [
{
"metric": "curl/7.68.0",
"requests": 100
}
]
}

​​ Expression Fields

FieldTypeDescription
cf.bot_management.ja3_hashstringThis provides an SSL/TLS fingerprint to help you identify potential bot requests.
cf.bot_management.scoreintegerThis represents the likelihood that a request originates from a bot using a score from 1-99.
http.hoststringThis represents the host name used in the full request URI.
http.request.uri.pathstringThis represents the URI path of the request.
http.user_agentstringThis represents the HTTP user agent which is a request header that contains a characteristic string to allow identification of the client operating system and web browser.
ip.geoip.asnumintegerThis represents the 16- or 32-bit integer representing the Autonomous System (AS) number associated with client IP address.
ip.geoip.countrystringThis represents the 2-letter country code in ISO 3166-1 Alpha 2 format.
ip.srcstringThe source address of the IP.

​​ Recommendations when submitting a report

When you submit a report, use the filters available in the Bot Analytics dashboard to ensure that your report includes only the traffic that received an incorrect score. In addition to filtering by a score (required), you may want to filter by user-agent, IP, ASN or JA3 to more precisely highlight the section of traffic that was scored incorrectly.

If you are not certain if some traffic received an incorrect score, keep this traffic in the report.

We appreciate any comments you wish to leave in the description field that might help our team better understand these requests in the context of typical traffic to your domain.

​​ Recommendations after submitting a false positive

After submitting a false positive, you can explicitly allow the traffic if you are confident that this traffic source cannot be used for abuse in the future. To allow traffic, you can create a Custom Rule or Firewall Rule with an allow action that matches the characteristics of your false positive report. We recommend any allow rule that you create uses the most narrow possible scope, including restricting the request methods and URIs that the expected traffic has access to, in order to limit potential abuse.

  • Allowing an IP address: Only use an IP address to allow traffic if the IP is a dedicated resource that belongs only to the traffic source you wish to allow.
    If the traffic you want to allow shares an IP with other traffic sources, or if the IP changes frequently, consider an alternative to allowing by IP address.

  • Allowing a JA3 fingerprint: If you want to allow access to a stable software client that does not come from a dedicated IP, you can do so by looking up the JA3 fingerprint(s) used by that client in the Bot Analytics dashboard, and creating a Custom Rule or Firewall Rule to allow traffic based on that JA3 fingerprint. JA3 fingerprints will only match a client’s TLS library, so be cautious in looking for both overlap with other clients and with variation based on the operating system.

    Cloudflare does not recommend relying on JA3 rules for mobile applications that may be abused. If you have questions about how to securely allow traffic from your mobile application, please contact your account team.

​​ Recommendations after submitting a false negative

After submitting a false negative report, you can explicitly block or rate-limit the incorrectly scored traffic using a combination of characteristics such as IP address, JA3 fingerprint, ASN, and user-agent. Before blocking or rate-limiting based on JA3 fingerprint, please use Bot Analytics to confirm that fingerprint is not being used by legitimate traffic sources.