email risk score api
Email risk score API
Score email addresses by risk so your team can block obvious abuse and review gray cases.
Risk scores are useful when you want a yes, no, or review decision.
They can account for disposable domains, catch-all behavior, and provider type.
They make moderation easier to automate.
{
"result": "risky",
"score": 64,
"signals": ["mx_found", "free_email", "catch_all"]
}What is a risky email?
An address that is valid but likely to behave poorly or create operational cost.
Should risky always mean invalid?
Not always. It depends on your risk tolerance and customer base.
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.