Other automated crawlers
SBIntuitionsBot is a bot operated by SB Intuitions that crawls the web automatically. AI development and information analysis. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Request says
"SBIntuitionsBot"
Checked against
Nothing published
Live check
No operator check exists for SBIntuitionsBot. This still shows what the address really is.
Reference
| User agent | SBIntuitionsBotToken only: match on the substring. |
|---|---|
| Operator | SB Intuitions |
| Purpose | Uses data gathered in AI development and information analysis. |
| Respects robots.txt | Honourssource |
| 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 | SBIntuitionsBot |
| Operator documentation | None published |
AI development and information analysis
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: SBIntuitionsBot
Disallow: /User-agent: SBIntuitionsBot
Allow: /User-agent: SBIntuitionsBot
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking SBIntuitionsBot 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
SBIntuitionsBot is a bot operated by SB Intuitions that crawls the web automatically. AI development and information analysis. It is documented as honouring robots.txt, but no IP range list or reverse-DNS convention is published, so a request carrying this user agent cannot be proven genuine.
Yes. The operator documents that SBIntuitionsBot reads robots.txt and follows Disallow rules for its own token. Rules take effect on the next fetch of the file, which can be hours or days after you publish them.
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 SBIntuitionsBot 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 SBIntuitionsBot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.