最終更新日:2026-03-25 18:14:14
If your website provides user-specific response pages tailored for certain crawlers, or if further analysis is needed in combination with your own risk control system, you can use custom HTTP request headers to flag requests that trigger Bot Management results and forward these flags to the origin site.
Note: This feature is enabled upon request. Please contact technical support to activate the feature if needed.
to enter the Security Policy editing page.| Origin Fetching Tag Type | Tag Description | Origin Fetching Value | Value Description | Data Example |
|---|---|---|---|---|
Custom Bots |
Marks the matched Custom Bots policy name in the custom HTTP request header,if multiple policies are matched, they are separated by semi-colons. |
Custom Bots Policy Name |
Text, contains2 pieces of data, separated by ',': The first value is always the policy typeCustom Bots); The second value is thename of the custom Bots policy(if multiple are matched, separated by semi-colons)。 |
X-Custom-Bots: Custom Bots,name1;Custom Bots,name2 |
AI Bots |
Indicate the matched AI Bots policy category in the custom HTTP request header. |
AI Assistant AI Search Crawler AI Data Scraper Undocumented AI Agent |
Text, with a total of 2 values separated by commas: The first value is always the policy type (Public Bots); The second value is the Public Bots category (Search Engine/Site Monitor/Page Viewer/Marketing Analysis/Feed Fetcher/Practical Tools). |
X-AI-Bots:AI Bots, AI Assistant |
Public BotsBots |
Mark the matched public Bots policy category in a custom HTTP request header. |
Search Engines Site Monitor Page Viewer Marketing Analytics Feed Fetcher Practical Tools |
Text, containing 2 data items, separated by a comma: The first item is always the Policy Type (AI Bots); The second item specifies the AI Bots category (Assistant/ AI Search Crawler/AI Data Scraper/Undocumented AI Agent). |
X-Public-Bots:Public Bots, Search Engines |
Bot Score |
Mark the matched Bot score in a custom HTTP request header. |
1-100 |
An integer value. The higher the score, the more suspicious the Bot is. Ø 100: Definite Bots (100% Automated) Ø 80-99: Suspected Bots (Highly Likely Automated) Ø 2-79: Suspected Human (Anomalies Detected, Possibly Human) Ø 1: Suspected Human (No Anomalies Detected, Highly Likely Human) |
X-Bot-Score:100 |
Bot Tags |
Mark the detected Bot label in the custom HTTP request header. |
1,2,3,4,5,6,7,8,9,10,30,31,32,33,34,35,36,60 |
Assign the corresponding tags based on abnormal conditions detected in access requests. Ø 1: Cloud Provider IP Ø 2: Threat Intelligence Risk IP Ø 3: Proxy IP Ø 4: Forged User_Agent Ø 5: Outdated Browser or Operating System Ø 6: Mismatch Between Request Headers and Declared Client Type in User-Agent Ø 7: Significant Missing Browser Request Headers Integrity Ø 8: Partial Missing Browser Request Headers Integrity Ø 9: Known Bot Tool Fingerprint Ø 10: Abnormal JA4 Fingerprint in Browser Ø 30: HTTP Library Ø 31: Browser Automation Testing Tools Ø 32: Command Line Network Request Tools Ø 33: Scanning Tools Ø 34: Crawler Tools Ø 35: Proxy Tools Ø 36: Fake Spider Ø 60: Anomalous Aggregation Behavior |
X-Bot-Tags: 1,2,3,4,5,6,7,9,10,30 |
Notes:
- A Bot Score of 1 means no abnormal activity was detected, and no Bot Labels are assigned.
- A Bot Score of 2–99 may correspond to the following Bot Labels: 1, 2, 3, 4, 5, 6, 7, 8, 9, 10, 60.
- A Bot Score of 100 may correspond to the following Bot Labels: 30, 31, 32, 33, 34, 35, 36.