Firebase (Google) SaaS sender
According to Live Direct Marketing's daily Tranco top-1M scan (September 16, 2026), Firebase (Google) is the SaaS sender for 1,860 domains — 0.29% of 634,905 SPF-publishing domains. Detection method: include: mechanisms in the SPF record.
Key facts
- 1,860 domains in the Tranco top-1M use Firebase (Google) (0.29% of SPF-publishing domains).
- Snapshot date: 2026-09-16 — recomputed every day.
- 30-day share change: +0.00 pp.
- Strongest TLD: .com (51.6% of its domains).
- Most co-used service: Google Workspace.
- Directory category: SaaS sender.
Why Firebase (Google) appears in this category
Firebase — Google mobile and web app backend platform sending auth, password-reset and project notification emails.
We classify it as a SaaS sender from include: mechanisms in the SPF record matching a maintained provider rule. This is infrastructure attribution from public DNS, not evidence of a direct contract or exclusive use.
Firebase is Google's cloud application platform, offering backend-as-a-service capabilities including email sending for transactional and event-triggered workflows. Google operates Firebase as part of its cloud infrastructure, and organisations using Firebase for email route their outbound mail through Google's SMTP infrastructure and authentication systems.
Firebase's footprint is concentrated in smaller and mid-market .com domains, reflecting adoption among startups and growing teams rather than enterprises. For deliverability professionals and senders testing against a realistic cross-section of domains, Firebase represents a common authentication infrastructure choice in the smaller-organisation segment and should be understood as a characteristic sending posture in that market.
Where Firebase (Google) sits in the Tranco ranking
| Tranco rank band | Domains | Share of its base |
|---|---|---|
| Top 1,000 | 0 | 0.0% |
| Top 10,000 | 21 | 1.1% |
| Top 100,000 | 244 | 13.1% |
| Top 1,000,000 | 1,590 | 85.5% |
| Unranked | 5 | 0.3% |
Top-level domain split
| TLD | Domains | Share | |
|---|---|---|---|
| .com | 959 | 51.6% | |
| .io | 95 | 5.1% | |
| .ai | 85 | 4.6% | |
| .org | 56 | 3.0% | |
| .app | 54 | 2.9% | |
| .net | 45 | 2.4% | |
| .co | 42 | 2.3% | |
| .com.br | 35 | 1.9% | |
| .jp | 30 | 1.6% | |
| .de | 21 | 1.1% |
What Firebase (Google) users also use
Cross-tabulated from the same daily snapshot — the other email services seen on the same 1,860 domains.
| Type | Service | Domains | Share of Firebase (Google) users |
|---|---|---|---|
| Mailbox | Google Workspace | 1,081 | 58.1% |
| Mailbox | Microsoft 365 | 223 | 12.0% |
| Mailbox | Self-Hosted | 78 | 4.2% |
| Mailbox | Generic / unmatched (mail.*) | 56 | 3.0% |
| Mailbox | OpenSRS (Tucows) | 35 | 1.9% |
| Mailbox | Unknown / Other | 33 | 1.8% |
Multi-tenant IP pools and shared reputation in Firebase's email model
Firebase publishes SPF include mechanisms that authorise its SMTP servers to send on a domain's behalf. Because Firebase's email service is shared across many lightweight applications, outbound IP addresses are typically pooled across multiple Firebase tenants. This means domains sending via Firebase inherit both the reliability of Google's infrastructure and the reputation consequences of other applications on the same IP ranges; if other Firebase users send to spam traps or exhibit poor authentication practices, it can degrade delivery rates for the entire pool. This pooled-reputation dynamic is intrinsic to managed email services targeting smaller organisations and requires monitoring if Firebase is a primary send channel.
See the full Firebase (Google) data page (KPI cards, trend, sample domains) →
Run a free inbox-placement test across Gmail, Outlook, Yahoo and more — see exactly where your mail lands and why.
Frequently asked questions
What is Firebase and why do I see it in SPF records?
Firebase is Google's cloud platform for building web and mobile applications, with backend services including email sending. When a domain uses Firebase for email, it adds Firebase's SPF include to its SPF record, authorising Firebase's SMTP infrastructure to authenticate mail on that domain's behalf.
How many domains use Firebase (Google)?
1,860 domains in the Tranco top-1M use Firebase (Google) as their SaaS sender as of September 16, 2026 (0.29% of SPF-publishing domains), according to Live Direct Marketing's daily DNS scan.
Is Firebase (Google) common enough to affect email deliverability testing?
Firebase (Google) accounts for 0.29% of SPF-publishing domains in the top 1M. Whether you should seed a test mailbox there depends on how much of your audience it represents — the co-usage table above shows the services it appears alongside most.
Is Firebase (Google) growing or declining?
Firebase (Google) has been stable — its share moved +0.00 pp over the last 30 days (as of September 16, 2026).
Which countries or TLDs use Firebase (Google) most?
Firebase (Google)'s largest TLD is .com (51.6% of its domains); it appears across 173 TLDs in total.