Email verifier that tells you what it could not confirm
An email verifier is only useful if it is honest about the limits of what it checked. This one runs every check the receiving server allows, shows you each result, and marks the rows it cannot confirm instead of dressing them up as deliverable.
Six checks on every address
Each check answers one question, and each one can fail on its own. You see all six results, not one traffic light.
| Check | Question it answers | What a failure means |
|---|---|---|
| Syntax | Is the address shaped the way the mail standard requires | The address can never receive mail and should be dropped |
| Domain and MX | Does the domain publish mail servers | The domain accepts no mail at all, so every address on it bounces |
| Mailbox at the server | Does the receiving server accept this specific mailbox | The mailbox does not exist or has been closed |
| Catch-all | Does the server accept every address on the domain | No external check can confirm one mailbox, so the row is marked catch-all |
| Role address | Is this a department address rather than a person | It reaches a shared inbox, which changes how you should write to it |
| Disposable and free provider | Is this a throwaway mailbox or a consumer account | It is not a work address, so it is a weak entry in a B2B list |
Statuses you get back
There are four, and each one tells you what to do next.
- Deliverable: the server confirmed the mailbox. Send to it.
- Undeliverable: the address, the mailbox or the domain failed. Drop it.
- Catch-all: the server accepts everything, so we could not confirm this one mailbox. Send carefully or keep it out of a cold sequence.
- Risky: the address works but it is a role address, a disposable domain or a consumer mailbox. Decide by list, not by row.
Check an address before you build a list around it
Paste the address and watch the checks run. This is the same verification the product runs on every row of a bulk job.
| Check | Result | What it means |
|---|
- MX hosts
- Provider
- Receives mail
- Catch-all
A bounce is not a wasted slot, it is a scored event
Mailbox providers count how often your domain sends to addresses that do not exist. A run of bounces reads as a list you did not check, and the response is to route more of your mail to spam. That applies to the addresses that were fine as well, and to every campaign you send after it.
Verification before the send keeps that number down. It is the cheapest thing you can do for deliverability, and it is why teams re-check a list they bought, a list they exported from the CRM last quarter and a list from a conference badge scanner.
- An address goes stale when a person changes jobs, and normal staff movement retires a meaningful share of any B2B list within a year.
- A domain can drop its mail servers between your export and your send.
- A mailbox that worked in January can be closed by March without anyone telling you.
Verified finds are the only thing that counts
Every plan counts verified results. An address that comes back undeliverable, catch-all or risky costs nothing against your monthly limit, so checking a doubtful list is never a reason to hold back.
- Starter verifies up to 1,000 addresses that come back deliverable each month, in jobs of up to 1,000 rows.
- Growth raises that to 5,000 and adds scheduled re-verification of saved lists.
- Scale raises it to 20,000 and adds the API, so verification runs at the moment a record enters your CRM.