One mail server and no spare? MX redundancy across mail domains
In the November 2026 census, 164,013,725 graded domains publish at least one MX (Mail Exchange) record that names a usable mail host, and 80,573,166 of them publish exactly one: 44.7% of mail domains under gTLDs and 56.9% under ccTLDs. A single record can still lead to many servers, because one host name can resolve to several machines. Microsoft 365 gives each customer domain one MX name, and 97.9% of the domains whose mail it receives publish that record and no other. Google’s current setup is also one name, smtp.google.com. When we looked them up a day after the census, smtp.google.com returned 5 IPv4 addresses and a Microsoft 365 MX name returned 4.
So how many MX records should a domain have? With a hosted service, publish the records the provider gives you, which for Microsoft 365 and Google’s current setup is one name. A second record adds a spare only if it names a host that can take the mail when the first can’t.
The single records most likely to mean a single machine are the 30,951,691 that name the domain itself or a host under it, such as mail.example.com. They make up 38.4% of the one-record domains. For 24,213,565 one-record domains, the address the census got for the mail host is also an address of the website on the bare domain, so mail and web arrive at the same place.
Horizontal bar chart of the 80,573,166 domains that publish exactly one MX record, by what that record names: Microsoft 365 18.5%, Google Workspace 9.4%, other named mail providers 1.9%, a name under the domain itself 38.4%, a host at another operator 31.8%, an IP address 0.05%.
Figure 1. What a single MX record names. The blue bar is the group most likely to be one server: a host named under the domain itself.
How the count was taken
The census reads MX records only for domains it grades. It doesn’t query dead names, and it skips the query when its pre-scan lookup found no MX, so everything here is about graded domains where the census captured MX records. There are 182,016,000 of them.
That count includes domains that take no mail at all. RFC 7505 lets a domain say so with a single record, MX 0 ., which names no host. 16,227,236 domains publish only records of that kind: 16,124,309 in the exact RFC 7505 (Request for Comments) form and 102,927 with a preference other than 0 or more than one such record. Another 1,775,039 point their MX records only at localhost or at names under .invalid, and 1,754,773 of those use localhost. Neither can receive mail from anyone: RFC 6761 has localhost always mean the sender’s own machine, and names under .invalid never resolve.
Both groups are left out, because counting them would put domains with no mail server into the one-record group. What remains is the base for every share on this page: 164,013,725 domains with at least one MX record naming a usable host. Records of either kind that sit beside usable ones are dropped too, and the usable ones counted. 5,781 domains publish a Null MX beside other records, which RFC 7505 forbids, and 58,779 list localhost or an .invalid name beside a usable host.
The main shares are also given for gTLDs and ccTLDs separately, because .com alone holds 46.8% of all mail domains. 104,227,405 mail domains sit under gTLDs and 59,564,266 under ccTLDs. The 222,054 mail domains under internationalised TLDs (Top-Level Domains) are in the totals and aren’t split out.
One record, two, or five
Each column is a share of that column’s mail domains.
| MX records | All TLDs | gTLDs | ccTLDs |
|---|---|---|---|
| 1 | 49.1% | 44.7% | 56.9% |
| 2 | 27.4% | 28.1% | 26.1% |
| 3 | 7.7% | 8.2% | 6.9% |
| 4 | 1.7% | 1.0% | 2.9% |
| 5 | 13.2% | 17.1% | 6.5% |
| 6 or more | 0.8% | 0.9% | 0.7% |
| Mail domains | 164,013,725 | 104,227,405 | 59,564,266 |
One record is the most common count. The bump at five comes almost entirely from two providers’ standard setups: 59.5% of the domains whose primary MX is at Google Workspace publish exactly five records, and so do 98.6% of those at Namecheap.
Paired horizontal bars for 1, 2, 3, 4, 5, and 6 or more MX records. One record: gTLDs 44.7%, ccTLDs 56.9%. Two: 28.1% and 26.1%. Three: 8.2% and 6.9%. Four: 1.0% and 2.9%. Five: 17.1% and 6.5%. Six or more: 0.9% and 0.7%.
Figure 2. How many MX records a mail domain publishes, gTLDs in blue and ccTLDs in orange.
The ten TLDs with the most mail domains, each row a share of that TLD’s own mail domains:
| TLD | Mail domains | One MX record | MX hosts at two or more operators |
|---|---|---|---|
| .com | 76,778,829 | 45.2% | 1.0% |
| .de | 9,671,197 | 59.9% | 3.9% |
| .org | 6,054,317 | 42.7% | 1.0% |
| .net | 5,787,420 | 46.0% | 1.1% |
| .uk | 4,954,780 | 45.6% | 1.7% |
| .nl | 3,018,846 | 67.1% | 3.2% |
| .ru | 2,939,526 | 55.0% | 0.8% |
| .fr | 2,891,349 | 32.1% | 3.3% |
| .br | 2,525,988 | 46.3% | 1.0% |
| .it | 2,299,141 | 78.2% | 1.3% |
What a second record is for
RFC 5321, section 5.1, tells a sending server to try MX hosts in order of preference, lowest number first. Hosts that share a preference are tried in random order, to spread the load. A host with a higher number is a backup, tried when the lower ones don’t answer. Section 4.5.4.1 also has the sender keep retrying, and says the give-up time generally needs to be at least four to five days. For a sender that follows it, a primary that is down for an hour delays mail. A backup that answers in the meantime accepts it sooner.
83,440,559 domains publish two or more records. 20.0% of them put every record at one preference, and 80.0% use a primary with one or more backups. Most of those backups sit with the same operator as the primary: in 97.1% of primary-and-backup layouts, every backup belongs to the primary’s operator. A backup at the same operator helps when one of its servers fails. When the operator itself is unreachable, only a host run by someone else can take the mail. 1,924,346 domains have a backup of that kind, 1.2% of all mail domains. It’s more common under ccTLDs, where 5.6% of primary-and-backup layouts have a backup elsewhere, against 1.8% under gTLDs.
That kind of backup has a cost. A backup that accepts mail without knowing which addresses exist on the primary has to bounce the unknown ones later, and those bounces go to whatever sender address the message carried, forged or not.
“Operator” here means the brand in the host’s domain name, with Google’s and Microsoft’s hosts grouped under their mail services. A company that runs MX hosts under two different brand names counts as two operators, and a record naming an IP (Internet Protocol) address is never counted as a backup. 808,642 domains list two or more records that all name the same host.
Three stacked bars, for all TLDs, gTLDs and ccTLDs, splitting the domains with two or more MX records by arrangement. All TLDs: one preference 20.0%, backup at the same operator 77.7%, backup at another operator 2.3%.
Figure 3. How the second and later records are arranged, as shares of the domains with two or more MX records.
MX record count by provider
97.9% of domains with Microsoft 365 as their primary MX publish one record. Google Workspace domains split between the five-host setup (59.5%) and the single smtp.google.com record (33.5%). Domains whose primary MX is a host under their own name publish one record in 93.7% of cases. At the large hosting companies one count dominates. GoDaddy, IONOS and Hostinger put almost every domain on two records (99.1%, 99.7% and 99.3%), and Cloudflare Email Routing uses three or more for 99.9%.
Stacked bars for the nine largest mail providers by primary MX record, then domains whose primary record is a name under the domain itself, then all other hosts, each split into one, two, and three or more MX records. One-record shares: Microsoft 365 97.9%, Google Workspace 33.5%, name under the domain itself 93.7%, other hosts 55.5%.
Figure 4. MX record count by the provider of the primary MX record. The column on the right is the share with exactly one record.
272,368 domains also carry Google’s domain-verification MX record, a host under mx-verification.google.com, beside their mail records. It counts as a record here, and as Google’s.
Records that can’t work as written
RFC 5321 says the value in an MX record must be a domain name that returns an address when looked up. 44,521 mail domains have at least one MX record set to an IP address, and for 37,729 of them every record is an IP address. Once a domain publishes MX records, a sender following the standard won’t fall back to the domain’s own address, so for those 37,729 domains a standard sender finds no usable host, and RFC 5321 tells it to report an error.
11,214,298 domains name the domain itself as the primary MX host, such as example.com for example.com. That’s allowed, and mail goes to the addresses of the bare domain.
For 4,227,365 domains, the census asked for the IPv4 address of the host with the lowest preference number and got none. Some of those hosts have only an IPv6 address and some lookups failed at scan time, so the count is an upper limit on primary hosts that don’t exist.
What the census can’t see
- The census keeps the first IPv4 address it gets for the primary host and no more, so it can’t tell a single server from a pool behind one name.
- A backup host may queue mail for the domain, refuse it, or no longer know the domain at all. The records alone don’t say which.
- The census asks for MX only when its pre-scan lookup found some. Of the 150,108,855 graded domains with no MX captured, 263,770 had an MX query that failed.
- A correct record can still point at a server that refuses connections, and the census doesn’t send mail to find out.
See your own
The free scan reads a domain’s MX records live, with the preference of each. The MX guide covers what to change when a record points somewhere it shouldn’t.
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.