# 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.

- 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
- Source: https://developers.cloudflare.com/fundamentals/reference/cloudflare-site-crawling/ (retrieved 2026-10-18)

## JSON

`curl -s https://whosthatbot.com/v1/crawlers/cloudflare-ssldetector`

## Check this token

tools/call with name check_robots is the same check at https://whosthatbot.com/mcp. Send `Content-Type: application/json` and `Accept: application/json, text/event-stream`. 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: /.

Each card paraphrases the linked vendor page and was checked on source.retrieved. This is not legal advice. robots.txt is a request from the site owner. Botcard does not fetch third-party sites and does not suggest ways around a disallow rule.