Email validation API with mailbox and catch-all checks
Send an address and find out whether mail to it will be accepted. Each lookup checks syntax, the domain's MX records and the mailbox itself, then flags catch-all, disposable and role addresses. 1 credit per lookup.
{
"success": true,
"data": {
"email": "jane.doe@example.com",
"status": "deliverable",
"sub_status": "mailbox_exists",
"checks": {
"syntax": true,
"domain": true,
"mx": true,
"smtp": true
},
"flags": {
"catch_all": false,
"disposable": false,
"role": false,
"free_provider": false
},
"mx_host": "mx1.example.com"
},
"meta": {
"credits_used": 1,
"credits_remaining": 999,
"cached": false,
"request_id": "req_8f3a2c1e9b7d"
}
}What you get back
The fields most teams branch on. The full response is in the sample on this page and in the API reference.
statusStatusdeliverable, undeliverable, risky or unknown. The one field most rules are built on.sub_statusSub-reasonWhy the status was assigned, for example mailbox_exists, mailbox_not_found or greylisted.checks.mxMX recordsWhether the domain publishes mail servers that can receive email.checks.smtpMailbox checkWhether the receiving server confirmed the mailbox over SMTP.flags.catch_allCatch-alltrue when the domain accepts mail for every address, so the mailbox cannot be confirmed.flags.disposableDisposabletrue when the domain belongs to a temporary inbox service.flags.roleRole addresstrue for shared addresses such as info@ or support@ that are not one person.flags.free_providerFree providertrue when the address is on a free webmail service instead of a company domain.What Email Validation does
A mailbox check, not only a pattern match
After syntax and DNS pass, the lookup opens an SMTP conversation with the receiving server and asks whether the mailbox exists. No message is sent to the address.
Four statuses and a reason
Every result is deliverable, undeliverable, risky or unknown, with a sub-reason such as mailbox_not_found or mailbox_full. Build rules on the status and keep the reason for debugging.
Catch-all domains called out
Some servers accept mail for any address, real or not. Those domains are flagged as catch-all and the address is marked risky, so you do not mistake an accept-everything server for a confirmed mailbox.
Disposable, role and free-provider flags
Throwaway inbox services, shared addresses such as info@ or sales@, and free webmail providers each get their own boolean. Decide per use case which ones you accept.
See the response before you sign up
Fill in the request and run it. The dashboard has the same form, plus history, bulk upload and live data.
Fill in the field and run the lookup to see what comes back.
One POST request
Send JSON with a Bearer key. The same key works for all 79 products.
curl -X POST https://api.1lookup.dev/v1/email-validation \
-H "Authorization: Bearer YOUR_API_KEY" \
-H "Content-Type: application/json" \
-d '{"email":"jane.doe@example.com"}'- Endpoint
POST /v1/email-validation- Base URL
https://api.1lookup.dev- Request
email- Price
- 1 credit
- Coverage
- Global
- Bulk
- CSV upload and bulk API
- Cache
- Repeats within 7 days are free
- Also via
- Dashboard and MCP server (run_lookup)
What teams use it for
Stop bad addresses at the form
Validate as the user submits. Reject undeliverable addresses with an inline error and block disposable domains if you need a lasting contact.
Clean a list before a send
Run the file through bulk validation, remove the undeliverable rows and segment the risky ones. Fewer bounces protect the sender reputation your campaigns depend on.
Screen purchased or scraped leads
Check addresses before they enter your sequencer. Role addresses and catch-all domains can go to a lower-priority track instead of your main cadence.
Re-verify before you re-engage
People leave jobs and abandon inboxes. Verify dormant contacts again before a win-back campaign instead of finding out from the bounce log.
Catch-all domains and servers that block verification cannot be confirmed at the mailbox level. Those results come back as risky or unknown, not deliverable.
1 credit
Credits come with your plan and work on every product. Requests that fail on our side are never charged. Beyond your plan, extra credits are pay as you go.
See pricing| Plan | Per 1,000 credits | Per 1,000 lookups |
|---|---|---|
| Starter $29/mo | $4.83 | $4.83 |
| Growth $99/mo | $3.96 | $3.96 |
| Pro $299/mo | $3.32 | $3.32 |
| Scale $799/mo | $2.66 | $2.66 |
Email Validation questions
How does email validation work?
The lookup checks the address format, confirms the domain has mail servers, then asks the receiving server over SMTP whether the mailbox exists. It also checks the domain against disposable and free-provider lists and looks for role-style local parts.
What do risky and unknown mean?
Risky means the address may accept mail but carries a warning, usually a catch-all domain or a full mailbox. Unknown means the receiving server did not give a usable answer, for example because of greylisting or a timeout.
What does validation cost?
One credit per address. Unknown results caused by greylisting or timeouts are not charged, and neither is a repeat check of the same address within 7 days.
Are there addresses it cannot verify?
Yes. Catch-all domains accept every address, so the mailbox cannot be confirmed and the result is risky. Some providers also refuse or delay SMTP checks, which produces an unknown.
Will the person receive an email when I validate?
No. The SMTP conversation stops before any message is transmitted, so nothing lands in the inbox.
Related products
Email Authentication Check
Grade a domain's MX, SPF, DKIM and DMARC setup from 0 to 100.
Signup Check
Allow, review or block a new signup, with the reasons, in one call.
Email Finder
A verified work email from a first name, last name and company domain.
Run Email Validation on your own data
Starter is $29 a month for 6,000 credits, enough for 6,000 lookups a month.