QuillBot
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.
Also seen as quillbot.com. Rules need to cover every token.
QuillBot at a glance
| User agent | QuillBotToken only. The operator has not published a full user-agent string, so match on the substring rather than an exact header. |
|---|---|
| Operator | Quillbot |
| Purpose | Company offers AI detection, writing tools and other services. |
| Respects robots.txt | Not documented |
| Verification method | None 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.
Allow or block QuillBot
Paste one of these into the robots.txt file at the root of your domain. Rules are per token, so a block on one crawler leaves every other bot untouched.
User-agent: QuillBot
User-agent: quillbot.com
Disallow: /Blocks every path for this crawler only.
User-agent: QuillBot
User-agent: quillbot.com
Allow: /Explicit allow. Useful when a wildcard rule above it would otherwise catch this crawler.
User-agent: QuillBot
User-agent: quillbot.com
Allow: /
Disallow: /account/
Disallow: /checkout/
Disallow: /searchEdit the Disallow paths to match your own account, checkout and search URLs.
What blocking actually costs you
Blocking QuillBot stops this specific token. Check your logs afterwards, because operators that ignore robots.txt often come back under a different name.
Block every crawler in the directory at onceIs that really QuillBot?
A user-agent header is a string the client chooses. Scrapers copy QuillBot precisely because site owners allow it. 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.
Paste the IP address from your access log below. You will see whether it belongs to a hosting provider, a residential proxy pool or a Tor exit, plus the ASN that announces it, which is what tells you whether the claim holds up.
Related crawlers
Identify crawlers automatically instead of by hand
Agentscan checks a request against published crawler ranges, reverse DNS and hosting data, then returns a verdict your edge can act on. One call per request, no range files to keep up to date.