- Listed domains that no longer exist
- 52.1%
- Other domains on Yopmail's servers
- 400+
- Mail operators behind live domains
- 8,522
What is the most reliable way to detect a disposable email?
The most reliable way is to check the email's domain at signup against several kinds of evidence at once: known disposable domains, the mail servers the domain uses, and the operators behind those servers. Any single method misses something. A list misses new domains, and a mail-server check alone cannot tell a disposable inbox from a real company's mailbox.
Method 1: a disposable domain blocklist
A blocklist is a file of domains known to belong to disposable services. It is free, fast and easy to add. Its weakness is age: lists keep every domain they have ever seen. In our October 2026 lookups, 52.1% of 429,532 known disposable domains no longer existed, so a large part of any list is history. Lists also miss domains registered after the last update, and some public lists mix in free providers such as Gmail, which blocks real users.
Method 2: check whether the domain can receive mail
Looking up a domain's mail servers (its MX records) tells you whether mail can be delivered there right now. This catches typos and dead domains, such as gmial.com or a lapsed disposable domain. It does not catch working disposable services, because they receive mail by design. Use it as a separate check alongside the category, not instead of it.
Method 3: match the mail servers and the operator behind them
Disposable services register new domains constantly but tend to run them on mail servers they already operate. In our data, more than 400 separately registered domains route their mail to Yopmail's servers and more than 300 to Mailinator's. Recognising the operator lets you flag a new domain on its first signup, before any list includes it. The care needed: shared hosting and large mail platforms are used by legitimate companies too, so a shared server alone is not proof.
Method 4: use a detection API
An API combines the methods above, keeps the data current and returns a decision in one request. The trade-offs are a network call during signup and a dependency on another service, so set a short timeout and decide in advance what happens if the check is unavailable. A good API tells you why it reached a result, not only true or false, so you can handle edge cases such as privacy aliases.
Method 5: behaviour signals
Some abuse comes from real, permanent addresses. Signals such as many accounts from one network, repeated payment details, unusual signup speed or the same device across accounts catch what email checks cannot. They are a complement, not a replacement: email checks stop cheap, anonymous signups early, and behaviour signals catch the determined ones later.
What does not work: keyword and pattern rules
Rules such as rejecting domains that contain temp or mail, or rejecting cheap domain endings, both miss and harm. Many disposable domains have ordinary names, and millions of legitimate sites use endings such as .xyz or .click. In our data the most common ending among disposable domains is .com, used by 36.2% of them.
Which combination should you use?
At signup, check the domain with an API that combines lists, mail-server checks and operator matching, act on the category, and treat unknown as unknown rather than safe. Keep behaviour signals for the abuse that gets through. Review false positives with a simple correction process so real customers are never stuck.
Source for provider behavior: Disban methodology. Product-policy guidance is Disban's interpretation.