A benchmark run by VerifySwift put 17 disposable email detection services through 272 checks across 16 temporary email providers. The headline numbers are stark: a 59% average detection rate, and 4 services scoring below 50%. Most of the tools developers trust to block fake signups are failing silently.
This post covers what the data shows, where Temp Mail Detector sits, and what the findings mean practically.
The Methodology
Each of the 16 temp mail providers had a fresh address generated. That address was tested against all 17 detection services via their primary interface, whether API, dashboard, or web tool. Every result was screen-recorded and scored: a pass means the service correctly flagged the address as disposable; a fail means it accepted it as legitimate.
This is a domain-level detection test. It measures whether services can identify known temporary mail infrastructure, which is the foundational requirement for any disposable email checker.
The Results Matrix: A Wide Spread
The full results matrix reveals a significant gap between the top performers and the rest. Green scores cluster around the top of the rankings. Red dominates the bottom. Several services that are widely integrated into developer toolkits scored below 10 out of 16.
The overall 59% detection rate is a useful anchor. It means a randomly selected detection service, applied to a randomly selected disposable address, fails to catch it over 40% of the time. For any signup flow where fake accounts carry real cost, that failure rate is not acceptable.
Top Performers
VerifySwift ranked first
This is the service that ran the test, which invites fair scrutiny. Self-published benchmarks where the author wins require a transparent methodology to be credible. In this case, the screen-recorded results and public matrix allow independent verification. The result holds.
TempMailDetector ranked second.
TempMailDetector scored 14⁄16. Two providers slipped through. That is the honest number, and it is worth understanding in context.
TempMailDetector’s Result: Context Matters
The two misses prevent TempMailDetector from claiming a clean sweep, and that should be acknowledged directly.
Emailnator, one of the services included in the benchmark, operates on Gmail infrastructure. Detecting it requires the checker to receive and evaluate a full user-submitted email address, matching it against known Gmail alias patterns.
TempMailDetector performs validation at the domain level only. No full email address is required or stored. This is a deliberate privacy design decision: the user’s email never touches TempMailDetector’s infrastructure beyond the domain portion.
The Bottom Performers: A Real Problem
Several services scored in the range of 4-7 out of 16. These are not edge cases. Some are well-known, actively marketed email verification platforms.
The report identifies WhoisXML as a notable failure: despite being a well-resourced data provider, it failed to flag a single disposable address in this test. That is a 0/16 score. Any integration relying on it for disposable email detection is providing no protection.
The “risky” label some services attach to results also came in for criticism. Flagging an address as “risky” rather than “disposable” shifts the classification burden onto the developer without giving them a clean signal. It is a hedge that makes the tool easier to defend and less useful to implement.
Hardest-to-Detect Providers
The benchmark calls out Emailnator, Mails.org, and EmailOnDeck as the addresses that most services failed to catch. These are the providers to benchmark against if you are evaluating any detection service. If a tool cannot catch these three, it is not covering the realistic threat surface.
Key Findings, Summarised
Static blocklists are insufficient. Services relying on fixed domain blocklists consistently underperformed against providers not yet on those lists. Real-time analysis or regularly updated data is necessary.
Price does not predict accuracy. Several paid, enterprise-positioned services scored below free alternatives. Vendor marketing around detection accuracy is not a reliable signal.
Emailnator is a systematic blind spot. Because it uses Gmail infrastructure, most domain-level checkers cannot detect it without full-address analysis. This is a known limitation. Services that score well against Emailnator are either processing full addresses or maintaining specific heuristics for Gmail alias abuse.
“Risky” classifications are not actionable. A checker that returns “risky” instead of a boolean disposable/not-disposable result is offloading the decision to the developer without the data to make it. This matters for automated signup flows.
Where This Leaves TempMailDetector
For use cases where full-address submission to a third-party is unacceptable, TempMailDetector’s approach is the relevant comparison point. On that basis, the gap between TempMailDetector and first place is one provider category: Gmail-alias-based disposable services.
The benchmark validates domain-level detection as competitive and maps exactly where the remaining gaps are. Closing them is the next step: We are currently training our own model to do exactly that and will soon offer this as a second detection endpoint.
Data source: 3rd party test conducted by VerifySwift, published January 2025. 272 individual tests across 17 services and 16 disposable email providers. Download infographic.
