Who actually receives B2B email
Resolved 19 July 2026 // by Mark Glazer, ReplyLead // editorial standards
The short answer: across 8,384,502 business domains that returned an MX record, 54.32 percent are received by Microsoft 365 or Google Workspace. A further 5.88 percent sit behind a security gateway such as Proofpoint, Mimecast or Barracuda, which is a different filtering regime again. So more than half of your cold email is judged by two companies' rules, and roughly one domain in seventeen is judged by a product bought specifically to stop unsolicited mail.
The full census
Every provider we could classify, ordered by share. The filters narrow the table; the whole table is in the page either way.
Showing all 30 providers
| Provider | Domains | Share | Category |
|---|---|---|---|
| Microsoft 365 | 2,387,891 | 28.48% | Google or Microsoft |
| Google Workspace | 2,166,677 | 25.84% | Google or Microsoft |
| Smaller and regional hosts | 1,348,835 | 16.09% | Self-hosted or long tail |
| Self-hosted (own domain) | 1,241,027 | 14.80% | Self-hosted or long tail |
| Proofpoint | 307,368 | 3.67% | Security gateway |
| Hostinger | 138,851 | 1.66% | Email host |
| IONOS / 1&1 | 135,724 | 1.62% | Email host |
| Zoho | 97,967 | 1.17% | Email host |
| GoDaddy | 89,040 | 1.06% | Email host |
| Mimecast | 74,566 | 0.89% | Security gateway |
| Barracuda | 72,239 | 0.86% | Security gateway |
| Rackspace | 55,032 | 0.66% | Email host |
| OVH | 49,157 | 0.59% | Email host |
| Yahoo / AOL | 45,185 | 0.54% | Email host |
| Titan | 38,198 | 0.46% | Email host |
| cPanel-style host | 27,371 | 0.33% | Email host |
| Yandex | 16,490 | 0.20% | Email host |
| Proton | 14,770 | 0.18% | Email host |
| Cisco / IronPort | 12,431 | 0.15% | Security gateway |
| Trend Micro | 11,506 | 0.14% | Security gateway |
| Fastmail | 11,287 | 0.13% | Email host |
| Sophos | 10,674 | 0.13% | Security gateway |
| Apple iCloud | 10,000 | 0.12% | Email host |
| Amazon SES / WorkMail | 7,268 | 0.09% | Email host |
| Mail.ru | 6,656 | 0.08% | Email host |
| Symantec / Broadcom | 3,081 | 0.04% | Security gateway |
| Hushmail | 2,093 | 0.03% | Email host |
| Bluehost / Newfold | 1,679 | 0.02% | Email host |
| Forcepoint | 1,428 | 0.02% | Security gateway |
| Fortinet | 11 | 0.00% | Security gateway |
Why the gateway number is the one that matters
Microsoft and Google filter, but they filter a general population of mail. A security gateway is different: it is a product a company bought on purpose to stop unsolicited email before it reaches a mailbox, and it is usually deployed by larger and more regulated organisations. 493,304 domains, 5.88 percent of the population, sit behind one.
That number is small and it is not evenly distributed. It concentrates in exactly the companies an enterprise-focused outbound programme most wants to reach, which is why a campaign aimed up-market can bounce far harder than its list quality alone would predict. Our own campaign work has run into this directly: gateway rejections, not invalid addresses, drove the bounce rate on programmes targeting larger organisations.
The practical consequence is not "avoid these companies". It is that a bounce rate is not a single number. Segment it by receiving provider before concluding that a list is bad, because a 1 percent bounce on Google-hosted domains and a 6 percent bounce on gateway-hosted domains are two different problems with two different fixes. The thresholds we run to are on deliverability, and what our own campaigns actually measured is on cold email benchmarks.
What this changes about sending
- Two rule sets cover most of the market. At 54.32 percent combined, authentication and reputation practice that satisfies Microsoft and Google covers the majority of any B2B list. That is a simplification worth having.
- Volume per mailbox is a Google and Microsoft question. Their acceptance behaviour is what most of your list will apply, so warmup and per-mailbox pacing should be tuned to them rather than to an average of everyone.
- The long tail is real but small individually. 30.89 percent of domains are self-hosted or on smaller and regional hosts, and no single host in that tail accounts for more than about 3 percent of it. There is no third giant to optimise for.
- Domain-level is not people-level. This census counts domains, not employees or leads. A large enterprise and a two-person consultancy are one row each.
The largest hosts inside the long tail
For completeness, since a bucket labelled "other" is the weakest thing a study can publish. These are the biggest individual MX hosts among the domains we could not attribute to a named provider.
| MX host | Domains |
|---|---|
| xion.oxcs.net | 73,489 |
| antispam.mailspamprotection.com | 44,832 |
| mx.cloudflare.net | 42,981 |
| mx.stackmail.com | 20,607 |
| mx1.mailchannels.net | 19,154 |
| h-email.net | 17,389 |
| registrar-servers.com | 17,268 |
| locaweb.com.br | 16,520 |
| smtpin.rzone.de | 16,073 |
| cust.hostedemail.com | 15,466 |
| park-mx.above.com | 13,831 |
Method
Every distinct email domain in a 188 million-lead B2B contact database was extracted and deduplicated, giving 9,847,723 unique domains. Each was resolved for MX records with aiodns over rotated public resolvers, in five passes so that transient timeouts converge rather than being recorded as failures. Resolution completed on 19 July 2026.
Of those, 8,384,502 returned an MX record and form the population for every share on this page. The remainder break down as 552,369 with no MX but an A record, which is still deliverable under RFC 5321, 662,748 that did not resolve at all, 154,499 with no records, and 93,605 still unresolved after five passes and therefore not claimed either way.
Providers were assigned by matching the MX hostname against a fixed, ordered rule list. Security gateways are matched before tenant hosts, so a Microsoft 365 tenant behind Mimecast is counted as Mimecast. That is deliberate: the gateway is the machine that accepts or refuses the connection. Domains whose MX host contains their own domain name are counted as self-hosted. Everything else is the long tail.
Limitations
- Domain-level, not mailbox-level: one domain is one row regardless of how many leads sit behind it, so this is not weighted by company size.
- Gateways are classified ahead of tenant hosts, so a Microsoft 365 tenant sitting behind Mimecast counts as Mimecast. That is deliberate: the gateway is the box that accepts the connection, and it is what decides whether the message arrives.
- 'Self-hosted (own domain)' means the MX host contains the domain's own name. That is a good proxy for self-hosting but it will also catch some hosts that white-label onto a customer subdomain.
- 'Smaller and regional hosts' is a long tail, not one population. The largest single host in it accounts for under 3 percent of that bucket.
- The population is the email domains present in one B2B lead database, not the internet. It skews to companies that appear in commercial contact data.
- Resolved on 2026-07-19 across 5 passes. MX records change.
The classification rules, the counts and the residual breakdown are all reproducible from the same resolution database, and every share on this page is a single division of two counts stated above.
Where to go next
For what our own campaigns measured, including a 14x spread in reply rate between campaigns, see cold email benchmarks. For the sending-side practice this implies, see deliverability. For what an outbound programme costs to run at volume, see what a cold email agency costs, and for who should own each part of it, done-for-you outbound.
Want your list segmented by receiving provider before you send? It changes what a bounce rate means and it is the first thing we do on a new programme. Tell us the ICP and we will show you the split.
Apply to work with us