🤖 Overview

Google-Firebase refers to the web crawler operated by Google LLC as part of the Firebase suite, specifically the Firebase Hosting infrastructure and the Firebase CLI deployment tool. According to official Google documentation (firebase.google.com/docs/hosting), this bot is responsible for pre-warming caches on Firebase Hosting, validating deployed static sites, and ensuring that custom domains resolve correctly. It is not a search-engine crawler; instead, it is a health‑check and CDN‑optimisation agent used by Firebase’s globally distributed hosting service.

🌐 Technical Behavior

The Google-Firebase bot issues periodic HEAD and GET requests against deployed sites, typically from Google Cloud’s us-central1 and europe-west1 regions. Based on Firebase Hosting documentation, it does not follow links recursively; it only checks the root path (/) and any paths listed in a site’s rewrites or redirects configuration. Requests are sent at irregular intervals, sometimes every few minutes during deployment validation, then tapering to hourly or daily health checks. The bot uses standard HTTP/1.1 and HTTP/2 protocols and respects Cache-Control headers when checking for content freshness. No publicly published IP range list exists, but observed IPs belong to Google’s 8.8.8.0/24 and 216.58.0.0/16 blocks.

📋 robots.txt Compliance

Firebase Hosting documentation explicitly states that the Google-Firebase crawler does not honor robots.txt because it only performs internal infrastructure tests, not content indexing. However, Firebase recommends using .htaccess or firebase.json rewrites to block paths that should not be accessed by any client. This is a deliberate design choice to ensure that health checks can reach the origin server even if a site misconfigures its robots.txt to disallow the root path.

🔍 Detection Indicators

The primary User‑Agent string is Google-Firebase-Crawler/1.0. A secondary, less common variant is Firebase-CLI/11.x when the deployment tool itself triggers a warm-up request. Behavioral fingerprints include a low request frequency (≤2 requests per minute per IP), absence of Referer headers, and the Via header often showing a Google‑owned proxy. In web server logs, the remote IP’s ASN is always Google LLC (AS15169).

📊 Data Usage

Collected data is used exclusively for Firebase Hosting internal operations: cache pre‑warming, SSL‑certificate validation, and rollback verification after deploys. No content is stored for training, indexing, or analytics. Google’s Firebase privacy policy (firebase.google.com/support/privacy) confirms that only metadata (HTTP status codes, response times) is retained for monitoring.

⚙️ Rate Limiting Policy

Rate limiting is applied because the bot’s health checks can spike during continuous deployment pipelines, potentially consuming connection pools. A threshold of 10 requests per 60 seconds per IP is recommended; blocking this bot would only interfere with site availability monitoring, not security.

ⓘ Data Notice: The information presented above has been compiled from publicly available internet sources. Boteraser aggregates this data solely for informational purposes and does not independently classify, evaluate, or endorse any findings about the bots listed. The accuracy and completeness of this information is the sole responsibility of the original publishers. Boteraser and its operators accept no liability for any decisions made based on this data.