Googlebot IP Addresses: 2,000+ IPs Updated Daily (All 5 IP Files)

Complete and up-to-date list of all Google crawler IP addresses and networks (CIDR ranges), across all five of Google’s official IP files. Data is fetched directly from Google’s official API and updates daily.

About This IP Database

This database contains all official Googlebot IP addresses and CIDR ranges published by Google.

• Total Networks: 2,111 IP networks (CIDR blocks)
• Update Frequency: Updated daily from Google’s official JSON API
• Data Source: Google Search Central Documentation
• Last Update: 2026-07-26
• Coverage: IPv4 and IPv6 addresses
• Format: Searchable table with CIDR notation

JSON File Access

Download the raw JSON data directly from Google:

• Common Crawlers JSON
• Special Crawlers JSON
• User-Triggered Fetchers JSON
• User-Triggered Fetchers (Google) JSON
• User-Triggered Agents JSON

Why Do You Need This List?

If you manage a website, application, or server, it’s important to identify legitimate Googlebot requests. For technical SEO professionals and site administrators, this list is essential for:

1. Security - Block fake bots pretending to be Googlebot
2. Optimization - Prioritize legitimate Google requests
3. Monitoring - Identify Googlebot crawl patterns in logs
4. Debugging - Troubleshoot indexing issues in Search Console

Three Categories, Five IP Files

This is the part that trips people up, so it is worth settling first.

Google’s documentation defines three categories of crawler: common crawlers, special-case crawlers, and user-triggered fetchers. But Google publishes five JSON files of IP ranges. The numbers do not line up because the third category spans three separate files.

To verify a request, check it against the right file rather than the right category.

1. Common Crawlers (Regular Googlebot)

The classic crawlers behind Google Search.

• Reverse DNS: crawl-***-***-***-***.googlebot.com or geo-crawl-***-***-***-***.geo.googlebot.com
• Quantity: 315 (169 IPv4, 146 IPv6) networks

2. Special-Case Crawlers

Crawlers tied to specific products, mainly advertising ones like AdsBot.

• Reverse DNS: rate-limited-proxy-***-***-***-***.google.com
• Quantity: 270 (135 IPv4, 135 IPv6) networks

3. User-Triggered Fetchers

Tools and functions where the end user triggers the fetch, such as Google Site Verifier and Read Aloud, plus Google’s AI agents.

This is the category that spans three files, and the difference between them is what makes verification work:

• user-triggered-fetchers.json for fetches that do not run on Google infrastructure, whose reverse DNS ends in gae.googleusercontent.com

• user-triggered-fetchers-google.json for fetches Google itself operates, whose reverse DNS ends in google.com

• user-triggered-agents.json, the dedicated file for Google’s AI agents

• Quantity across both fetcher files: 1,506 (753 IPv4, 753 IPv6) networks

• Quantity in the agents file: 20 (12 IPv4, 8 IPv6) networks

The table above breaks the agents file out on its own because its IP ranges are separate. That is a split between IP lists, not a fourth category of crawler. In Google’s documentation those agents sit inside this category.

IP Address Statistics

Network Distribution by Type

CIDR Block Ranges

Google has moved to publishing small, uniform blocks instead of broad ranges: most IPv4 blocks are /27 (32 IPs each) and most IPv6 blocks are /64. The smallest block is /28 and the largest is /16.

Comparing Googlebot to Other Crawlers

Unlike Googlebot’s 2,111 published IP ranges, other crawlers take different approaches:

• Googlebot: Full list published and updated daily
• Bingbot: Published list at bing.com/toolbox/bingbot.json, plus reverse DNS verification
• Facebook Crawler: Limited published ranges
• Semrush Bot: Published list available

Having a complete, updated list lets you whitelist legitimate crawlers in your firewall, analyze crawler behavior in logs, and optimize server resources for important bots.

How to Use This List

Check Using the On-Page Tool

Enter an IP address in the search field above and the tool will automatically check if it’s in one of the official networks.

Check Using Reverse DNS

# Linux / macOS
host 66.249.66.1

# Windows
nslookup 66.249.66.1

If it’s legitimate Googlebot, you’ll get a result like:

1.66.249.66.in-addr.arpa domain name pointer crawl-66-249-66-1.googlebot.com

Block/Allow in Firewall

If you want to block or allow only legitimate Googlebot, use the CIDR block list. Example for iptables:

# Allow Googlebot
iptables -A INPUT -s 66.249.64.0/27 -j ACCEPT

Use in Nginx

# geo block to identify Googlebot
geo $is_googlebot {
    default 0;
    66.249.64.0/27 1;
    # ... other networks
}

Use the JSON API Programmatically

For automated systems, fetch the JSON directly:

# Download all Googlebot IPs
curl https://developers.google.com/static/crawling/ipranges/common-crawlers.json

# Example response structure
{
  "creationTime": "2026-07-24T14:46:00.000000",
  "prefixes": [
    {
      "ipv4Prefix": "66.249.64.0/27"
    },
    {
      "ipv6Prefix": "2001:4860:4801:10::/64"
    }
  ]
}

Google updates these files daily.

Sources

• Google Search Central - Verifying Googlebot

Last updated: Data updates daily from Google’s official API.