How-to
Verify a single address
Verify one email address in the dashboard or with the API, choose between fast and full mode, and use verification to catch bad addresses at sign-up.
This guide shows how to check one email address, either by hand in the dashboard or from your code with the API. It also covers using verification in a sign-up form to stop typos and throwaway addresses before they reach your list.
Before you begin
- Each verification costs 5 credits. Check your balance in the sidebar or in WorkspaceBilling.
- For the API, use an API key with Full Access. Sending-only keys can’t verify addresses.
Fast and full mode
| Mode | Checks | Use it for |
|---|---|---|
fast (API default) |
Syntax, MX records, domain age, disposable, role, free-provider and random-looking addresses | Sign-up forms and anything a person is waiting on. |
full (dashboard) |
Everything in fast, plus a connection to the recipient’s mail server to check the mailbox: deliverable, disabled, inbox full and catch-all |
Knowing whether a mailbox exists, for example before an important send, when a few extra seconds don’t matter. |
Both modes cost the same. full takes longer, usually a few seconds and up to about 40 seconds, because it talks to the recipient’s mail server, which can be slow or refuse to answer. When it refuses, the result is unknown rather than a guess. See How the mailbox check works and Verification results for what each check means.
Verify an address
-
Open Email Verification. Go to Email VerificationEmails and select Verify Email.
-
Enter the address. Type it into Email and select Verify Email. The dashboard uses
fullmode, so it also checks the mailbox. -
Open the result. The address appears in the list with its Status, Result, Risk, Score, Created date and days until it’s Expiring. Select it to see every individual check, such as Deliverable, Catch-all, Valid Syntax, Disposable, Role Account and Has MX Records. A check the mail server didn’t answer clearly shows Unknown.
To check many addresses at once, verify a list instead.
Call Verify an address with the address and, optionally, the mode:
curl https://api.emailit.com/v2/email-verifications \
-X POST \
-H "Authorization: Bearer $EMAILIT_API_KEY" \
-H "Content-Type: application/json" \
-d '{ "email": "ada@example.com", "mode": "full" }'The result comes back in the response:
{
"id": "ev_6Hq2Lm9Tx4Pz",
"object": "email_verification",
"email": "ada@example.com",
"status": "completed",
"score": 100,
"risk": "low",
"result": "safe",
"mode": "full",
"checks": {
"valid_syntax": true,
"disposable": false,
"role_account": false,
"inbox_full": false,
"deliverable": true,
"disabled": false,
"free_email": false,
"gibberish": false,
"catch_all": false,
"smtp_connect": true,
"has_mx_records": true,
"domain_age": 10957
},
"address": {
"mailbox": "ada",
"domain": "example.com",
"suffix": null,
"root": "ada@example.com"
},
"did_you_mean": null,
"mx_records": [
{ "priority": 10, "exchange": "mx1.example.com" }
],
"created_at": "2026-10-01T10:24:11Z",
"updated_at": "2026-10-01T10:24:11Z"
}In fast mode, the mailbox checks (deliverable, disabled, inbox_full, catch_all and smtp_connect) are null because they weren’t tested. In full mode, a mailbox check is null when the mail server didn’t give a clear answer.
| Status | When |
|---|---|
200 |
The address was verified. This includes badly formed addresses, which come back with result: "invalid". |
400 |
email is missing, or mode isn’t fast or full. |
402 |
The workspace has fewer than 5 credits. |
Every successful verification also fires an email_verification.created event. See Webhook event types.
Verify addresses at sign-up
Checking an address when someone types it is the cheapest way to keep a list clean. A typo caught at sign-up never becomes a bounce.
-
Call the API from your server. Never put your API key in browser code. Send the address from your sign-up handler, in
fastmode. -
Set a timeout and fail open. If verification is slow or returns an error, let the sign-up through. Losing a real customer costs more than one bad address.
-
Act on the result. Block what’s clearly wrong, suggest fixes for typos and let everything else through.
export async function checkSignupEmail(email) {
const controller = new AbortController();
const timer = setTimeout(() => controller.abort(), 5000);
try {
const res = await fetch('https://api.emailit.com/v2/email-verifications', {
method: 'POST',
headers: {
Authorization: `Bearer ${process.env.EMAILIT_API_KEY}`,
'Content-Type': 'application/json',
},
body: JSON.stringify({ email, mode: 'fast' }),
signal: controller.signal,
});
if (!res.ok) return { ok: true }; // fail open
const verification = await res.json();
if (verification.result === 'invalid') {
return {
ok: false,
message: verification.did_you_mean
? `Did you mean ${verification.did_you_mean}?`
: 'Please check your email address.',
};
}
if (verification.result === 'disposable') {
return { ok: false, message: 'Please use a permanent email address.' };
}
// Accept the address, but offer a correction if one looks likely.
return { ok: true, suggestion: verification.did_you_mean };
} catch {
return { ok: true }; // timeout or network error: fail open
} finally {
clearTimeout(timer);
}
}A few tips:
- Use
did_you_mean. For common domain typos, such asada@gmial.com, it contains the likely address,ada@gmail.com. Show it as a suggestion the person can accept. - Don’t block role addresses outright.
info@orsales@is often how small businesses sign up. Flag them instead. - Verify once per address. Each call costs credits, so verify when the form is submitted, not on every keystroke, and store the result.