Mailbox on one platform, sender authorised on another
In the November 2026 census, 62,799,771 domains publish an SPF (Sender Policy Framework) record and a primary MX (Mail Exchange) host that each name a mail vendor the census recognises. For 7,852,831 of them, 12.5%, the two name different vendors: mail arrives at one company, and SPF authorises another to send the domain’s mail.
Most of that is how the setups are built. 4,792,398 of the mismatched domains, 61.0%, use a host’s SPF include that carries the mailbox platform’s own include inside it, and 4,605,632 of those are GoDaddy records on Microsoft 365 mailboxes. Another 1,090,344 receive mail through a filtering gateway such as Proofpoint or Mimecast, and 383,990 are one company listed under two names.
The group that matters is smaller: 749,896 domains, 1.2% of those with both labels, receive mail at Google Workspace or Microsoft 365 and publish an SPF record that names neither the platform nor a host whose include carries it. 701,358 of them are on Google Workspace, 5.1% of its mailboxes in the base. Mail those mailboxes send can’t pass SPF unless the record authorises the platform some other way, and in a sample checked live most records didn’t.
Horizontal bars splitting the 7,852,831 domains whose SPF and MX labels differ into six groups: a host's include that carries the mailbox platform 4,792,398, a filtering gateway 1,090,344, one company under two names 383,990, mailbox platform left out of SPF 749,896, Google record on a Microsoft 365 mailbox 105,673, other pairs 730,530.
Figure 1. What the mismatches are. The blue bar is the group whose SPF record leaves the mailbox platform out.
How the two labels were read
The census reads each domain’s TXT (Text) and MX records. For this page each domain got two labels: the vendor its SPF record names, and the vendor running its primary MX host, the one with the lowest preference number. A label is the first vendor in a fixed list whose include or host name appears in the record. The list has 59 match strings for SPF, such as _spf.google.com and secureserver.net, and 39 for MX hosts.
85,691,526 SPF records and 84,614,588 primary MX hosts got a label. 62,799,771 domains got both, and that is the base for every share on this page. 45,311,973 of them sit under gTLDs and 17,478,898 under ccTLDs; the 8,900 under internationalised endings are in the totals and aren’t split out.
Each SPF record gets one label, even when it includes several vendors. The list is checked in order, Google first and Microsoft second, so a record that includes Google and Mailgun counts as Google. That order is what lets this page say a record leaves a platform out: a record labelled with any vendor except Google doesn’t contain Google’s include, and one labelled with anything except Google or Microsoft doesn’t contain Microsoft’s. It also means a record labelled Google or Microsoft may name other vendors the label doesn’t show.
Where the mail lands and who may send it
Each row of the matrix is a mailbox vendor, and each cell is the share of that vendor’s domains whose SPF record carries the label in the column. On the diagonal the two agree. At the large hosting companies they agree for nearly all domains: 99.8% at Namecheap, 99.7% at Hostinger and 99.6% at IONOS. Google Workspace agrees for 93.7%. Microsoft 365 agrees for 67.6%, the lowest of the ten, because 31.3% of its mailboxes carry GoDaddy’s SPF record.
Heatmap of ten mailbox vendors (rows, by MX) against the same ten vendors named by SPF (columns) plus an other column; each row adds to 100%. Diagonal shares: Google Workspace 93.7%, Microsoft 365 67.6%, Namecheap 99.8%, IONOS 99.6%, Hostinger 99.7%, GoDaddy 97.7%, Cloudflare Email Routing 97.2%, OVH 99.0%, Zoho Mail 89.4%, Titan 98.2%. The largest cell off the diagonal is Microsoft 365 mailboxes with a GoDaddy record, 31.3%.
Figure 2. The matrix. Rows are where mail arrives, columns are what SPF names, and each row adds to 100%. The outlined cells are the diagonal.
The same ten vendors, and Proofpoint, read from both sides. Each share is of that vendor’s own domains in the base.
| Vendor | Domains with MX here | SPF names the same vendor | Domains with SPF here | MX names the same vendor |
|---|---|---|---|---|
| Google Workspace | 13,861,980 | 93.7% | 13,296,974 | 97.6% |
| Microsoft 365 | 14,727,702 | 67.6% | 10,304,595 | 96.6% |
| Namecheap | 8,077,691 | 99.8% | 8,116,664 | 99.3% |
| IONOS | 7,548,648 | 99.6% | 7,528,559 | 99.8% |
| Hostinger | 4,705,150 | 99.7% | 4,805,784 | 97.7% |
| GoDaddy | 1,661,403 | 97.7% | 7,141,761 | 22.7% |
| Cloudflare Email Routing | 2,968,917 | 97.2% | 2,906,937 | 99.3% |
| OVH | 2,455,365 | 99.0% | 2,479,571 | 98.0% |
| Zoho Mail | 1,466,059 | 89.4% | 1,333,390 | 98.3% |
| Titan (Flock) | 809,082 | 98.2% | 811,829 | 97.9% |
| Proofpoint | 1,017,842 | 2.4% | 25,414 | 95.5% |
Read from the SPF side, GoDaddy’s label sits on a GoDaddy mailbox for 22.7% of its 7,141,761 domains. Proofpoint’s MX hosts carry a Proofpoint SPF label for 2.4% of theirs. The next section explains both.
Mismatches that work as built
Host records that carry the mailbox platform
GoDaddy resells Microsoft 365. In the three country-code endings re-read in full for this page (.ac, .ie and .nz), 7,650 of the 8,094 domains with a GoDaddy record and a Microsoft 365 mailbox publish exactly v=spf1 include:secureserver.net -all. That include names one more, and that one names spf.protection.outlook.com, Microsoft’s own. So that record authorises Microsoft 365 through GoDaddy’s include, although its label says GoDaddy. The pair covers 4,605,632 domains.
HostGator’s include, websitewelcome.com, carries more. It includes both _spf.google.com and spf.protection.outlook.com, and 177,709 Google Workspace mailboxes and 9,057 Microsoft 365 mailboxes carry a HostGator record. The two includes apply whether or not a domain uses either service: 24,978 of the 211,744 domains in the base whose record carries HostGator’s label receive their mail somewhere else.
We looked up these include records a day after the census captured the domains’ own records. Most domains name the standard include. Across the census, secureserver.net itself appears in 7,610,053 domains’ records. Every other include name containing it, misspellings included, appears 677,875 times, and the most common of those, spf.em.secureserver.net (655,481), doesn’t carry Microsoft’s. websitewelcome.com itself appears 3,142,065 times, and other names containing it 7,299.
On the same day we took fixed samples of each group from those three endings, fetched each domain’s SPF record, kept the records unchanged since the census and evaluated them for one real sending address of the mailbox platform: 209.85.220.41 for Google Workspace and 40.107.22.50 for Microsoft 365. 200 of 200 GoDaddy records on Microsoft 365 mailboxes passed, and so did 184 of 189 HostGator records.
A carried include can still fail. Bluehost’s include reaches Microsoft’s only at its ninth DNS (Domain Name System) lookup, and SPF allows ten per check. A record that spends lookups first, such as v=spf1 a mx ptr include:bluehost.com ?all, runs out before it gets there and returns a permanent error. This page counts the 781 domains with a Bluehost record and a Microsoft 365 mailbox among the mailboxes SPF leaves out; the lookup limit explains the arithmetic.
Gateways and two names
Proofpoint and Mimecast filter mail before it reaches the mailbox: their MX hosts take mail in and pass it on to the mailbox platform. Of the 1,090,344 gateway domains whose labels differ, 1,057,708 (97.0%) carry a GoDaddy or Microsoft 365 record, which authorises Microsoft 365 to send, directly or through GoDaddy’s standard include. A gateway that also relays outgoing mail needs its own include as well, and the label can’t show whether a record has one.
Two more pairs come from the list itself. Tencent’s SPF include and its MX hosts appear under different names in the two lists, on 372,357 domains, and so do Alibaba’s, on 11,633.
The mailbox SPF leaves out
749,896 domains receive mail at Google Workspace or Microsoft 365 and publish an SPF record that names neither the platform nor a host whose include carries it: 701,358 Google Workspace mailboxes, 5.1% of those in the base, and 48,538 Microsoft 365 mailboxes, 0.3%.
Two stacked bars, one for Google Workspace mailboxes and one for Microsoft 365 mailboxes, split by what their SPF record names. Google Workspace: the platform itself 93.7%, a host's include that carries it 1.3%, left out 5.1%. Microsoft 365: the platform itself 67.6%, a host's include that carries it 31.3%, a Google record that may also name Microsoft 0.7%, left out 0.3%.
Figure 3. What SPF names for the two largest mailbox platforms. Blue is the share left out.
Most of these records name a web host instead. 52.6% carry a host or registrar label, led by Hostinger’s include on 88,561 domains, GoDaddy’s on 83,887 (its include carries Microsoft’s, which doesn’t help a Google mailbox) and OVH’s on 41,750.
26.9% name a bulk or transactional mail service such as Mailgun, MailerLite or Mailchimp. Those services send newsletters and receipts, while the mail people write leaves from the mailbox. 9.2% name a relay or forwarding service, and 11.2% another mailbox provider, including 34,283 Google Workspace mailboxes whose record names Microsoft 365.
When someone at one of these domains sends an email, it leaves from the mailbox platform’s servers. The receiving server looks up the domain’s SPF record, doesn’t find those servers in it, and gets softfail, fail or neutral depending on how the record ends, or a permanent error if the record breaks SPF’s own rules. DMARC (Domain-based Message Authentication, Reporting and Conformance) can still pass on a DKIM (DomainKeys Identified Mail) signature for the domain itself. Google Workspace signs with a gappssmtp.com key until an admin turns on DKIM for the domain, and that signature doesn’t count for DMARC.
Moving a mailbox and leaving the old SPF record in place is one way to arrive here. The census can’t tell how any domain got there, and a domain may send no mail from its mailbox at all.
The live sample agrees with the labels. Of 193 Google Workspace records unchanged since the census, 185 didn’t pass SPF for Google’s sending address, and the 8 that did authorise Google some other way, such as raw address ranges or an older Google include. The Microsoft group is less clear: 86 of 103 didn’t pass, and 17 reached Microsoft’s address through ranges or an organisation’s own include.
More of the Microsoft group had changed, too: 97 of the 200 sampled records differed from the census by the time of the check, against 1 of 200 records already matched to Microsoft 365.
So treat 701,358 as an upper limit. Some records authorise Google in a form the label list doesn’t look for. Across the census, 59,106 domains name aspmx.googlemail.com, which redirects to Google’s include, 13,937 name google.com, and up to 7,540 name Google’s netblock records directly; the census doesn’t say how many of those fall in this group. On the Microsoft side, 7 other Microsoft includes that carry its sending range appear 16,809 times across the census.
Figure 4 puts the two groups on one scale. Gateway domains name the platform behind the gateway, or GoDaddy’s record that carries it; the left-out domains name hosts and mail services.
Horizontal bars on one scale in two groups. Mailbox left out of SPF, by what the record names: Hostinger 88,561, GoDaddy 83,887, Mailgun 55,509, MailerLite 47,586, MailChannels 46,895, Mailchimp / Mandrill 42,987, OVH 41,750, Microsoft 365 34,283, all others 308,438. Filtering gateway, by what the record names: GoDaddy 801,538, Microsoft 365 256,170, Google Workspace 15,459, all others 17,177.
Figure 4. The left-out group (blue) and the gateway group (grey) on one scale, by the vendor the SPF record names.
The 25 largest pairs
Together the 25 largest pairs cover 7,009,398 domains, 89.3% of the mismatch. 12 of them leave the mailbox platform out, 6 work as built, and 7 can’t be settled from one label.
| # | SPF names | Primary MX at | Domains | Share of mismatch | Group |
|---|---|---|---|---|---|
| 1 | GoDaddy | Microsoft 365 | 4,605,632 | 58.6% | host’s include carries it |
| 2 | GoDaddy | Proofpoint | 801,107 | 10.2% | filtering gateway |
| 3 | Tencent QQ | Tencent Exmail | 372,357 | 4.7% | one company, two names |
| 4 | HostGator | Google Workspace | 177,709 | 2.3% | host’s include carries it |
| 5 | Microsoft 365 | Proofpoint | 173,826 | 2.2% | filtering gateway |
| 6 | Google Workspace | Microsoft 365 | 105,673 | 1.3% | Google record, Microsoft mailbox |
| 7 | Hostinger | Google Workspace | 84,149 | 1.1% | mailbox left out of SPF |
| 8 | GoDaddy | Google Workspace | 83,887 | 1.1% | mailbox left out of SPF |
| 9 | Microsoft 365 | Mimecast | 82,344 | 1.0% | filtering gateway |
| 10 | Google Workspace | Cloudflare Email Routing | 71,231 | 0.9% | other pair |
| 11 | Mailgun | Google Workspace | 47,479 | 0.6% | mailbox left out of SPF |
| 12 | MailerLite | Google Workspace | 45,615 | 0.6% | mailbox left out of SPF |
| 13 | MailChannels | Google Workspace | 42,952 | 0.5% | mailbox left out of SPF |
| 14 | OVH | Google Workspace | 39,846 | 0.5% | mailbox left out of SPF |
| 15 | Mailchimp / Mandrill | Google Workspace | 38,079 | 0.5% | mailbox left out of SPF |
| 16 | Microsoft 365 | Google Workspace | 34,283 | 0.4% | mailbox left out of SPF |
| 17 | SendGrid | Rackspace | 33,355 | 0.4% | other pair |
| 18 | Namecheap | Zoho Mail | 28,015 | 0.4% | other pair |
| 19 | Web Hosting Inc | Google Workspace | 21,979 | 0.3% | mailbox left out of SPF |
| 20 | Bluehost | Google Workspace | 21,925 | 0.3% | mailbox left out of SPF |
| 21 | WordPress.com / Automattic | Google Workspace | 20,722 | 0.3% | mailbox left out of SPF |
| 22 | Google Workspace | Zoho Mail | 19,813 | 0.3% | other pair |
| 23 | Google Workspace | IONOS | 19,171 | 0.2% | other pair |
| 24 | Beget | Yandex | 19,157 | 0.2% | other pair |
| 25 | SendGrid | Google Workspace | 19,092 | 0.2% | mailbox left out of SPF |
Horizontal bars for the 25 largest mismatched pairs, each labelled with the vendor the SPF record names and the vendor at the primary MX, coloured by group. The largest is GoDaddy with Microsoft 365, 4,605,632 domains; the next are GoDaddy with Proofpoint, 801,107, and Tencent QQ with Tencent Exmail, 372,357.
Figure 5. The 25 largest mismatched pairs. Blue pairs leave the mailbox platform out, mid grey pairs work as built, and light grey pairs can’t be settled from one label.
105,673 Microsoft 365 mailboxes carry a record labelled Google. The label shows the record includes Google, and it can’t show whether the record includes Microsoft too. In the sample most did: 186 of 193 unchanged records passed for Microsoft’s address.
The remaining 730,530 mismatched domains pair hosts, forwarders and smaller mailbox providers. For those, the mailbox vendor’s include may come later in the list than the vendor the label names, so one label can’t say whether the record carries it. The largest of these pairs is Google Workspace records on Cloudflare Email Routing mailboxes, with 71,231 domains.
By ending
Mismatches are more common under gTLDs, 13.8%, than under ccTLDs, 9.0%, and most of the difference is GoDaddy’s record on Microsoft 365 mailboxes: 8.3% of the gTLD base against 4.8% of the ccTLD base. The left-out group is a similar size in both, 1.1% and 1.3%.
Each row is a share of that ending’s own domains with both sides labelled.
| Ending | Both labelled | Labels differ | Work as built | Mailbox left out | Can’t tell |
|---|---|---|---|---|---|
| All gTLDs | 45,311,973 | 13.8% | 11.4% | 1.1% | 1.3% |
| All ccTLDs | 17,478,898 | 9.0% | 6.2% | 1.3% | 1.5% |
| .com | 33,721,173 | 16.0% | 13.4% | 1.3% | 1.3% |
| .de | 2,537,964 | 5.3% | 4.6% | 0.3% | 0.5% |
| .org | 2,526,237 | 11.9% | 9.4% | 1.5% | 1.1% |
| .uk | 2,153,556 | 13.3% | 11.2% | 0.9% | 1.2% |
| .net | 1,961,408 | 12.0% | 9.9% | 0.8% | 1.2% |
| .fr | 1,626,514 | 2.7% | 0.4% | 1.0% | 1.2% |
| .br | 978,235 | 4.8% | 1.5% | 1.9% | 1.4% |
| .info | 916,892 | 2.9% | 2.3% | 0.2% | 0.4% |
| .au | 864,661 | 21.6% | 18.7% | 1.6% | 1.2% |
| .co | 738,319 | 11.6% | 8.9% | 1.6% | 1.1% |
| .ca | 688,968 | 24.9% | 22.0% | 1.6% | 1.3% |
| .in | 657,539 | 5.4% | 2.5% | 2.0% | 0.9% |
| .nl | 578,133 | 4.7% | 1.6% | 1.5% | 1.6% |
| .online | 501,477 | 2.5% | 1.5% | 0.2% | 0.7% |
| .shop | 403,661 | 3.9% | 3.2% | 0.2% | 0.5% |
Among the 15 endings with the most labelled domains, .ca, .au and .com have the highest mismatch rates, and in each of the three GoDaddy’s record on a Microsoft 365 mailbox makes up at least 60.9% of the mismatch. The left-out share stays between 0.2% and 2.0% in all fifteen.
Stacked horizontal bars for all gTLDs, all ccTLDs and the 15 endings with the most labelled domains, each showing the share whose labels differ, split into work as built, mailbox left out and can't tell. The longest bar is .ca at 24.9%.
Figure 6. Labels that differ, by ending, as a share of each ending’s labelled domains. Blue is the share whose SPF record leaves the mailbox platform out.
What the census can’t see
- The census reads records and doesn’t send mail, so it can’t tell whether any message was delivered, filtered or rejected. A DKIM signature for the domain can carry DMARC when SPF doesn’t pass.
- Each SPF record carries one label, chosen in a fixed order, so a record that includes several vendors shows as the first. The left-out group rests on that order, and the Google records on Microsoft 365 mailboxes can’t be read from it.
- Only the primary MX host is labelled. When two hosts share the lowest preference, or a domain has two scan rows, the pick between them is arbitrary, so running the same query twice on the same data moves the counts by a few domains. The pass’s two output files differ by 0 domains for that reason.
- .com ran in 24 parts, and the lake holds one row per domain, so no .com domain is counted twice.
- Misspelt includes count under the vendor they name. Across the census, 9,262 domains name
spf.google.comwithout the leading underscore, which doesn’t exist, and 1,177 name_spf.protection.outlook.com, which doesn’t either. - The include records and the sample were checked a day after the census. A provider can change its include at any time.
- A domain with more than one SPF record is labelled from one of them, although SPF itself treats two records as an error.
See your own
The free scan reads your SPF record live. If your mailbox is at Google Workspace or Microsoft 365, the Google Workspace SPF values and the Microsoft 365 SPF values give the include to add, and SPF after switching provider covers what to take out.
Figures from the defaults.exposed census, data as of 2 November 2026. Census numbers move every month; the current values are on the census data page.