
2026-10-25 · 4 min read
How to Verify an Email List
Every email list decays. People abandon accounts, companies rebrand and change domains, and a surprising number of addresses were never valid in the first place. Verifying your list finds the addresses that would bounce so you can remove them before they hurt your sender reputation.
Here is a practical, step-by-step process you can run on any list, whatever tool you use.
Why verify before you send
Bounce rate is one of the first things email providers look at when deciding whether your mail reaches the inbox. A single campaign sent to a stale list can produce a spike of hard bounces that drags your reputation down for weeks afterward — affecting every recipient, not just the bad addresses.
Verification also tells you the truth about your list. If a third of your contacts are dead, you want to know that before you report on open rates or spend money on a send. Clean data means clean metrics, and clean metrics mean decisions you can actually trust.
Step 1: Export and prep the list
Export your contacts from your CRM or email platform into a CSV. At minimum you need the email address column; anything else is optional.
Before you verify, strip out the obvious junk by hand or with a quick pass: blank rows, duplicated rows, and addresses with visible typos. You do not need to be perfect here — the verifier will catch the rest — but removing duplicates now saves credits and keeps your counts honest from the start.
Step 2: Understand what each check does
A verification run is not a single test. A good tool walks each address through layers, cheapest first:
- Syntax — is the address well-formed? A local part, an
@, a properly formed domain. - MX records — does the domain accept mail at all? No MX means undeliverable by definition.
- SMTP mailbox — does the specific mailbox exist? The tool connects to the mail server and checks, without sending an actual message.
- Disposable and role detection — is this a throwaway account or a shared
info@/sales@address? - Catch-all — does the domain accept any address, making "deliverable" a soft claim?
Each layer removes a different category of bad data, and the tool returns a reason with each failure so you know what you are looking at.
Step 3: Run the bulk verification
Upload your CSV to a bulk email checker. The tool detects the email column, lets you preview and remap it, and shows you the cost before any credits are spent. Then you start the job and it verifies every row, returning a verdict, a score, and a reason per address.
The job runs asynchronously for larger lists, so you can start it and come back to the results when it is done rather than babysitting a progress bar.
Step 4: Segment by verdict
This is where the real work happens, and it is not just "delete the invalids." Segment the results:
- Valid — safe to keep and send to.
- Invalid — remove. These will bounce.
- Risky — disposable, role, or catch-all addresses. Decide per segment: block disposables, watch role accounts, and treat catch-all domains with caution.
The reason field is what lets you make these judgment calls. A typo and a throwaway account both fail, but they deserve different handling. A catch-all address might be perfectly real — you just cannot prove it — so removing it outright is a business decision, not an obvious one.
Step 5: Re-import and schedule re-verification
Re-import the clean segments into your sending tool, then put verification on a schedule. Because lists decay continuously, a verification pass is a snapshot, not a permanent fix. Re-verify before every major campaign and after any period of inactivity.
A good cadence is: verify at the point of capture (via API or form validation), run a bulk pass before every significant send, and do a full re-verification whenever a list has gone quiet for a few months.
Common mistakes to avoid
- Verifying once and forgetting. Lists churn. One pass buys you a clean list for a month or two, not forever.
- Treating every failure the same. Disposable, role, and catch-all addresses need different decisions, which is why the reason matters.
- Skipping the cost preview. Know how many credits a job will consume before you run it.
FAQ
How long does a bulk verification take?
It depends on the list size and the depth of the checks. Syntax and MX checks are fast; SMTP probing takes longer. Larger lists run as a queued job you can poll to completion.
What should I do with addresses that can't be verified?
Some addresses cannot be confirmed either way — for example, when a mail server refuses to answer. Treat them as risky rather than valid, and avoid sending critical messages to them.
Verify your list now
Upload your list to the bulk email checker and get a verdict for every address in one pass. For more on the difference between checking structure and checking reachability, see email verification vs validation.