Back to Posts

Verify Googlebot IP Address: Reverse DNS, 66.249, and IP Ranges

FindMyTeam May 5, 2026

Check whether an IP address is really Googlebot using reverse DNS, forward DNS, 66.249 examples, crawler hostname patterns, and current IP range files.

If your logs show an IP like 66.249.64.226 with a hostname such as crawl-66-249-64-226.googlebot.com, the right question is simple: is this really Googlebot, or is someone pretending?

Do not decide from the user agent alone. User agents are easy to fake.

The practical check is reverse DNS plus forward DNS. For automation, compare the exact source IP with the current crawler IP range file for the crawler category you are checking.

Quick Googlebot verification checklist

Use this order when a request claims to be Googlebot:

  1. Copy the source IP from raw server logs.
  2. Do not trust the User-Agent header by itself.
  3. Run a reverse DNS lookup on the source IP.
  4. Check that the returned hostname matches the crawler category.
  5. Run a forward DNS lookup on that hostname.
  6. Confirm the forward lookup returns the same source IP.
  7. For allowlists or firewall rules, compare the exact IP with the current published crawler IP ranges.

If any step fails, treat the request as unverified.

Quick answer for 66.249.64.226

On May 5, 2026, this local check resolved cleanly:

host 66.249.64.226

226.64.249.66.in-addr.arpa domain name pointer crawl-66-249-64-226.googlebot.com.

Then the hostname resolved back to the same IP:

host crawl-66-249-64-226.googlebot.com

crawl-66-249-64-226.googlebot.com has address 66.249.64.226

That is the pattern you want: the IP points to a Googlebot hostname, and the hostname points back to the same IP.

For searches like 66.249 Googlebot, do not assume every 66.249.x.x address is Googlebot. Verify the exact IP from the log line.

How Google says to verify Googlebot

Google's crawler verification guidance gives two practical options:

  • run a reverse DNS lookup on the source IP, then run a forward DNS lookup on the returned hostname
  • compare the source IP against Google's published crawler IP ranges

For normal server-log checks, the reverse-plus-forward DNS method is usually fast enough.

Google's common crawler hostname pattern includes names like:

crawl-***-***-***-***.googlebot.com
geo-crawl-***-***-***-***.geo.googlebot.com

Other Google crawler and fetcher categories can use different hostname endings, including google.com and googleusercontent.com. Match the hostname category to the crawler type before you make a block or allow decision.

Official references:

The reverse DNS workflow

Start with the IP from your server log.

Run:

host 66.249.64.226

Check whether the returned hostname ends with an expected Google crawler domain such as googlebot.com, google.com, or googleusercontent.com.

Then run a forward lookup on that hostname:

host crawl-66-249-64-226.googlebot.com

If the forward lookup returns the original IP, the result is much stronger.

Why the forward lookup matters

Reverse DNS alone is not enough.

A reverse hostname can look plausible while still being stale, misleading, or unrelated to the current requester. The forward lookup closes the loop. It checks whether the hostname maps back to the same address you started with.

This is often called forward-confirmed reverse DNS.

Reverse DNS vs published Googlebot IP ranges

Reverse DNS is the easiest manual check when you are looking at one suspicious log entry. It is also a good fit for support tickets, crawl debugging, and quick checks of examples like 66.249.64.226.

Published IP ranges are better for code. If you are building a firewall rule, rate-limit exception, or crawler allowlist, use the current JSON file for the crawler category. Common Googlebot crawling belongs to the common crawler range file:

https://developers.google.com/static/crawling/ipranges/common-crawlers.json

Those ranges are written in CIDR notation. Compare the exact source IP against the ranges instead of matching a partial string such as 66.249.

What a fake Googlebot check should look for

A fake Googlebot usually fails in one of these ways:

  • the user agent says Googlebot, but reverse DNS does not return a Google crawler hostname
  • reverse DNS returns a plausible-looking name, but forward DNS does not return the original IP
  • the source IP is outside the current crawler range for the category you are checking
  • the request rate, URL pattern, or blocked path looks inconsistent with normal crawl behavior

Failed verification does not automatically mean the traffic is dangerous. It means you should treat it like untrusted automated traffic until the log context says more.

What to do with the result

If the reverse and forward checks match, treat the request as likely Googlebot and debug it like a crawler request:

  • review robots.txt
  • check status codes
  • check redirects and canonical URLs
  • inspect crawl timing
  • check whether the requested URL should exist
  • review CDN, WAF, and rate-limit rules
  • avoid blocking it just because the request looks automated

If the hostname does not match, or the forward lookup does not return the original IP, treat it as unverified. A bot can say Googlebot in the user agent without being Googlebot.

Where IP lookup fits

Use IP Address Lookup or IP Location for broad context such as ASN, network owner, and location. Use reverse DNS, PTR records, and forward DNS for the crawler identity check.

They answer different questions.

IP lookup helps explain the network. DNS verification helps confirm whether the crawler identity is believable.

FAQ

Is 66.249.64.226 Googlebot?

A local reverse and forward DNS check on May 5, 2026 matched 66.249.64.226 to crawl-66-249-64-226.googlebot.com and back to the same IP. That is the expected verification pattern.

Is every 66.249 address Googlebot?

No. Treat 66.249 Googlebot as a clue, not proof. Check the exact IP from the log with reverse DNS and forward DNS, or compare it with the current crawler IP range file.

What does crawl-66-249-64-226.googlebot.com mean?

It is the reverse DNS hostname returned for the 66.249.64.226 example checked above. The hostname is useful only after the forward lookup points back to the same IP.

Can a user agent prove a request is Googlebot?

No. User agents can be spoofed. Use reverse DNS plus forward DNS, or compare the source IP against Google's published crawler IP ranges.

What is the current Googlebot IP ranges file?

For common Googlebot crawling, use the common crawler range file at https://developers.google.com/static/crawling/ipranges/common-crawlers.json. For other crawler and fetcher categories, use the matching file from Google's crawler verification docs.

Should I block fake Googlebot traffic?

If a request claims to be Googlebot but fails verification, treat it like any other untrusted automated traffic. Check logs, rate, requested paths, and security rules before deciding what to block.

Does an IP location map prove a crawler is Googlebot?

No. Location and ASN are supporting context. Googlebot verification depends on DNS verification or published IP ranges.

Continue reading

Stay in the same investigation track with these closely related guides.

Tools mentioned in this article

Run the same diagnostics to follow along with the guide.