AI Crawler User-Agent Lookup

Paste user-agent strings or log lines to identify AI crawlers, and see what each one is for.

How to use

What it checks and how it works

The registry lists the crawlers that OpenAI, Anthropic, Perplexity, Google, Apple, Meta, Amazon, DuckDuckGo, Mistral, Common Crawl and ByteDance describe, each checked against the vendor's own documentation on 28 Oct 2026, with a link to that page. A user-agent header contains the crawler's token, so the tool matches the token as a case-insensitive part of the line. The match shows what a user-agent string claims, not who sent the request: any client can send any string. Vendors publish IP ranges so you can verify a crawler; see their documentation. Google-Extended and Applebot-Extended are control tokens in robots.txt and never appear as a user agent in a request.

Can I trust a user-agent string?

No. Anyone can send any user-agent string. To verify a crawler, check the request's IP address against the ranges the vendor publishes, as described in the vendor's documentation linked on this page.

What is the difference between a training and a search crawler?

Vendors describe training crawlers as collecting content that may be used to train models, and search crawlers as building an index that an assistant answers from. Blocking each has a different effect, shown in the table.

Why is Bytespider marked as undocumented?

ByteDance publishes no documentation for it, so the tool cannot confirm its behavior from a vendor source and says so.

Sources

Related tools

Privacy

Runs in your browser; nothing is uploaded. The interactive tool needs JavaScript.