Try it on a real address
No account required. This runs the same scoring pipeline as the live API — limited to a few free checks per visitor.
- Risk score, confidence & signal breakdown
- Local-part analysis (entropy, randomness, patterns)
- Domain reputation, age & infrastructure, SPF/DMARC
- Live SMTP mailbox verification — confirms the inbox actually accepts mail
- Catch-all detection (needs a real SMTP handshake)
- Bulk checking, webhooks & an API key for your own app
One request.
Full picture.
Every check returns a risk score, a deliverability read, verification confidence, and plain-language signals explaining exactly why — not just a number you have to trust blindly.
Get an API keycurl https://api.emailriskradar.com/v1/email/check \
-H "Authorization: Bearer $API_KEY" \
-H "Content-Type: application/json" \
-d '{"email": "john@example.com", "mode": "standard", "context": "signup"}'Built for signal, not guesswork.
Risk & deliverability, scored separately
A 0-100 risk score with a confidence rating, kept distinct from whether the mailbox is actually deliverable — so you can decide what "risky" means for your own flow.
Local-part intelligence
Entropy, character randomness, keyboard-pattern and name-likeness detection catch generated-looking addresses that pass basic syntax checks.
Domain reputation, age & infrastructure
Checked against 200,000+ disposable domains merged from six maintained sources, then classified further by mail infrastructure, age, and reputation — not just a static blocklist.
Real SMTP mailbox verification
Opt-in "full" mode performs an actual SMTP handshake against the mailbox, protected by a circuit breaker so one bad mail server can't slow down your whole batch.
Bulk checking & webhooks
Submit thousands of addresses in one batch and get results by polling or via webhook delivery when the job completes — no need to hold a connection open.
Context-aware scoring
Tell the API whether this is a signup, a B2B lead, a CRM import, or a payment flow, and the scoring weights adjust to what actually matters for that context.
Built around what you're actually screening.
Signup screening
Catch fake and bot-generated accounts at the point of signup, before they ever reach your database.
B2B lead scoring
Weigh role-based and free-provider addresses differently for inbound leads and CRM imports than for consumer signups.
Checkout & payment fraud
Use email risk as one signal alongside your payment fraud tooling — not a replacement for it, a second opinion.
Bulk list cleanup
Clean a purchased list, a stale database, or a one-time CRM import in a single asynchronous batch.
Verification tools tell you it's valid.
This tells you if you should trust it.
| Capability | Most verification APIs | Email Risk Radar |
|---|---|---|
| Result | Valid / invalid / unknown | 0-100 risk score + confidence + allow/review/block |
| Explainability | Category or single opaque score | Every point traces to a named signal, severity & impact |
| Context | Same evaluation for every use case | Weighting adapts to signup, lead, marketplace, or payment |
| Pricing | Often purchased credits, sometimes expiring | Monthly quota from free, or a one-time bulk pass |
Sourced, factual breakdowns against 9 named competitors — see the full comparison.
Simple, usage-based pricing.
Pick a monthly plan for ongoing traffic, or a one-time pass for a single bulk job.
Built to not overreach.
No vanity numbers here — just what the system actually does with the addresses you send it.
Single checks aren't stored
The address you submit to a single check is processed and returned — not written to any usage record afterward.
API keys hashed at rest
Only a short lookup prefix and a hash are stored — the full key exists only once, at creation.
Webhooks are signed
Every delivery carries an HMAC-SHA256 signature, so you can verify it genuinely came from this API.
You control bulk data
Bulk-job addresses are retained until you request deletion or close your account — never indefinitely by default.
FAQ
An API that evaluates an email address and returns a 0-100 risk score, a confidence value, and named, explainable signals — syntax, domain, disposable/free-provider status, local-part shape, and optionally live SMTP mailbox verification — plus an allow/review/block decision you can route on directly.
Verification answers whether an address is valid and likely to receive mail. This goes further: it weighs multiple signals into a trust score for a specific context (signup, B2B lead, marketplace, payment), and explains exactly which signals drove the result rather than returning a single opaque number. See What Is an Email Risk API? for the full breakdown.
Yes — 250 checks per month at no cost, ongoing, with no credit card required. See Email Verification API Pricing for how that compares across the category.
Yes — POST a batch to the bulk endpoint and either poll for status or register a webhook to be notified when the job completes, instead of holding a connection open for a large batch.
Yes, in full mode — it asks the receiving mail server via an SMTP handshake whether it would accept the address, without sending or waiting for a message to arrive.
This is a hosted API, called over HTTPS with a bearer API key — there's no separate SDK or self-hosted option, just plain REST calls that work the same from any language.