"Nobody self-hosts email any more" is one of those claims that is directionally true and factually wrong. Directionally: our nightly DNS scan of the Tranco top-1M domains shows self-hosted mail falling from 42.76% of mail-receiving domains in 2016 to 30.18% in 2022 and 22.53% as of the 2026-07-05 snapshot. Factually: 22.53% is still 147,712 domains — universities, governments, hosting companies, privacy-conscious businesses, and a great many organisations that simply never saw a reason to move.
So the real question is not "is self-hosting dead?" It is: which kind of organisation should still be in that 22.53% — and would yours be one of them?
The part nobody warns you about: receiving is easy, sending is a career
A weekend of work gets you a mail server that receives perfectly. Postfix or an all-in-one stack, an MX record, TLS — done. The decade-long difficulty gradient is entirely on the outbound side, because deliverability is not a configuration, it is a reputation:
- IP reputation starts at zero (or below). Large mailbox providers score your sending IP's history. A fresh IP — especially in a cloud provider's range with a spammy past — gets throttled or junked regardless of how correct your configuration is.
- Reverse DNS is table stakes. Your sending IP needs a PTR record that resolves to your mail server's hostname, and that hostname must resolve back to the IP. Many VPS providers make setting the PTR awkward; some large recipients refuse mail without it.
- You own the full authentication stack. SPF, DKIM signing, and a DMARC policy are yours to publish, rotate, and monitor — forever. With 47.16% of DMARC-publishing domains now enforcing their policies, mistakes are increasingly punished with rejection rather than a spam-folder warning.
- Reputation needs volume and time. Providers build trust from consistent, complained-about-rarely sending over weeks and months. A low-volume personal server never accumulates enough signal to be confidently trusted — the paradox of small self-hosters.
The state of the self-hosted fleet
The dataset also shows how the remaining fleet is maintained — and it tempers romanticism. Among self-hosted MX hosts we sampled for IPv6, only about 4.96% (1,570 of 31,666 checked) publish an AAAA record, versus roughly 90% of Google's MX hosts. The strongest self-hosted TLD, .org, manages just 8.28%. Email is IPv4's last fortress, and the self-hosted segment is its most conservative garrison. If your mental image of self-hosting is a lovingly modernised stack, the data says the median reality is closer to "it still works, do not touch it."
When self-hosting is the right call
- Data control as a requirement, not a preference. Legal privilege, medical data, journalism sources, or contractual terms that forbid third-party processing of message content.
- Jurisdiction. You need mail stored under a specific legal regime, and no acceptable hosted provider operates there.
- You already have the muscle. An ops team that runs servers professionally anyway, monitoring included — the marginal cost of one more well-run service is genuinely low.
- Institutional scale. Universities and ISPs with tens of thousands of mailboxes have real economics on their side, plus decades of accumulated IP reputation.
When it is not
- To save the subscription fee. The honest accounting includes your hours: patching, deliverability firefighting, spam-filter tuning, backup testing. At any realistic valuation of founder time, the suite is cheaper.
- For outbound-heavy workloads. If email is how you win customers, you are choosing to fight reputation battles that Google and Microsoft customers never see. Ironically, the decline of self-hosting has made life easier for senders — predictable filters replaced sysadmin whims — but as the operator you are on the other side of that trade.
- As a learning project on a production domain. Learn on a throwaway domain. Reputation damage on your real domain outlives the experiment.
The minimum honest checklist
If you proceed, this is the floor, not the ceiling:
- Static IP with a clean history, PTR record set, forward-confirmed reverse DNS.
- SPF with
-allor~all, DKIM signing with key rotation, DMARC starting atp=nonewith reports monitored, then ratcheted up. - TLS on SMTP in both directions; modern ciphers.
- Outbound volume ramped slowly over weeks, never in bursts.
- Blocklist and reputation monitoring with alerting — you find out from your monitoring, not from a customer.
- A regular placement test against real mailboxes at Gmail, Microsoft 365, Yahoo and the rest — self-hosted senders have no provider dashboard to warn them, so external verification is the only ground truth. Our daily email infrastructure report also shows exactly which filters guard your recipients.
Self-hosting in 2026 is a legitimate choice made for sovereignty and paid for in reputation work. If the sovereignty argument does not apply to you, the 147,712 domains still doing it are not evidence that you should — they are mostly organisations for whom it does.