disposable email detection api
Disposable email detection API
Block throwaway inboxes before they reach your signup table.
Disposable detection protects onboarding and prevents low-quality records.
It is one of the most important anti-abuse checks for public forms.
It works best together with MX and role-based filtering.
curl -X POST "https://your-domain.com/api/v1/[email protected]" \
-H "X-Api-Key: ev_your_key_here"What is a disposable domain?
It is a provider that exists mainly for temporary inboxes and short-lived use.
When should I block it?
Block it at signup if you need real users and durable contactability.
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.