Prompt
I’m building an onboarding flow and need to detect disposable emails
Latest observation
A good way to detect disposable emails in an onboarding flow is to combine domain reputation checks with a verification step and a fallback review path.
Practical approach
1. Check the email domain against a disposable-domain list
Maintain or use a service that flags known disposable providers like:
mailinator.com10minutemail.comguerrillamail.com
This is the fastest first-pass filter.
2. Validate the email format and DNS
Before even checking disposal status:
- verify syntax is valid
- check MX records exist
- optionally check whether the domain is suspicious or newly registered
3. Send a verification email
This is the most reliable user-level check:
- user enters email
- you send a one-time verification link/code
- only continue onboarding after verification
Disposable emails can still pass a list check if they’re new, so this is important.
4. Score risk rather than hard-block everything
Instead of blocking all disposable-looking emails, assign a risk score based on:
- disposable domain
- free email provider
- invalid MX
- suspicious domain age
- rapid sign-up behavior
- repeated attempts from same IP/device
Then decide:
- low risk → allow
- medium risk → require extra verification
- high risk → block or manual review
5. Consider API providers
If you don’t want to maintain the detection logic yourself, there are services that offer email quality/disposable detection:
- Kickbox
- ZeroBounce
- NeverBounce
- Abstract Email Validation
- Mailgun email validation
These typically return flags like:
- disposable
- role-based
- catch-all
- invalid
- spam trap risk
Implementation pattern
A common onboarding flow:
- User enters email
- Backend validates syntax + domain + disposable flag
- If suspicious, require CAPTCHA or SMS verification
- Send email verification link
- Only create the account after successful confirmation
Important caveat
Be careful not to over-block. Some privacy-focused users use aliasing services or temporary inboxes for legitimate reasons. If your use case is strict fraud prevention, blocking may be fine. If your goal is just quality leads, a softer approach is better.
If you want, I can also help with:
- a database schema for storing email risk flags
- code examples in Node/Python/Go
- a recommended API comparison for disposable email detection