Autonomous agents
Reflectionbot is a bot operated by Reflection that browses the web on its own to finish multi-step tasks. An undocumented crawler whose user agent links to Reflection, a company that builds AI models. 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
"Reflectionbot"
Checked against
Nothing published
Live check
No operator check exists for Reflectionbot. This still shows what the address really is.
Reference
| User agent | ReflectionbotToken only: match on the substring. |
|---|---|
| Operator | Reflection |
| Purpose | Autonomous agents |
| Respects robots.txt | No policy |
| 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 | Reflectionbot |
| Operator documentation | None published |
An undocumented crawler whose user agent links to Reflection, a company that builds AI models.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: Reflectionbot
Disallow: /User-agent: Reflectionbot
Allow: /User-agent: Reflectionbot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking Reflectionbot stops automated sessions that fill forms, click through flows and read pages the way a logged-in user would. Rate limits and challenges usually work better here than a robots.txt line.
Build a file for every crawlerFAQ
Reflectionbot is a bot operated by Reflection that browses the web on its own to finish multi-step tasks. An undocumented crawler whose user agent links to Reflection, a company that builds AI models. 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.
Not documented. No operator statement says whether Reflectionbot reads robots.txt, so add the rule but verify in your logs that the requests actually stop.
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 Reflectionbot 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 Reflectionbot stops automated sessions that fill forms, click through flows and read pages the way a logged-in user would. Rate limits and challenges usually work better here than a robots.txt line.