Email risk API

Should you trust this email address?

A risk score with confidence and explainable signals — context-aware for how different forms define risk differently.

What the risk engine evaluates

0–100 risk score

Built from six weighted categories: email quality, domain, disposable, provider, deliverability, reputation.

Separate confidence value

Tracks how much real evidence backed the score — a fast-mode guess and a fully-verified result are never conflated.

Allow / review / block decision

A direct routing decision derived from the score band, not just a raw number to interpret yourself.

Explainable signals

Every point of the score traces to a named signal with severity, impact, and a plain-language description.

Context-aware weighting

Signup, B2B lead, CRM, marketplace, and payment contexts each weight specific signals differently.

Domain reputation & age

Composite reputation scoring and domain-age signals catch infrastructure risk, not just the address itself.

Example request

curl https://api.emailriskradar.com/v1/email/check \
  -H "Authorization: Bearer $API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"email": "user@example.com", "context": "b2b_lead"}'

FAQ

Is risk scoring the same as spam scoring?

No. Spam scoring evaluates message content and sending reputation. This evaluates the address itself, independent of any message being sent.

Does a high score prove fraud?

No — it means several independent signals were present. It's evidence to weigh via your own decision routing, not a verdict.

How does context change the score?

Context multiplies specific signal weights before summing. A role-based address weighs far more in a B2B lead context than in a generic signup context.

Can I see why a specific score was produced?

Yes — every response includes the individual signals, their severity, and their point impact, so the score is always traceable to specific facts.

We use Google Analytics to understand site traffic, and only load it if you accept — nothing runs before you choose. Signing in still stores a strictly necessary session token regardless. See the Privacy Policy for details.