Bot traffic checker: paste up to 1,000 IP addresses or raw server log lines. You get one row per address and a bar with the share of datacenter, crawler, VPN or proxy, and no match. Why this matters: bot traffic.
What you get
| result | meaning |
|---|---|
| Known crawler | the address is on the owner’s published list for that bot (Googlebot, Bingbot, GPTBot, PerplexityBot, Applebot and more) |
| Datacenter | a cloud or hosting provider owns the range (AWS, Google Cloud, Azure, Oracle, Cloudflare, DigitalOcean, Linode, Fastly, others) |
| VPN, proxy or Tor | the range is on a public VPN list, the Tor exit list, or a list of proxies bots used lately |
| No match | on none of the lists: most often a home or mobile connection, sometimes a proxy we cannot see |
| Private address | 10.x, 192.168.x and similar: your own network or proxy, not the visitor |
| Fake crawler | log lines only: the user agent names a bot we have a list for, the address is not on that list |
Log lines: only the first address of each line is read (the client). A line with nothing but addresses counts all of them. Limits: 1,000 different addresses, 50,000 lines.
Where the ranges come from
Each list is the owner’s own file, fetched on the date shown in the tool.
| list | source |
|---|---|
| Googlebot, special crawlers, user-triggered fetchers | Google crawler IP files |
| Bingbot | bing.com/toolbox/bingbot.json |
| GPTBot, OAI-SearchBot, ChatGPT-User | openai.com/gptbot.json, searchbot.json, chatgpt-user.json |
| PerplexityBot, Perplexity-User | perplexitybot.json, perplexity-user.json |
| Applebot, DuckDuckBot, Amazonbot, AhrefsBot, CCBot | Apple, DuckDuckGo, Amazon, Ahrefs, Common Crawl |
| AWS, Google Cloud, Azure, Oracle Cloud | AWS, Google Cloud, Azure, Oracle |
| Cloudflare, Fastly, DigitalOcean, Linode | Cloudflare, Fastly, DigitalOcean, Linode |
| Tor exit nodes | Tor Project bulk exit list |
| Other datacenter and hosting ranges, VPN ranges | X4BNet/lists_vpn |
| Proxies used by bots in the 5 days before the date | antoinevastel/avastel-bot-ips-lists |
An address on several lists gets the most specific name: crawler first, then Tor, then a named cloud, then the generic lists.
What it cannot see
- Residential proxies and botnets on home connections. They show as “No match”, the same as a person.
- Which datacenter visitors are people. A staff member on a company VPN shows as datacenter.
- Bots not named above: ClaudeBot (we found no published address list), Meta, Yandex, Baidu, Semrush and others. A claim to be one is not checked.
- Changes since the date shown. Cloud providers move ranges often.
- IPv6 beyond the first 64 bits, the part that names the network.
For what a site’s own bot protection and robots.txt say, use the anti-bot detector and the AI crawler checker.