temporary email detection api
Temporary email detection API
Temporary mailbox detection helps protect signup flows and reduce disposable abuse.
Temporary email providers change quickly, so freshness matters.
A maintained detection API helps keep your blocklist current.
It is most effective when paired with signup throttling and score limits.
curl -X POST "https://your-domain.com/api/v1/[email protected]" \
-H "X-Api-Key: ev_your_key_here"What is the goal?
Prevent short-lived addresses from creating long-term records in your system.
How often should it update?
Frequent updates are better because the provider landscape moves quickly.
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.