# Verify: email verification

`GET https://api.crawl4ai.com/verify`

Check if an email address can receive mail. Our own servers talk to the address's mail server from our own addresses and stop before the message: no mail is ever sent. The answer is valid, invalid, accept_all or unknown, with fixed reasons, the mail provider and a suggestion when the domain looks mistyped. Check one address with GET, or a list of up to 1,000 with POST.


curl:

```bash
curl "https://api.crawl4ai.com/verify?email=lena@praxis-hoffmann.at" \
  -H "Authorization: Bearer sk_live_..."
```

## Parameters

| Name | Type | Default | Description |
|---|---|---|---|
| email* | string | - | The address to check. |

## Response

json · shortened:

```json
{ "email": "lena@praxis-hoffmann.at", "status": "valid", "confidence": 0.95,
  "reasons": ["smtp_ok"], "provider": "google", "mx_host": "aspmx.l.google.com",
  "checked_at": "2026-11-13T09:41:07Z" }
```

`status`:

| Status | Meaning |
|---|---|
| valid | The mail server accepts this exact mailbox and refuses a random one. |
| invalid | Bad syntax, a domain with no mail server, or a mailbox the server refuses. |
| accept_all | The domain's mail server accepts every name, so no verifier can prove the mailbox from outside. Microsoft 365 domains get an extra account check that turns many of them into valid or invalid. |
| unknown | No usable answer now: timeout, greylisting, our address blocked, a DNS failure. |

`reasons` are fixed words, so your code can switch on them:

| Reason | Meaning |
|---|---|
| from_store | Answered from the stored result, no new check. |
| bad_syntax | The address is not written like an email address. |
| no_mx | The domain has no mail server. |
| dns_failed | Our DNS lookup failed twice; nothing is known about the domain. |
| smtp_ok | The mail server accepted this address and refused a random one. |
| rejected | The mail server refused this address with a permanent error. |
| catch_all | The mail server accepted a random address too. |
| probe_unclear | The mail server accepted the address but gave no clear answer about a random name, twice. |
| implicit_mx | The domain has no MX record; its own address record is the mail host. |
| disabled | The mail server says the mailbox is disabled or blocked. |
| full_inbox | The mail server says the mailbox is full; it exists. |
| no_connect | No connection to any address of the mail server. |
| greylisted | A temporary refusal that asks us to come back later. |
| blocked | The mail server refuses our address itself, not the mailbox. |
| timeout | The check ran out of time. |
| gateway | The mail server is a mail gateway; it answers for every name. |
| ms_account_exists | Microsoft's account check says the account exists. |
| ms_account_missing | Microsoft's account check says there is no such account. |
| pattern_match | The name follows the domain's known email pattern. |
| person_known | Lead holds a person with this exact address at this company. |
| role_address | A role mailbox such as info@ or sales@. |
| disposable | A disposable-mail domain. |

`provider`: `google`, `microsoft`, `yahoo`, `proofpoint`, `mimecast`, `barracuda` or `other`. `mx_host` is the mail server we talked to. `suggestion` is a likely fix when the domain looks mistyped (`gmial.com`).

## A list of addresses

`POST /verify` takes up to 1,000 addresses. The answer is one JSON object when the whole list is done, which takes up to a few minutes for 1,000.

```bash
curl https://api.crawl4ai.com/verify \
  -H "Authorization: Bearer sk_live_..." \
  -H "Content-Type: application/json" \
  -d '{ "emails": ["lena@praxis-hoffmann.at", "info@example.com"] }'
```

```json
{ "results": [ { "email": "lena@praxis-hoffmann.at", "status": "valid", "…": "…" } ],
  "done": { "done": true, "job_id": 4821,
            "counts": { "valid": 1, "invalid": 0, "accept_all": 0, "unknown": 1, "pending": 0 },
            "retrying": 1 } }
```

A greylisted address comes back as `unknown` with the reason `greylisted`. `retrying` counts them: we check them again after 15 minutes, in the background. `GET /verify/jobs/{job_id}` returns `{job_id, done, counts, items}` with the later results.

## Other routes

| Route | Does |
|---|---|
| GET /verify?email= | One address (above). |
| POST /verify | A list of up to 1,000 addresses: `{"emails": [...]}`. |
| GET /verify/jobs/{job_id} | The state of a list: `{job_id, done, counts, items}`. |
| GET /verify/domain?domain= | One domain: `{domain, accepts_mail, provider, is_gateway, mx_host, catch_all, spf, dmarc}`. `catch_all` is `null` when we could not test it. |
| DELETE /verify?email= | Forgets the stored answer. Answers `204`. |

## Errors

| Status | Code | Meaning |
|---|---|---|
| 400 | bad_input | A missing or empty `email`, `emails` or `domain`, or more than 1,000 addresses in a list. |
| 402 | no_credit | Your balance is empty. Start a plan, or buy extra credits, and call again. |
| 404 | not_available | The service is not open to your account. |

Every 4xx and 5xx answer is free.

Price: 1.5 credits per address that answers valid or invalid when the mail server says so by itself; 3 credits when the domain accepts every name and we still resolved the address (reasons `ms_account_exists`, `ms_account_missing`, `pattern_match` or `person_known`). `accept_all` and `unknown` are free, and so is a repeat inside 30 days (an answer is kept 30 days). `GET /verify/domain` is 1 credit. A mailbox check is an SMTP conversation from our own addresses; no mail is ever sent.

**Try it with your key**

Run this call in the playground and see the real answer, the time and the units.
[Open the playground](https://crawl4ai.com/#playground)

---
Source: https://crawl4ai.com/docs/verify/
