Disposable Email Detection API

Email Qualification is a deep deliverability verification endpoint. It performs full Email Validation and adds an SMTP inbox check plus catch-all detection, then returns a single qualification verdict: valid, invalid, risky, disposable, or unknown.

Why use this API?

• Block fake signups and trial abuse (disposable, relay domains)
• Improve lead quality by validating real inboxes
• Reduce bounces and protect sender reputation
• Detect catch-all domains and route to a safer workflow

What the API returns

Identity & normalization

• email, normalized_email (lowercased automatically)
• domain extracted from the email

Domain & mailbox type signals

• disposable, public_domain, relay_domain, education
• role_account, role_type (e.g., contact, info, sales)
• is_alias, did_you_mean (helpful for typos)
• has_gravatar (optional enrichment signal)

DNS & deliverability posture

• dns.mx + dns.mx_records
• dns.mx_providers (provider + grade, e.g., “professional”)
• dns.spf, dns.spf_valid
• dns.dmarc, dns.dmarc_valid

SMTP inbox verification + catch-all

• smtp_valid (SMTP-level inbox check)
• is_catch_all (domain accepts all recipients)

Final decision & risk

• qualification (one of: valid, invalid, risky, disposable, unknown)
• risk_score (numeric risk indicator)

Use cases

1) Signup protection (bots, fake accounts, free-trial abuse)

Use the verdict to decide instantly:

• Block if qualification=disposable or disposable=true
• Step-up verification (OTP / CAPTCHA / rate-limit) if qualification=risky or relay_domain=true
• Allow if qualification=valid and smtp_valid=true

Result: fewer fake signups, cleaner user base, better activation metrics.

2) Reduce bounces and protect sender reputation

Before adding an email to newsletters, sequences, or invites:

• If qualification=invalid or smtp_valid=false, don’t send (or request an update)
• If DNS posture is weak (missing/invalid SPF/DMARC), flag for caution workflows

Result: lower bounce rate, better deliverability, fewer spam complaints.

3) Catch-all detection for safer outreach & scoring

Catch-all domains can make inbox existence ambiguous.

• If is_catch_all=true, treat as “deliverable but uncertain”
• Route to a double opt-in flow or lower confidence scoring
• Combine with risk_score to prioritize manual review

Result: less wasted outreach, more reliable lead scoring.

4) B2B lead qualification and routing

• Downrank public_domain=true (consumer webmail)
• Flag role_account=true (e.g., contact@, info@) to route to a “company” funnel or enrichment path
• Prefer qualification=valid + professional MX provider signals

Result: better MQL→SQL conversion and cleaner segmentation.