Google IP Checker
Checks whether an IP address belongs to Google's official ranges (Googlebot). The list is verified against Google's published ranges. Synced: April 6.
| IP address | Status |
|---|
What the tool checks
This page compares IP addresses with Google's published network ranges and shows whether each one matches. The most common reason is to filter fake Googlebot hits out of server logs. Other bots often send a Googlebot User-Agent so that nobody blocks them. The check runs in your browser, and no sign-up is needed.
These are the tasks where it helps most often:
- log analysis: separate real Google visits from fake ones before you count crawls;
- firewall, WAF or rate-limit setup: make sure a rule won't catch Google's addresses;
- server load investigation: find out whether an overly active "Googlebot" really comes from Google's networks.
For disputed addresses, follow this check with the DNS check described below.
How to use it
Paste the addresses into the "IP addresses (one per line)" field, click "Check" and look at the "Status" column in the table. Both IPv4 and IPv6 work. The tool ignores empty lines and spaces at the edges of a line. Enter each address without a port or subnet mask: the format isn't validated, so a typo can produce a wrong result.
How to read the result
Each line gets the status "Google (Googlebot)" or "Not Google", and matching rows are
highlighted. The first status only means that the address belongs to a Google network. The
list is broader than the crawler ranges and includes, for example, 8.8.8.0/24
of Google Public DNS and large 34.x.x.x and 35.x.x.x blocks used
by Google Cloud. Anyone can rent a Google Cloud server, so a match does not prove that the
request came from Googlebot.
If a request with a Googlebot User-Agent gets "Not Google", that is a strong sign of a fake.
As of October 2026, every range in Google's published crawler list
(common-crawlers.json) falls inside the built-in list.
How to confirm Googlebot for sure
Google recommends verifying its crawlers through DNS. This tool makes no DNS lookups, so for
disputed addresses run the check by hand. Google's documentation uses the host
command for it.
The steps are:
- Run a reverse DNS lookup on the IP, for example
host 66.249.66.1. - Make sure the hostname ends in
googlebot.com,google.comorgoogleusercontent.com. For Googlebot itself it isgooglebot.com. - Run a forward DNS lookup on that hostname and check that it returns the same IP.
If both conditions hold, the request really came from a Google crawler or service. Without this check, treat the status in the table as preliminary.
Data source and limitations
The list of IPv4 and IPv6 ranges is built into the page code. It is a snapshot of Google's
general IP list (goog.json), and the sync date is shown under the heading.
Ranges that Google adds later won't be recognised until the list is updated. Addresses are
not sent anywhere: the comparison runs in your browser.
Sources
The verification method and the IP lists are described in Google's official documentation. You can check everything above against these pages.
- Verify requests from Google crawlers and fetchers: the reverse and forward DNS check, crawler domains and links to the IP lists.
- goog.json: Google's general list of IP ranges.
- common-crawlers.json: the narrower list for Googlebot and Google's other common crawlers.