Googlebot IP Addresses: 1,800+ IPs Updated Daily (All 4 Crawler Types)

Complete and up-to-date list of all Google crawler IP addresses and networks (CIDR ranges), including the new Google-Agent (Project Mariner). Data is fetched directly from Google Search Central’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: 1,799 IP networks (CIDR blocks)
• Update Frequency: Updated daily from Google’s official JSON API
• Data Source: Google Search Central Documentation
• Last Update: 2026-04-15
• 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

Google’s 4 Types of Crawlers

Google uses 4 types of crawlers, each with its own purpose and IP list:

1. Common Crawlers (Regular Googlebot)

Regular crawlers used for Google products like Google Search. Always respect robots.txt.

• Reverse DNS: crawl-***-***-***-***.googlebot.com or geo-crawl-***-***-***-***.geo.googlebot.com
• Quantity: 164 networks (128 IPv6 + 36 IPv4)

2. Special-Case Crawlers

Crawlers that perform specific functions (like AdsBot) where there’s an agreement between the site and the product. May ignore robots.txt.

• Reverse DNS: rate-limited-proxy-***-***-***-***.google.com
• Quantity: 280 networks (128 IPv6 + 152 IPv4)

3. User-Triggered Fetchers

Tools and functions where the end user triggers the fetch (like Google Site Verifier). Ignore robots.txt because they’re user-initiated.

• Reverse DNS:
  • ***-***-***-***.gae.googleusercontent.com
  • google-proxy-***-***-***-***.google.com
• Quantity: 1,351 networks (724 IPv6 + 627 IPv4)

4. User-Triggered Agents (NEW)

AI agents that browse the web on behalf of users. This is a new category, separate from User-Triggered Fetchers. Currently used by Project Mariner — Google’s AI agent that navigates websites and executes actions on user request. Ignore robots.txt because the fetch is user-initiated.

• User Agent: Google-Agent (full Chrome-like UA string with Google-Agent identifier)
• Reverse DNS: google-proxy-***-***-***-***.google.com
• Quantity: 4 networks (3 IPv4 + 1 IPv6)
• Authentication: Google is experimenting with the web-bot-auth protocol using the agent.bot.goog identity

IP Address Statistics

Network Distribution by Type

CIDR Block Ranges

The smallest block is /32 (single IP), largest is /19 (8,192 IPs), with most being /24 blocks (256 IPs each).

Comparing Googlebot to Other Crawlers

Unlike Googlebot’s 1,799 published IP ranges, other crawlers take different approaches:

• Googlebot: Full list published and updated daily
• Bingbot: No published list, verification via reverse DNS only
• 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/19 -j ACCEPT

Use in Nginx

# geo block to identify Googlebot
geo $is_googlebot {
    default 0;
    66.249.64.0/19 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/search/apis/ipranges/googlebot.json

# Example response structure
{
  "creationTime": "2025-11-12T00:00:00.000000Z",
  "prefixes": [
    {
      "ipv4Prefix": "66.249.64.0/19"
    },
    {
      "ipv6Prefix": "2001:4860::/32"
    }
  ]
}

Google updates these files daily, usually around midnight UTC.

Sources

• Google Search Central - Verifying Googlebot

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