Free tool Fake bot checker: Googlebot verification for any crawler IP
Anyone can put “Googlebot” in a user agent; scrapers do it to get past firewalls and rate limits. The only proof is where the request came from. Paste the IP address (and, if you have it, the user agent) and this tool runs the check each operator documents: reverse DNS, the hostname suffix, a forward lookup back to the same address, and the operator’s published IP list.
- Each operator’s own method
- 11 operators, 23 IP lists
- Sent only when you click
Verify a crawler IP address
The user agent is optional: paste it to check the claim, or leave it empty to ask “whose crawler is this address?”. The results below are a sample, dated, until you click Verify.
cloudflare-dns.com), Google (dns.google) or Alibaba Cloud (dns.alidns.com) — for the reverse name of the address, the hostname it finds, and Team Cymru’s network record (a DNS name that contains the address). The user agent never leaves your browser. The official IP lists are a file on tapcub.com, compared locally.From your access log, CDN log or firewall event.
Alibaba Cloud usually works from mainland China.
The full string or just the bot name, e.g. Googlebot, bingbot, GPTBot.
Verdict
- VerifiedReal Google crawler: verified by crawl-66-249-66-1.googlebot.com.
- NoteSample result: checked on 2026-11-17 while building this page. Click Verify for live data.
Checks
Each line is one step of the operator’s documented method.
| Check | Result | Detail |
|---|---|---|
| Claimed crawler | Verified by reverse DNS ending in googlebot.com, google.com, googleusercontent.com, then a forward lookup | |
| Reverse DNS (PTR) | crawl-66-249-66-1.googlebot.com | Ends in googlebot.com: Google |
| Forward lookup | Points back to this address | 66.249.66.1 |
| Official IP list | Google · Googlebot, Google-InspectionTool, GoogleOther, Storebot-Google | 66.249.66.0/27 |
| Network (ASN) | AS15169 GOOGLE - Google LLC, US | 66.249.64.0/20 |
Version v1.0Updated Update history
What the verdicts mean
A crawler is identified by where it connects from, never by what it calls itself.
Verified
The address reverse-resolves to the operator’s documented domain and that name points back, or the address is on the operator’s published list. Allow it, and its traffic is genuinely that crawler.
Fake
The request claims a crawler name, but the address belongs to someone else. Usually a scraper, an SEO tool or a vulnerability scanner borrowing a trusted name. Rate-limit or block it without hurting your search visibility.
Another operator
The address is a real crawler, just not the one the user agent names. Rare, but it happens with misconfigured tools; trust the address, not the name.
Cannot verify
Some operators publish neither host names nor IP lists, so no one can prove their crawlers are real. Judge those by behaviour: do they read robots.txt and keep a sensible rate?
Google, Bing, Baidu, Yandex, Apple, Common Crawl and Ahrefs document the DNS check; OpenAI, Anthropic, Perplexity, DuckDuckGo, Amazon and Mistral publish IP lists only. Both methods are equally conclusive when they pass.
Three steps
No sign-up. One click sends the queries.
-
1
Copy the IP from your logs
The client address of the request, not a proxy’s. Behind a CDN, use the header it adds (such as CF-Connecting-IP).
-
2
Add the user agent
Paste the full user agent or just the bot name. Leave it empty to ask whose crawler the address is.
-
3
Verify and act
Verified: allow it. Fake: rate-limit or block it. Check a whole log at once with the crawler IP range checker.
The documented check, step by step
This is the method Google, Bing, Baidu and Yandex describe in their webmaster guides, plus the official IP lists.
- Reverse DNS: read the PTR record of the address (for example
1.66.249.66.in-addr.arpa) - Suffix: the hostname must end in a domain the operator documents, such as
googlebot.com,search.msn.comorbaidu.com. The whole label must match:googlebot.com.evil.netdoes not count - Forward lookup: look up that hostname’s A (or AAAA) record. It must include the original address; anyone can set a reverse name, but only the domain owner controls the forward record
- IP lists: compare the address with the operator’s published JSON files (23 lists from 11 operators, fetched 2026-11-17)
- Either method passing is enough. For a request that claims Googlebot, the tool also checks it is Google’s common crawler and not AdsBot or a user-triggered fetcher
| Operator | Reverse DNS ends in | Published IP list |
|---|---|---|
googlebot.com, google.com, googleusercontent.com | Yes (5 files) | |
| Microsoft Bing | search.msn.com | Yes |
| Baidu | baidu.com, baidu.jp | — |
| Yandex | yandex.ru, yandex.net, yandex.com | — |
| Apple | applebot.apple.com | Yes |
| Common Crawl | crawl.commoncrawl.org (IPv4) | Yes |
| Ahrefs | ahrefs.com, ahrefs.net | Yes |
| OpenAI, Anthropic, Perplexity, DuckDuckGo, Amazon, Mistral AI | — | Yes |
Real or fake: the same user agent from two addresses
Both requests say “Googlebot/2.1”. Only the address tells them apart (checked on 2026-11-17).
| Check | 66.249.66.1 | 45.33.32.156 |
|---|---|---|
| Reverse DNS | crawl-66-249-66-1.googlebot.com | scanme.nmap.org |
| Ends in a Google domain? | Yes, googlebot.com | No |
| Forward lookup | 66.249.66.1: points back | Not needed |
| On Google’s IP lists? | Yes, 66.249.66.0/27 (common crawlers) | No |
| Network | AS15169 Google | AS63949 Akamai (Linode) |
| Verdict | Real Googlebot | Fake Googlebot |
45.33.32.156 is scanme.nmap.org, a host the Nmap project keeps for people to test against. Click “Try: a fake Googlebot” to run it live.
How bot verification goes wrong
Each of these lets fakes through or blocks the real crawler.
Stopping at the reverse name
Anyone who controls an address block can set its PTR to crawl.googlebot.com. Without the forward lookup the check proves nothing.
Substring matching
“contains googlebot.com” also matches googlebot.com.attacker.net. Match the whole domain at the end of the name.
Checking the proxy’s address
Behind a CDN or load balancer, the connecting address is the proxy. Verify the client address from the forwarding header, or every check fails.
Hard-coding old IP lists
Google, OpenAI and others change their lists every few weeks. Re-download them on a schedule; this tool’s lists are dated.
Verified crawlers in your bot reports
TapCub separates people from bots on every visit, and checks crawler identity where it can.
Verified or suspected
Crawler hits sent from your server or imported logs get the same reverse-and-forward DNS check for crawlers that publish verification host names, and are marked verified or suspected.
Learn moreFive layers of bot detection
User agent, headers, client signals, network and rate keep bots out of the visitor numbers, real or fake.
Learn moreTapCub’s own bots
TapCub’s crawlers say who they are in the user agent and explain how to reach us about them.
Learn moreGooglebot verification questions
Still have a question?
Chat with the team behind TapCub — we usually reply within a few hours on business days.
How do I verify Googlebot?
Take the IP from your log, look up its reverse DNS, check that the name ends in googlebot.com, google.com or googleusercontent.com, then look that name up again and confirm it returns the same IP. Or match the IP against Google’s published JSON lists. This tool does both.
How can I tell if a bot is fake?
Check the address, not the user agent. If a request claims to be Googlebot, Bingbot or Baiduspider but the IP neither reverse-resolves to that operator’s domain (with a matching forward lookup) nor sits in its published ranges, it is fake.
Is it safe to block fake Googlebots?
Yes, once verified as fake. Real Googlebot always passes the check, so blocking failures does not affect your search visibility. Be careful with addresses behind your own proxy; verify the real client address.
How do I verify GPTBot, ClaudeBot or PerplexityBot?
OpenAI, Anthropic and Perplexity publish IP lists instead of host names. Match the address against gptbot.json, searchbot.json and chatgpt-user.json (OpenAI), claude.com/crawling/bots.json (Anthropic) or perplexitybot.json (Perplexity). The tool does it with the lists fetched on 2026-11-17.
How do I verify Baiduspider?
Baidu documents the same two steps: the reverse name must end in baidu.com or baidu.jp, and a forward lookup must return the same IP. Baidu publishes no IP list. Some old Baidu addresses keep a reverse name without a forward record; the tool reports those as not verified rather than verified.
Why does a real Google IP fail the Googlebot check?
Google also fetches pages through AdsBot, user-triggered fetchers (Site Verifier, feed readers, Google Cloud sites) and other agents. They are Google, but not Googlebot, and some ignore robots.txt. The tool tells you which kind it found.
Can I verify bots automatically on my server?
Yes: cache the result per IP for a day, use the operators’ JSON lists for bulk checks, and fall back to DNS for operators without lists. TapCub does this for crawler hits it receives from your server or logs.
Update history
New features, fixes and data refreshes for this tool, newest first.
-
· v1.0
LaunchedFirst release.
Data this tool relies on
- Official crawler IP ranges (Google, Bing, OpenAI, Anthropic…) — checked 2026-11-17, reviewed every 1 months (next review by 2026-12-17)
- Sample DNS lookups shown before you click — checked 2026-11-17, reviewed every 6 months (next review by 2027-05-17)
Missing something or found an error? Tell us — requests that come up often go into the next update. All tool updates
Know which crawlers read your site
TapCub separates people, search engines and AI crawlers and shows what each crawler fetched, next to the visitors it sends back.