throwaway email detection api
Throwaway email detection API
Use a throwaway detector to catch short-lived inboxes before they enter your system.
Throwaway mail is common in free trials and spammy lead capture.
It is a strong signal when the same domain appears across many bad signups.
You can block it outright or fold it into a risk score.
curl -X POST "https://your-domain.com/api/v1/[email protected]" \
-H "X-Api-Key: ev_your_key_here"What makes it throwaway?
Short-lived providers, temporary routing, and abuse-heavy patterns.
Should I allow it?
Usually only if your product explicitly accepts anonymous or temporary email use.
Why disposable detection matters
Disposable inboxes distort activation metrics, increase support noise, and make abuse easier. A disposable detector is most useful when it runs before account creation, not after the user has already entered your system.
What makes a strong detector
A useful implementation combines a maintained domain list, DNS lookups, and risk scoring. That reduces the chance of relying on one stale signal and gives you a cleaner block-or-warn decision.
FAQ
How do I use this page?
Use it as a quickstart reference and link it from your docs, onboarding flow, or marketing page.
What should I do next?
Create an account, try the demo, and move the integration into your backend with a real API key.
Should disposable always mean invalid?
For most public signup flows, yes. In some low-friction products you may only warn.
How often should the list update?
As often as possible, because throwaway providers change quickly.