Self-hosted email in top domains halves over decade as two providers now handle 38.6% of inbound mail

The decline of self-hosted email reflects a broader shift toward managed services, driven by operational complexity and deliverability challenges. Running a mail server in 2026 requires navigating reputation systems, spam filters, and authentication protocols tuned for major providers. The data shows this is no longer a niche concern: over a decade, the share of top domains self-hosting email has halved, with no signs of reversal. The trend mirrors DNS and CDN centralization but carries unique risks, as email lacks fallback mechanisms for failed delivery. Operators who persist with self-hosting must contend with a landscape where their infrastructure is treated as an outlier by default.

Consolidation around Google Workspace and Microsoft 365 creates systemic fragility. The two providers now handle inbound mail for 38.6% of measured domains, meaning a single outage or policy change can ripple across the ecosystem. Unlike CDNs, where redundancy and failover are built into the model, email offers no graceful degradation, rejected messages are lost. The data underscores how resilience discussions in the RIPE community apply equally to email, even if the problem is less visible. Smaller providers and self-hosted setups inherit the deliverability problems of this centralization, as reputation systems favor the dominant players.

DMARC adoption has plateaued at a superficial level, with most domains publishing policies that enforce nothing. Only 46.9% of domains with DMARC records use quarantine or reject policies, and the share is declining. The most common DMARC record in the dataset is a bare `v=DMARC1; p=none;`, often copy-pasted to satisfy compliance checklists without follow-through. This creates a false sense of security: domains believe they are protected, but their policies generate no actionable data and provide no actual enforcement. The stagnation suggests that bulk-sender requirements from Google and Yahoo in 2024 drove adoption but not meaningful implementation.

A significant portion of email infrastructure remains unclassified, revealing a long tail of bespoke or obscure setups. Dictionary-based classification attributes 81.5% of SPF includes and most MX records, but the remainder includes tens of thousands of unique hostnames and one-off SPF targets. Some of these are misconfigurations (e.g., `localhost` or `~` as MX records), but most represent legitimate, if niche, infrastructure. This tail highlights the limits of automated measurement and the diversity of email setups that persist despite consolidation. For engineers, it underscores that email’s complexity is not disappearing, it’s just becoming less visible.