Email validation
Find out whether an email will bounce before you send to it, including catch-all addresses most validators can't judge.
Email validation
Email validation tells you whether an address will bounce before you send to it. Send one email; we return a verdict, a deliverability score out of 100, and flags for catch-all, role-based, disposable, and consumer addresses.
It works on catch-all domains, which accept every address at the mail server and so look valid to most validators. Catch-all domains are where a list that "validated clean" still bounces.
Emails from Contact Reveal already come back
with a status (on a coarser valid / risky / unknown / invalid scale
than the verdicts below). Use this for addresses you got elsewhere: CRM records, inbound
signups, or another provider's export.
What comes back
| Field | What it tells you |
|---|---|
verdict | ok, risky, undeliverable, or inconclusive |
deliverability_score | 0–100; higher is more likely to deliver |
is_catch_all | The domain accepts all addresses, so the server alone can't confirm this one |
is_role_based | A shared inbox like sales@ or hello@ rather than a person |
is_disposable | A throwaway-address provider |
is_consumer | A consumer mailbox (Gmail, Outlook) rather than a company domain |
email_provider | Who hosts the mailbox |
How to read the verdict:
verdict | What to do |
|---|---|
ok | Send |
risky | Likely to deliver but not certain; send in small batches or to your warmest segment |
undeliverable | Don't send; it will bounce |
inconclusive | We couldn't get a clear answer; treat as unverified |
Operations
| Operation | What it does | Reference |
|---|---|---|
| Email validation | Check whether one email will bounce | emailBounceDetection |
{ "apiKey": "sk_live_...", "email": "jane@example.com" }The endpoint allows 300 requests per minute. For a list, run requests in parallel within that limit.
Using it effectively
- Validate before every campaign, not just once: addresses go stale as people change jobs.
- Don't drop catch-all addresses blindly. Use the verdict and score instead of the catch-all flag alone; many catch-all addresses are real.
- Keep role-based addresses out of personal outreach. They reach a shared inbox, not your contact.
Credits
1 credit per email checked. Requests that fail on our side aren't charged. See Billing & credits.
Credit amounts are defaults — custom pricing is available for bulk use cases.
Related: Phone validation · Contact Reveal · Reverse email lookup
Hashed Email Lookup
Turn SHA-256, MD5, or SHA-1 hashed emails (HEMs) back into the real address and the LinkedIn profile behind it — up to 100 per call, billed only on hits.
Phone validation
Check whether a phone number is real and reachable right now, and see its carrier, line status, and caller ID name.