Verify Crawler IP
Verify a crawler IP in one step: find out whether a request that claims to be Googlebot, Bingbot, GPTBot or ClaudeBot really came from that operator. We check the IP against 19 official crawler IP range files from 10 operators.
The user agent is compared in your browser and never sent to us. Only the IP is looked up.
A user agent is a claim. The IP is the proof.
Anyone can send "Googlebot" in a request header. Only Google can send it from Google's crawler addresses, so the honest check is whether the IP sits inside the ranges the operator publishes.
- The IP is looked up against the operators' own range files, re-fetched daily
- The user agent is compared in your browser, so it never leaves the page
- A mismatch between the two is the clearest sign of a fake crawler

Which crawlers we verify by IP.
We load 19 machine-readable IP range files published by 10 operators. Everything else gets an honest "can't verify by IP" answer instead of a guess.
Search engines
Google (five files, including Googlebot, special crawlers and user-triggered fetchers), Bingbot, Applebot and DuckDuckBot.
AI crawlers and assistants
GPTBot, ChatGPT-User and OAI-SearchBot from OpenAI, ClaudeBot, Claude-User and Claude-SearchBot from Anthropic, PerplexityBot and Perplexity-User, Mistral's two bots and DuckAssistBot.
SEO and archive bots
AhrefsBot and Common Crawl's CCBot. Meta publishes no range file, so a Meta crawler can only be matched to Meta's network, never verified.
Frequently asked questions
- Search engines and AI companies publish JSON files listing the IP ranges their crawlers use. We fetch 19 of these files daily and check whether the IP you enter falls inside one of them. A match returns the bot's name, its operator and verification_method "ip_range_list".
- Paste the request's IP and user agent. A fake Googlebot sends Googlebot's user agent from an address outside Google's published crawler ranges, so the tool shows a mismatch. Without the user agent, you only learn whether the IP belongs to a known crawler.
- Run a reverse DNS lookup on the IP. A real Google crawler hostname ends in googlebot.com, google.com or googleusercontent.com. Then run a forward lookup on that hostname and check it returns the same IP. Our tool does the equivalent check against Google's published range files.
- No. The comparison runs in your browser. Only the IP is looked up, the same way as on our other free tools.
- Some operators, such as Yandex, Baidu and Amazon, don't publish a range file that we load. For those the tool says it can't verify the bot by IP. Use a reverse DNS lookup on the IP, then a forward lookup on the hostname, and check it matches the operator's documented domain.
- The range files are re-fetched daily and our lookup database is rebuilt every night, so a prefix an operator adds today can take up to about two days to show as verified. If a crawler you trust fails the check, confirm it with reverse DNS before blocking.
- Crawlers often run on cloud networks whose addresses also appear on abuse lists. Verification lowers the fraud score but doesn't hide the other signals, so you see the whole record and decide.
- Yes. Every API lookup returns threat.crawler with verified, name and operator. Compare the operator with the bot your request's user agent claims, and treat a mismatch as unverified. The API can't see your user agents, so that comparison stays in your code.
Every check, one API call.
IP Lookup
The complete report for any IPv4 or IPv6 address: location, network, detections, risk score.
What Is My IP
Your public IP, where it places you, and what every website can infer from it.
VPN Detection Test
Check whether an IP is a VPN or proxy exit, with the provider named when known.
IP Fraud Score Check
A 0–100 risk score with the exact signals that produced it.
Datacenter IP Check
Find out if an IP belongs to a hosting provider or cloud platform.
Need this at scale?
Get 1,500 free API lookups a day, every field included, no credit card. These tools run on the same endpoint you would ship to production.