Disposable email detection API
Mailsurity checks any email address in real time and tells you whether it's disposable, temporary, or fake, including brand-new burner domains no static blocklist has caught yet. One HTTP call, no SDK required.
Last verified July 25, 2026.
What is disposable-email detection?
A disposable email address is one created specifically to be used once and then abandoned. Services like Mailinator, 10 Minute Mail, Guerrilla Mail, and hundreds of rotating lookalikes let anyone generate a working inbox in seconds, with no verification and no cost. People use them to skip email confirmation, claim a “new signup” free trial or discount more than once, or join a mailing list without ever intending to read it.
Disposable-email detection means checking whether an email address belongs to one of these throwaway services before you create the account, add the subscriber, or spend a free-trial credit. As a disposable email detection API, Mailsurity does this by checking the domain against a constantly growing list of known throwaway providers, then falling back to live analysis for domains nobody has cataloged yet.
Types of disposable-email services
“Disposable email” covers a few different setups, and a detector that only handles the first one misses the rest:
Rotating public inboxes
Mailinator, Guerrilla Mail, 10 Minute Mail, and similar services: no signup, a publicly readable inbox, gone within minutes to hours.
Auto-rotating throwaway domains
The same underlying service keeps registering new domain names once the old ones land on blocklists. Only the domain name changes; the mailbox behavior stays the same.
Bulk-registered lookalike clusters
Dozens to hundreds of near-identical domains pointed at the same mail server. Blocking one domain by name does nothing to the rest of the cluster.
A name-only blocklist catches the first type and struggles with the other two, since the domain name itself is disposable. Mailsurity's disposable email detection API is built to catch all three: layer five of the cascade below checks the reputation of the mail server actually receiving a domain's email, not just the domain name, which is exactly what the second and third cases need.
Why disposable signups hurt deliverability
A disposable signup rarely stays neutral. The confirmation or welcome email either hard-bounces once the throwaway inbox expires, or lands in an inbox nobody ever intended to keep. An address that was never going to engage is far more likely to get marked as spam than politely unsubscribed.
Bounce and complaint rates feed directly into how mailbox providers (Gmail, Outlook, and the rest) score your sending domain. A list full of disposable addresses drags that score down for everyone on it, including the real subscribers and customers you actually want landing in the inbox, not the spam folder. Catching disposable addresses at signup protects deliverability for every email you send afterward, not just the one that got blocked.
Who this is for
Newsletter authors & course creators
Disposable subscribers inflate your list and hurt deliverability.
Stop fake subscribersWhy static blocklists miss new domains
Throwaway-mail providers spin up new domains constantly, on purpose: it's how they dodge blocklists. A .json file of bad domains downloaded from a public repo is out of date by the time you deploy it. Mailsurity runs every check through five layers, in order, so a static list is only ever one of them:
Your own rules, if you set any
Allow-list a partner domain or deny-list a known-bad one from your dashboard. A rule you set always wins over everything below it.
A curated known-legitimate list
Large webmail and corporate providers (Gmail, Outlook, and the like) get an instant answer, since there’s no reason to run the full check on domains everybody already trusts.
Our disposable-domain list, 220k+ and growing
A constantly updated list of known throwaway domains, built from public disposable-domain feeds and ongoing monitoring of real throwaway-mail providers.
A cached verdict, if we’ve seen this domain recently
Once we’ve checked a domain live, we cache the answer for 30 days, so a repeat signup from the same domain resolves instantly and consistently.
Live detection for anything brand-new
For a domain nobody has seen before, we resolve its mail servers and score patterns common to throwaway addresses. Only when the case is genuinely ambiguous does an AI model break the tie, and we cache that verdict too, so the next signup from that domain is instant.
That's the gap a static list can't close: a brand-new throwaway domain gets caught the first time it ever shows up, not weeks later after someone notices it and adds it to a list.
What about burner emails specifically?
Burner-email services exist specifically to dodge blocklists: new domains, disposable inboxes, sometimes hundreds of interchangeable lookalikes fronting the same underlying service. A list, however large, only ever knows about a domain name after someone has added it — which is exactly the gap a brand-new burner domain is built to exploit.
Layer 5, live detection, is what actually closes that gap. Instead of checking the domain name against a list, it resolves the domain's mail servers and scores it on the spot: how random or high-entropy the name itself looks, how closely it resembles known throwaway-service naming patterns, and the reputation of the mail servers behind it. Only a genuinely unclear result escalates to an AI model. That means a burner domain can get flagged on the very first request it ever makes, before anyone has manually added its domain name anywhere.
This is exactly where the bulk-registered lookalike clusters described above show up in practice: dozens of near-identical burner domains sharing a handful of mail servers. Once one of those mail servers has been seen serving throwaway addresses, Mailsurity remembers it, so the next brand-new sibling domain pointed at the same server inherits that suspicion immediately, rather than needing its own name individually catalogued first.
Calling the disposable email detection API
One HTTP call, JSON in and out, no SDK to install. Send the email, read isDisposable off the response:
curl -X POST https://www.mailsurity.com/api/check-email \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "email": "user@mailinator.com" }'A throwaway address comes back like this:
{
"email": "user@mailinator.com",
"isDisposable": true,
"source": "list"
}Full authentication details, error codes, and copy-paste examples in eight languages are in the API reference.
How Mailsurity compares
Kickbox and ZeroBounce are full-stack email-verification platforms; disposable detection is one flag among many they check. BounceZero is a closer competitor: a dedicated disposable-email checker that claims 99.8% accuracy and 65+ signals on its own site. DeBounce is closer on price: it runs a free disposable-check API, no signup mentioned. Disposable, temporary, and fake email detection is Mailsurity's only product, not one flag among many.
| Mailsurity | Kickbox | ZeroBounce | BounceZero | DeBounce | |
|---|---|---|---|---|---|
| Built for | Disposable / temporary / fake email detection, purpose-built | General email verification & deliverability | Full verification + 9-tool marketing suite (ZeroBounce ONE) | Dedicated disposable-email checker, self-reported 65+ signals | Free disposable-email-check API |
| Free tier | 500 free checks, no card required | Not published here — check their site | Not published here — check their site | Not published here — check their site | Free disposable-check API, no signup mentioned |
| Paid pricing | $5–$59/mo for 5,000–100,000 checks See plans | ~$0.008/verification · $10 per 1,000 credits | ~$0.008/verification · ZeroBounce ONE: $99/mo for 10,000 credits | Not published here — check their site | Not published here — check their site |
| How it detects disposable domains | 5-layer cascade: your rules → legit-list → 220k+ domain list → cached verdicts → live heuristics + AI for brand-new domains | Disposable flag as one check among many verification signals | Disposable flag as one tool among nine in the ONE bundle | Self-reported 65+ signals, dedicated disposable checker | List lookup against a continuously updated disposable-domain database |
| Detection accuracy | 99.4% | Not independently verified here | Not independently verified here | Self-reported 99.8% — not independently verified here | No published figure |
Mailsurity pricing shown is live from our current plans. Competitor figures are sourced from each vendor's public pricing page, last verified 2026-07-25 — confirm current rates before deciding. See the full comparisons hub for more vendor breakdowns.
Go deeper: integration guides
Step-by-step walkthroughs for wiring disposable-email checks into the stack you already run — or see the full guides index.
Block disposable emails in Next.js
Reject throwaway signups with one server-side API call.
Read the guideBlock fake signups in Clerk & Supabase Auth
Layer a freshness check on top of their built-in static lists.
Read the guideBlock disposable signups in Auth0
Deny the registration before the account is ever created, with a Pre User Registration Action.
Read the guideBlock signup fraud on Vercel
Stop throwaway signups at the edge, before they hit your app.
Read the guideBlock fake subscribers in ConvertKit & Beehiiv
Keep disposable addresses off your list before they hurt deliverability.
Read the guideThe disposable-email npm package for Node.js
Skip hand-written HTTP calls with the mailsurity npm package.
Read the guideEvaluating this for a security or compliance review? See the Trust & Security page for subprocessors, certifications, and data-retention details.
Frequently asked questions
See how many disposable signups slip past your current setup
Paste a list of your signups — Mailsurity shows how many a standard blocklist misses. No signup needed; the part before the @ never leaves your browser.