`Cloudflare-Traffic-Manager`

Cloudflare says load balancing monitors use Cloudflare-Traffic-Manager/1.0 and a 16-character pool ID. The page does not say whether robots.txt controls this token. This check matches the whole token, so a group named Cloudflare does not match, and it still reports the RFC 9309 decision.

robots.txt token: Cloudflare-Traffic-Manager
Operator: Cloudflare
Kind: owner_requested
robots.txt: not_stated. The cited page does not say whether robots.txt controls this token.
HTTP user-agent: Mozilla/5.0 (compatible; Cloudflare-Traffic-Manager/1.0; +https://www.cloudflare.com/traffic-manager/; pool-id: <POOL_ID>) The page prints this string as the user agent. It does not print a separate robots.txt User-agent line. <POOL_ID> is the page's placeholder for a 16-character load balancing pool ID, not an ID Botcard observed. A group named Cloudflare does not match this token.
IP list: None on the cited page. The page does not publish an IP list. Botcard does not copy addresses.
Source: Cloudflare crawlers. Retrieved 2026-10-18, page says updated 2026-08-06.

JSON

curl -s https://whosthatbot.com/v1/crawlers/cloudflare-traffic-manager

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Cloudflare-Traffic-Manager on /docs and allows *. The call does not fetch a host.

curl -s https://whosthatbot.com/mcp -H 'content-type: application/json' -H 'accept: application/json, text/event-stream' -d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"check_robots","arguments":{"robots_txt":"User-agent: Cloudflare-Traffic-Manager\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["cloudflare-traffic-manager"]}}}'

That call returns fetched_target false. This row is disallow via group Cloudflare-Traffic-Manager, rule Disallow: /.