Detect disposable and throwaway emails
Why this signal matters
Disposable email domains exist to create one-time inboxes for signups, trials, and abuse. Blocking them at registration protects trial conversion metrics, reduces support noise, and limits credential-stuffing targets. A checker that combines curated lists with live DNS catches domains that have not yet appeared on public blocklists.
FAQ
- How does disposable detection work?
- EmailGuard matches against curated disposable domain intelligence and can fall back to live DNS when a domain is not yet on public lists.
- What is detection_source?
- precomputed means the domain matched curated data. live_dns means infrastructure was classified at lookup time via DNS.
- Should I block every disposable address?
- Most signup flows block disposables to reduce abuse and fake accounts. Product teams sometimes allow them in low-risk contexts.
Related tools
Need volume, webhooks, or team access?
The same detection stack powers the EmailGuard API. Start free, then scale with scoped API keys and predictable rate limits.