This is an AI-generated report. The company list, domain matching, DNS lookups and analysis were produced by an AI agent (Claude). Findings are drawn from live DNS records and are believed accurate as of 3 August 2026, but domain matching is imperfect and the numbers have not been independently reviewed — verify anything you intend to rely on.
MX record survey · August 2026
Live MX and SPF lookups against the primary domain of 1,150 companies — the top 1,000 of the Forbes Global 2000 plus 150 AI-native and private cloud firms — broken down by sector.
Microsoft 365 serves nearly half of these companies outright. Self-hosted mail is far from dead: roughly one in five still runs its own inbound infrastructure, concentrated in Chinese state-owned groups, Japanese conglomerates and the largest US banks.
Split the same population by vintage and the pattern inverts. Established global corporates run on Microsoft; the AI and private-cloud generation runs on Google Workspace by a factor of roughly nineteen to one.
Sorted by number of companies. Hover any segment for exact counts. Oil & gas, healthcare and hospitality are the most heavily Microsoft-weighted; banking carries the most self-hosted mail; the two technology tiers built since 2015 are the only ones where Google leads.
A gateway in front of the mailbox rewrites MX, so the platform behind it is invisible to a plain MX lookup. Recursively expanding each domain's SPF chain and checking its autodiscover record unmasked most of them; the rest are counted separately rather than guessed at.
Counted wherever a gateway fronts the MX, whether or not the backend was identified.
Countries with at least 12 companies in the sample. The self-hosted share tracks state ownership and data-residency rules more than company size.
All 1,150 rows, with the domain checked and the first MX host returned. Click a column heading to sort.
| Rank | Company | Sector | Country | Domain | Mail platform | First MX host |
|---|
jpmorganchase.com publishes no MX; mail runs on jpmorgan.com. Where the site domain had no MX, sibling domains were probed and confirmed.<tenant>.mx.microsoft.include: chain was expanded recursively and its autodiscover CNAME checked.