- Live disposable domains
- 174,013
- Mail operators
- 8,522
- Routed via Cloudflare
- 12.2%
- No MX record, still routable
- 20.0%
From domains to mail operators
A disposable email service can own hundreds of domains, but every message still has to arrive at a mail server. We grouped the 174,013 domains in Disban's inventory that could receive mail on 8 October 2026 by the organisation that runs their mail servers. They are spread across 8,522 operators, and the ten largest handle 28.3% of the live domains. The rest is a long tail of small and self-hosted setups.
The largest operator is a free forwarding service
21,229 live disposable domains (12.2%) receive mail through Cloudflare Email Routing, a free service that forwards mail for any domain using Cloudflare DNS. That is far more than any temporary-email company runs itself. The same service forwards mail for a very large number of legitimate businesses and personal sites, so the mail server alone says nothing about whether a domain is disposable.
Some operators exist only for temporary email
Behind Cloudflare, the next largest operators are dedicated to temporary inboxes: mimimail.me receives mail for 5,536 live domains, pigeonprotocol.com for 3,457, tempmail.tw for 3,415 and spymail.one for 2,785. When a service rotates to a brand-new domain, that domain usually points at the same mail servers. Recognising these dedicated servers lets a checker classify a new domain before it appears on any list.
Parking and big providers show up too
3,370 live domains route to above.com, a domain-parking service, and 1,778 use Google's mail servers. Neither is evidence of disposable use on its own: parked domains rarely belong to an active inbox service, and Google hosts mail for millions of organisations. Rules that block a mail provider outright would reject large numbers of legitimate customers.
One in five live domains has no MX record
34,747 of the live domains (20.0%) publish no MX record at all. They still receive mail because SMTP falls back to the domain's address record. A check that only looks for MX records would wrongly report these domains as unable to receive mail.
What this means for detection
Blocking by mail server catches rotating domains only when the server is dedicated to disposable email, and it causes false positives everywhere else. Blocking by domain ending does the same at a larger scale. Reliable detection combines exact domain evidence, mail servers that are known to be dedicated, and protection for shared providers such as Cloudflare, Google and parking services. That is the approach Disban's methodology describes, and it is why a shared platform never turns one tenant's behaviour into a verdict for everyone else.
Source for provider behavior: Disban methodology. Product-policy guidance is Disban's interpretation.