email deliverability check api
Email deliverability check API
Combine syntax, DNS, disposable, and SMTP signals into one deliverability decision.
Deliverability checks help you avoid sending to broken or risky addresses.
They are especially useful for onboarding, notifications, and campaign hygiene.
A score-based result is easier to use than a long list of raw flags.
{
"result": "risky",
"score": 64,
"signals": ["mx_found", "free_email", "catch_all"]
}What is deliverability?
It is the likelihood that a message can reach a live mailbox and be accepted.
How is it different from validation?
Validation is broader; deliverability focuses more on inbox reachability.
Why a score is easier to use
A single score is easier to wire into product decisions than a long list of raw checks. It lets your app map email outcomes to simple actions such as accept, warn, review, or block.
What should affect the score
Score models usually combine syntax, MX, disposable status, role-based status, catch-all behavior, and optional SMTP results. The point is to make the decision explainable and consistent, not merely numeric.
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.
Is high score always safe?
No. It only means the address looks better by your configured criteria.
Should I expose the score to users?
Usually as a friendly result, not as the full internal formula.