Skip to content
Blog
Article
History · 8 min read

A history of disposable email — from 2003 Mailinator to 2026 multi-provider

Disposable email is older than Gmail. Here's a 23-year history of how it evolved from a one-engineer hack to a multi-billion-signup industry.

Disposable email has a longer history than most users realise. It predates Gmail (2004), predates the iPhone (2007), and predates the modern signup-form-with-OTP convention itself. Here's the timeline.

2003: Mailinator

Engineer Paul Tyma builds Mailinator as a side-project. The innovation: any address @mailinator.com works without registration. Public inboxes; anyone can read anyone's mail; no signup. The site goes viral on Slashdot. Mailinator becomes the canonical reference for what "disposable email" means.

2004: Yahoo Disposable Addresses

Yahoo Mail launches a disposable-address feature for Yahoo accounts: generate up to 500 alias addresses tied to your real inbox; delete an alias when it gets spammy. This is essentially the first commercial alias service. It's discontinued in 2018.

2005: 10MinuteMail

10MinuteMail launches with a different proposition: an inbox that auto-destroys after 10 minutes (extendable). The time-bomb concept becomes a UX standard for temp mail.

2007: Trashmail / GuerrillaMail / others

A wave of alternatives launches. GuerrillaMail (2008) differentiates with a Tor-friendly design and persistent inbox URLs. Trashmail (2007) adds forwarding-to-real-mail features. Public-inbox provider DispoMail.com emerges and disappears.

2010–2013: The arms race begins

Anti-fraud vendors emerge. Kickbox launches in 2012 with the explicit value-prop "detect disposable email". Stripe (founded 2010), at the start, blocks Mailinator but accepts most others. By 2013 Stripe blocks ~50 disposable domains.

2014: Temp-Mail.org

Temp-Mail.org launches with a more polished UI than its predecessors and aggressive SEO. By 2016 it's the #1 Google result for "temp mail".

2018: Mail.tm

A community-developed service with a free public REST API launches. Mail.tm becomes the backbone for many smaller temp-mail sites that aggregate it. Multi-provider front-ends start to emerge.

2019: SimpleLogin / Apple Hide My Email

SimpleLogin launches as a privacy-focused alias service (not temp mail — alias mail). Acquired by Proton in 2022. Apple ships Hide My Email in 2021 as a paid iCloud+ feature. The alias category is now its own thing.

2020: Disposable-domain blocklists go mainstream

The open-source list disposable-email-domains/disposable-email-domains crosses 50,000 entries. NeverBounce, ZeroBounce, Kickbox, and Bouncer dominate the validation-API market. Most modern SaaS signup flows include a disposable check by 2022.

2021–2024: TempMail.lol

TempMail.lol launches with a paid tier offering custom domains — the first credible response to the blocklist arms race. Acceptance rates on services that block public temp-mail domains rise dramatically.

2026: PocketInbox and multi-provider aggregation

The current generation. Multi-provider failover (rotate Mail.tm → Mail.gw → TempMail.lol on rate limit), polished iOS-style UIs, structured-data SEO, OTP auto-extraction, full PWA support. The big idea: no single provider can serve every use case, so aggregate the best ones behind one polished front-end.

What's next

Three trends to watch:

  • Privacy-respecting commercial. Apple Hide My Email shipped as a default; SimpleLogin grew 10× post-Proton. Alias mail is becoming standard. Temp-mail use cases narrow to one-time signups and bypass.
  • Custom-domain-as-default. Free temp-mail domains are increasingly blocked. The free tier may eventually cap at "newsletter signups only"; serious signup bypass moves to paid tiers with custom domains.
  • Email-as-secondary-identity. SaaS signup is shifting to OAuth (Sign in with Google / Apple) and phone numbers. Email becomes notification-only; the temp-mail-vs-real-email distinction becomes less load-bearing.

Related: Best temp-mail services 2026 · Disposable vs alias email.

Sponsored
Ad space (consent or AdSense ID required)

Continue reading

Read the FAQ · Back to PocketInbox