ClaudeBot
AI training crawler operated by Anthropic
Anthropic
Operator
Published IP ranges
Verification
ClaudeBot
robots.txt token
Yes
Honours robots.txt
Measured across detections recorded by WebDecoy, mostly on WebDecoy's own properties, 2025-11-14 to 2026-08-19. A small sample, not the whole web.
What ClaudeBot is
Collects public web content used to train Claude models.
It identifies itself with a User-Agent containing ClaudeBot/1.0; [email protected]. Its robots.txt token is ClaudeBot , and it is listed as honouring robots.txt. Operator documentation: Anthropic .
Verifying it yourself
Anthropic publishes the ranges ClaudeBot crawls from. Fetch them and test the source address:
# 1. fetch the published ranges
curl -s -o ranges.json \
https://claude.com/crawling/bots.json
# 2. check an address against them
python3 - 203.0.113.42 <<'PY'
import json, sys, ipaddress
ip = ipaddress.ip_address(sys.argv[1])
data = json.load(open('ranges.json'))
hit = any(ip in ipaddress.ip_network(p.get('ipv4Prefix') or p['ipv6Prefix'])
for p in data['prefixes'])
print('verified' if hit else 'NOT VERIFIED')
PYSwap in the address you are checking. Never trust the User-Agent on its own: it is a header the client picks for itself.
Blocking it
If you want the real crawler to stay away, robots.txt is the polite way to ask:
User-agent: ClaudeBot
Disallow: /robots.txt only works on a client willing to obey it, which rules out every request that was already lying about who it is. Stopping those takes enforcement at the network or application layer, keyed on something the client cannot simply retype. That is the problem WebDecoy exists to solve.
Frequently Asked Questions
What is ClaudeBot? +
ClaudeBot is an ai training crawler operated by Anthropic. Collects public web content used to train Claude models.
How do I verify ClaudeBot? +
Anthropic publishes the IP ranges ClaudeBot uses at https://claude.com/crawling/bots.json. Check whether the request's source address falls inside one of those prefixes, and reject it if it does not. Never match on the User-Agent alone, because that is the part a client chooses for itself.
How do I block ClaudeBot? +
Add a robots.txt rule for the token ClaudeBot. That stops the real crawler, but not clients that only borrow its name, so pair it with verification and enforcement at your edge.
Methodology
Every request recorded by WebDecoy's sensors, mostly on WebDecoy's own properties, whose User-Agent declares one of these crawlers, checked IP-by-IP against the operator's own published IP range list. A request is counted as verified when its source IP falls inside a published prefix, and forged when it does not. Operators that publish no machine-readable range list cannot be checked this way and are reported without a forgery figure. Corpus: 81,034 detections from 17,187 distinct addresses, 2025-11-14 to 2026-08-19. Published ranges retrieved 2026-08-19. Operators revise their ranges over time, so a request logged months ago is checked against today's list; we re-ran the comparison over a recent 30-day window and the rates held.
This crawler dataset is licensed under CC BY 4.0; reuse is permitted with attribution to WebDecoy.
Related crawlers
- Anthropic Anthropic
- Claude-SearchBot Anthropic
- Claude-User Anthropic
- Claude-Web Anthropic
- AbliterantBot Abliterant
- AI2Bot Allen Institute for AI
- Amazonbot Amazon
- Applebot-Extended Apple
- ByteSpider ByteDance
- CCBot Common Crawl
- ChatGLM-Spider Zhipu AI
- Cohere Cohere
See which ClaudeBot requests are real
WebDecoy verifies declared crawlers against what their operators publish and identifies the ones that fail, as persistent actors rather than disposable IPs.