`Cloudflare-SSLDetector`

Cloudflare says the SSL/TLS recommender uses the user agent Cloudflare-SSLDetector. The page says this crawler ignores your robots.txt file unless there are rules explicitly targeting the user agent. 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-SSLDetector
Operator: Cloudflare
Kind: owner_requested
robots.txt: ignores_star. The vendor says this robot does not take the general User-agent: * rules in robots.txt into account.
HTTP user-agent: Cloudflare-SSLDetector The page prints Cloudflare-SSLDetector as the whole user agent. It does not print a separate robots.txt User-agent line. 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-ssldetector

Check this token

tools/call with name check_robots is the same check at POST /mcp. The pasted file disallows Cloudflare-SSLDetector 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-SSLDetector\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["cloudflare-ssldetector"]}}}'

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