Email verifier and email validation tool 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 checks the syntax, the domain and its mail records, disposable domains, role addresses, free providers and typos, shows you each result, and says plainly that it does not test the individual mailbox on the receiving server.
Paste an address and watch the checks run. It is the same verification the product runs on every row of a bulk job.
| Check | Result | What it means |
|---|
- MX hosts
- Provider
- Receives mail
- Disposable domain
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. We do not open a conversation with the receiving mail server, so there is no mailbox level or catch-all result, and we never show one.
| 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 |
| Published by the company | Does the company show this address on its own website | Nothing: the row can still be valid, it just has no published proof |
| Typo | Is the domain a misspelling of a common mail provider, like gmial.com | The address was probably mistyped, so check it before you send |
| 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
Each one tells you what to do next.
- Confirmed: the company published this address on its own website, and the row links to the page.
- Valid: the syntax is right, the domain accepts mail, and it is not disposable or a typo. The mailbox itself is not tested.
- Undeliverable: the syntax or the domain failed, so nothing can arrive. Drop it.
- Disposable: a throwaway mailbox provider. Drop it from a B2B list.
- Possible typo: the domain looks like a misspelling of a common provider. Fix it before you send.
- Role address and free provider are flags on a valid row, not a separate status. Decide by list, not by row.
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 company can take an address off its website when the person leaves, which a re-check shows you.
Verified finds are the only thing that counts
Every plan counts verified results. An address that comes back undeliverable, disposable or a possible typo 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 confirmed or valid 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.