disposable email provider list api
Disposable email provider list API
Keep a current provider list so you can identify throwaway domains with minimal latency.
A domain list is a practical first line of defense.
You can combine it with live verification for better confidence.
The list should be maintained and updated as providers change.
curl -X POST "https://your-domain.com/api/v1/[email protected]" \
-H "X-Api-Key: ev_your_key_here"Why a list matters
Provider lists catch known throwaway services quickly and cheaply.
What else should I check?
Add syntax, MX, and risk scoring on top of the list result.
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.