Disposable Domain Detection API

Domain Validation API validates any domain instantly and returns high-signal indicators for deliverability, lead quality, and risk scoring.

What you get

• Disposable domain detection (disposable)
• Public webmail detection (public_domain)
• Relay domain detection (relay_domain)
• Education domain detection (education)
• Subdomain flag (is_subdomain)
• DNS & email checks: MX, SPF, DMARC + validation
• Trust signals: domain age (domain_age_days) + WHOIS data

Use cases

1) Stop signup abuse & fake accounts

When someone signs up with an email like name@tempmail.xyz, you can reduce spam, bots, and trial abuse by using the flags:

• Block if disposable=true
• Step-up verification (OTP + CAPTCHA + rate limiting) if relay_domain=true or the domain looks suspicious
• Route to manual review if the domain is very new (domain_age_days low) and DNS signals are weak

Typical outcome: fewer junk accounts, cleaner database, lower support and infrastructure cost.

2) Improve B2B lead quality & qualification

Many B2B workflows prefer company emails over public webmails:

• If public_domain=true, you can down-rank the lead score, ask for a work email later, or trigger a different nurture path.
• If the domain is corporate (not disposable/public) and has healthy DNS (MX present + SPF/DMARC valid), you can up-rank the lead.

Typical outcome: better MQL/SQL conversion and less time wasted by sales on low-intent leads.

3) Email deliverability readiness (before you send)

Before onboarding a customer to outbound sequences or newsletters, you can detect basic deliverability hygiene:

• MX present (dns.mx=true) → domain can receive mail properly
• SPF/DMARC valid → better protection against spoofing and often better deliverability
• If SPF/DMARC is missing/invalid, you can trigger setup guidance (in-product checklist) before enabling email features.

Typical outcome: fewer bounces, fewer “your emails go to spam” tickets, better sender reputation.

4) Fraud / risk scoring for payments or trials

Combine multiple signals to produce a simple risk score:

• Higher risk if disposable=true or relay_domain=true
• Higher risk if domain is very new (domain_age_days low)
• Higher risk if WHOIS is missing/odd or DNS is incomplete
• Optional CT (certificate_transparency=true) can add extra signals for suspicious certificate patterns

Typical outcome: fewer chargebacks, less card testing, fewer fraudulent trials.

5) Routing & personalization in-product

You can adapt the experience based on domain type:

• education=true → show student/academic pricing or onboarding
• Corporate domains → show “team setup” flows
• public_domain=true → more self-serve onboarding or ask for company domain for advanced features

Typical outcome: higher activation rates and a more relevant onboarding journey.

6) Data enrichment & segmentation

If you store only an email address, domain validation helps you segment users/companies:

• Separate consumer vs business signups
• Filter disposable/relay traffic from analytics
• Build audiences for lifecycle campaigns (“public email users” vs “company domain users”)