Every bot we track, every IP range its operator publishes, and every time those ranges change. 4,680 ranges across 15 verifiable crawlers.
Paste an IP address from your access logs. We check it against every range the operators publish.
Publishing an IP range list does not mean it is stable. Some operators have not touched theirs in years. Others rewrite them constantly, because the crawler is triggered by users in real time and its capacity follows demand. Treating any of these lists as a one-off download is how you end up rejecting real traffic as spoofed.
These operators publish a machine-readable list of the addresses their crawlers use, so a hit claiming to be them can be confirmed or rejected. The movement column covers the last 90 days.
| Bot | Operator | Ranges | Movement (90d) | Source updated |
|---|---|---|---|---|
| Amazonbot | Amazon | 1292 | +768 / -0 | 2026-09-08 |
| Amzn-SearchBot | Amazon | 816 | +304 / -0 | 2026-09-08 |
| Claude bots | Anthropic | 38 | +38 / -0 | 2026-10-07 |
| Applebot | Apple | 24 | +21 / -9 | 2026-09-15 |
| Googlebot | 317 | +6 / -0 | 2026-10-09 | |
| Special crawlers (AdsBot...) | 272 | +6 / -0 | 2026-10-09 | |
| User-triggered agents | 20 | no change | 2026-10-09 | |
| User-triggered fetchers | 1068 | +20 / -0 | 2026-10-09 | |
| User-triggered fetchers (Google) | 502 | +54 / -0 | 2026-10-09 | |
| bingbot | Microsoft | 28 | no change | 2024-01-03 |
| ChatGPT-User | OpenAI | 234 | +116 / -129 | 2026-10-07 |
| GPTBot | OpenAI | 18 | +0 / -3 | 2026-09-22 |
| OAI-SearchBot | OpenAI | 39 | +4 / -0 | 2026-01-02 |
| Perplexity-User | Perplexity | 4 | no change | 2025-10-17 |
| PerplexityBot | Perplexity | 8 | no change | 2025-02-07 |
These operators publish no address list. Their user-agent can be copied by anyone, so a hit claiming to be one of them proves nothing on its own.
The column below lists what is theoretically available to check them. It is not what this registry does: we verify against published ranges only, and we run no reverse DNS lookup.
| Bots | Operator | What could be checked | Note |
|---|---|---|---|
| meta-externalagent, facebookexternalhit | Meta | None | No IP range published. |
| GrokBot, xAI-Grok, Grok-DeepSearch | xAI | None | No documentation. Rotating residential addresses, and the user-agent is often disguised. |
| MistralAI-User | Mistral | User-agent and robots.txt | No IP file published. See docs.mistral.ai/robots. |
| Date | Bot | Change | Total |
|---|---|---|---|
| 2026-10-10 | User-triggered fetchers | +6 / -0 | 1062 to 1068 |
| 2026-10-08 | Claude bots | +10 / -0 | 28 to 38 |
| 2026-10-08 | ChatGPT-User | +0 / -1 | 235 to 234 |
| 2026-10-07 | ChatGPT-User | +5 / -0 | 230 to 235 |
| 2026-10-03 | Claude bots | +2 / -0 | 26 to 28 |
| 2026-10-03 | User-triggered fetchers | +2 / -0 | 1060 to 1062 |
| 2026-10-02 | User-triggered fetchers (Google) | +2 / -0 | 500 to 502 |
| 2026-10-02 | User-triggered fetchers | +2 / -0 | 1058 to 1060 |
| 2026-09-29 | User-triggered fetchers (Google) | +4 / -0 | 496 to 500 |
| 2026-09-26 | ChatGPT-User | +1 / -0 | 229 to 230 |
| 2026-09-23 | ChatGPT-User | +4 / -0 | 225 to 229 |
| 2026-09-23 | GPTBot | +0 / -3 | 21 to 18 |
Everything on this page is available as JSON, and as a flat text list you can drop straight into a firewall rule. No key, no sign-up, no rate limit beyond basic abuse protection.
GET /v1/bots every tracked bot and its metadata
GET /v1/ranges the full snapshot, all ranges
GET /v1/ranges.txt one CIDR per line, ready for a firewall rule
GET /v1/verify?ip=1.2.3.4 which bot owns this address
GET /v1/changes the full change history
GET /v1/volatility which bots move, and how much