`CCBot`

Common Crawl's CCBot page says the crawler identifies itself as CCBot/2.0 with the FAQ URL inside the user-agent. The page description says it is a Nutch-based crawler that uses the crawl database to pick candidates. The body says the crawl supports an open repository of web crawl data, and that publishing User-agent: CCBot and Disallow: / prevents Common Crawl from crawling the site. The page says some crawlers falsely use the CCBot name, and that the real crawler uses dedicated IP ranges with reverse DNS, except IPv6 where reverse DNS is not yet supported. The CCBot page shows no article date. A separate post dated September 17, 2025 says the Opt-Out Registry is now the Opt-Out Ledger, because the list is immutable. That post says Common Crawl publishes every legal opt-out request it has received, encourages robots.txt to control crawling, and still processes legal requests. It points CCBot configuration back at the CCBot page and does not say the ledger replaces the Disallow block.

robots.txt token: CCBot
Operator: Common Crawl
Kind: open_crawl
robots.txt: disallow_is_opt_out. The vendor says disallowing this token opts that use out.
Opt-out ledger: Not applied to the RFC decision. Common Crawl Foundation Opt-Out Registry, header date 2025-09-17, retrieved 2026-10-18. The post says the Opt-Out Registry is now the Opt-Out Ledger. The post header shows September 17, 2025. The body says the Opt-Out Registry is now the Opt-Out Ledger, to reflect that the list is immutable. Common Crawl says it publishes the full list of legal opt-out requests it has received, encourages robots.txt to control crawling, and continues to process legal requests. Questions and requests go to info@commoncrawl.org. The post points CCBot configuration at the CCBot page. The checker reports this and does not apply it to the RFC decision. The post links this spreadsheet and labels the link Common Crawl Opt-Out Ledger. On 2026-10-18 the URL returned HTTP 200. The HTML title began with Common Crawl Opt-Out Ledger. Botcard does not copy the rows.
HTTP user-agent: CCBot/2.0 (https://commoncrawl.org/faq/) The cited page publishes this as the UserAgent string. The FAQ URL is inside the parentheses. The same page says some crawlers falsely identify themselves as CCBot and recommends verifying the string.
IP list: https://index.commoncrawl.org/ccbot.json The cited page publishes this URL of v4 and v6 ranges. It says CCBot runs on dedicated ranges with reverse DNS, except over IPv6 where reverse DNS is not yet supported. On 2026-10-18 this URL returned HTTP 200 and JSON, with no redirect. Botcard does not copy the address list.
Source: Common Crawl - CCBot. Retrieved 2026-10-18.

JSON

curl -s https://whosthatbot.com/v1/crawlers/ccbot

Check this token

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

That call returns fetched_target false. This row is disallow via group CCBot, rule Disallow: /. opt_out_ledger is reported and is not the decision.