# Cloudflare-diagnostics

Cloudflare says Cloudflare-diagnostics is used when Support Engineers perform error checks and when continuous monitoring raises alerts in the Cloudflare dashboard. 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.

- Operator: Cloudflare
- Kind: owner_requested
- robots.txt: not_stated. The cited page does not say whether robots.txt controls this token.
- HTTP user-agent: Cloudflare-diagnostics The page prints Cloudflare-diagnostics 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-diagnostics`

## 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-diagnostics 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-diagnostics\nDisallow: /\n\nUser-agent: *\nAllow: /\n","path":"/docs","ids":["cloudflare-diagnostics"]}}}'
```

That call returns fetched_target false. This row is disallow via group Cloudflare-diagnostics, 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.