Disposable Email API: isDisposable in One Call

You call GET /v1/email-validation/:email and the JSON response includes an isDisposable flag alongside the full nine-check breakdown, so blocking a burner signup is one condition in your handler. Median latency sits around 380 ms, and sub-50 ms for cached domains.

Prefer not to write code at all? The FoxGuard widget ships with blockDisposable on by default, so your form rejects throwaway addresses before submit. Request and response shapes live in the API docs.

A disposable email is any address on a domain built to be thrown away: temporary inboxes, burner providers, and ten-minute-mail services people use to clear a signup gate without handing over a real address. Mailinator, Guerrilla Mail, Temp Mail, and thousands of lesser-known domains all fall in this bucket, and new ones appear daily.

They are the addresses most likely to fuel fake accounts, trial abuse, and junk signups, and they never convert. Disposable detection is one of the nine checks our verification engine runs on every address it sees.

No. Privacy relays forward to a real, monitored inbox, which is the opposite of a burner. The SMTP handshake in our nine-check pipeline confirms a live mailbox sits behind the relay, so those addresses come back deliverable, not disposable. The isDisposable flag is reserved for domains whose inboxes are built to self-destruct.

Unsure about one specific address? Run it through the disposable email lookup and read the per-check verdict yourself.

Continuously. The disposable-domain list our engine matches against is refreshed all day rather than shipped quarterly, so a throwaway provider that went live this morning is caught this afternoon. Freshness is the whole game here, because burner services rotate domains precisely to outrun stale blocklists.

There is a second net underneath. The engine also scores domain age as one of its nine checks, so a day-old domain raises the risk score even before it is catalogued anywhere. Details on every check sit under email verification.

Block when a signup hands out value immediately: free trials, credits, coupons, or anything a fraud ring can farm with fresh inboxes. Flag and review when the cost of a false rejection is higher than the cost of a junk row, like a newsletter or a waitlist.

The API gives you both levers: the isDisposable boolean for a hard gate, plus the overall score for softer policies. On forms, FoxGuardshows a custom message like "Disposable emails are not allowed" so legitimate users self-correct on the spot.

Static lists rot. Burner providers spin up new domains daily, and a repo updated whenever a maintainer finds time will always lag the domains doing the actual damage this week. A list match alone also says nothing about a brand-new domain nobody has catalogued yet.

Verifox pairs the continuously refreshed list with live signals: domain age, MX records, and a real SMTP handshake from the nine-check verification engine, measured at 99.99% accuracy on a 1,000-address benchmark. A text file on GitHub cannot do any of that.

Yes, because the policy is yours. The API returns the verdict; your code decides what to do with it, so allowlisting a domain is one extra condition before you check isDisposable. Nothing to configure on our side, no support ticket.

The FoxGuard widget goes one step further with per-field overrides: set data-verifox-block-disposable="false" on a specific input and that field accepts throwaway addresses even when blocking is on globally.

Yes. The tool above runs 4 checks per day with no account, no card. It executes the same nine-check engine the paid API runs, disposable-domain match included.

Create a free account and you get 1,000 credits on the spot, or 2,500 if your signup email is a work address. Past that, credits are pay-as-you-go and never expire, with volume pricing shown for your region.

Yes. POST /v1/email-validation/bulk accepts up to 100,000 emails per job, or a CSV upload, and processes roughly 10,000 emails per minute on the standard tier. Every row comes back with its own isDisposable verdict.

Smaller list and no code handy? Paste it into the free email validator instead; your free signup credits cover most small lists outright.

No. Every address, whether it arrives from the free checker above or from an API call, is verified in memory and discarded the moment the response returns. We never store, log, or sell them.

Verifox is SOC 2 Type II compliant, with the full Trust Center report available on request. The privacy policy spells out exactly what we touch and what we never keep.