Other automated crawlers
Thinkbot is a bot that crawls the web automatically. Collects data for analysis on AI usage and automation. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Request says
"Thinkbot"
Checked against
Nothing published
Live check
No operator check exists for Thinkbot. This still shows what the address really is.
Reference
| User agent | ThinkbotToken only: match on the substring. |
|---|---|
| Operator | Thinkbot |
| Purpose | Insights on AI integration and automation. |
| Respects robots.txt | Ignores |
| Verification method | Claim onlyNone published, user agent only No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. |
| Crawl pattern | Not published |
| Robots.txt tokens | Thinkbot |
| Operator documentation | None published |
Collects data for analysis on AI usage and automation.
robots.txt
Thinkbot is documented as ignoring robots.txt. Enforce a block at your CDN too.
User-agent: Thinkbot
Disallow: /User-agent: Thinkbot
Allow: /User-agent: Thinkbot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Thinkbot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.
Build a file for every crawlerFAQ
Thinkbot is a bot that crawls the web automatically. Collects data for analysis on AI usage and automation. No IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine and a robots.txt rule alone will not stop a forgery.
Site-owner reports suggest Thinkbot does not reliably follow robots.txt. Add the rule anyway, then check your logs; if requests continue, block at the edge by user agent or source address.
You cannot, at least not from the request itself. No IP range file and no reverse-DNS convention have been published for this agent. The user-agent string is the only signal, and any client can send it, so treat a match as a claim rather than proof. Compare the source IP against hosting and datacenter ranges instead, and rate limit anything that behaves like a crawler.
Add the Thinkbot token to robots.txt with Disallow: /. If the crawler ignores robots.txt, match the user agent at your CDN or reverse proxy and return 403 there instead.
Blocking Thinkbot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.