Other automated crawlers
QuillBot is a bot that crawls the web automatically. Operated by QuillBot as part of their suite of AI product offerings. 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
"QuillBot"
Checked against
Nothing published
Live check
No operator check exists for QuillBot. This still shows what the address really is.
Reference
| User agent | QuillBotToken only: match on the substring. |
|---|---|
| Operator | Quillbot |
| Purpose | Company offers AI detection, writing tools and other services. |
| 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 | No explicit frequency provided. |
| Robots.txt tokens | QuillBotquillbot.com |
| Operator documentation | None published |
Operated by QuillBot as part of their suite of AI product offerings.
robots.txt
Paste one at the root of your domain. Rules are per token.
User-agent: QuillBot
User-agent: quillbot.com
Disallow: /User-agent: QuillBot
User-agent: quillbot.com
Allow: /User-agent: QuillBot
User-agent: quillbot.com
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own URLs.
Blocking QuillBot 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
QuillBot is a bot that crawls the web automatically. Operated by QuillBot as part of their suite of AI product offerings. 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 QuillBot 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 these user-agent tokens (QuillBot, quillbot.com) 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 QuillBot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.