Email verification for cold email
Verify every lead list right before it goes into a sequence. Database exports and scraped lists carry dead mailboxes and lots of catch-all addresses, and every bounce they cause counts against the domains you send from.
Why cold email lists need verifying
Cold email has no opt-in to tell you an address is in use. The list comes from a lead database export, an enrichment tool or a scraper, and every record in it was collected or checked at some point in the past. Since then people have changed jobs, mailboxes have been closed and companies have moved domains.
The cost lands on your sending domains. Mailbox providers count bounces against the domain and the inbox that sent them, and cold email leaves little room: the domains took weeks to warm up, and one bad list can undo that. Verifying right before a list goes into Instantly, Smartlead or Lemlist removes the bounces you can see coming.
The workflow, from export to sequence
- 01
Export the list
Export a CSV from your lead source, whether that's Apollo, ZoomInfo, a scraper or a spreadsheet. Keep every column; MailVet adds its own at the end.
- 02
Upload it
Duplicates and malformed addresses are removed first, without using credits.
- 03
Let it verify
Every address gets syntax, domain, mailbox and catch-all checks. Most of a list finishes in minutes; the slowest catch-all checks finish in the background.
- 04
Split by result
Download the deliverable rows for the campaign. Keep risky and unknown rows in a separate file instead of deleting them.
- 05
Import into your sequencer
Upload the deliverable file to Instantly, Smartlead, Lemlist or whichever tool you send from, and map the columns as usual.
- 06
Re-verify before reuse
If a list sits for more than a few weeks, or you're re-running an old campaign, verify it again first.
What to do with each result
| Result | Reason | In a cold campaign |
|---|---|---|
| deliverable | accepted | Send |
| deliverable | catch_all_verified | Send: a confirmed mailbox on a catch-all domain |
| undeliverable | mailbox_not_found, invalid_domain, catch_all_no_mailbox | Remove, and never send |
| risky | mailbox_full | Hold; re-verify before the next campaign |
| risky | disposable | Remove; on a B2B list it usually points to a poor source |
| unknown | no_response | Re-run after a day; it's free |
| unknown | catch_all_unresolved | Skip, or send at low volume from a separate warmed domain |
Any result with the role flag | info@, sales@ and similar | Usually leave out of one-to-one sequences |
Unknown results cost nothing, so re-running them is free. Every code is explained on /email-verification-statuses.
Catch-all-heavy B2B lists
Many companies set their mail servers to accept mail for any address at their domain, so nothing is lost when someone misspells a name. On B2B lists that can be a large share of the file, and standard verification can't see past it: the server says yes to every address, so the verifier reports "accept-all" or "risky" and leaves the call to you.
That forces a bad choice: send blind and risk the bounces, or drop the segment and lose real prospects. MailVet checks the specific mailbox instead and returns catch_all_verified (send) or catch_all_no_mailbox (remove). It costs the normal single credit, and the addresses it can't settle come back unknown, free. Details on /catch-all-email-verification.
Protect the domains you send from
Verify right before sending
Not at export time, weeks earlier. The closer verification is to the send, the less has changed.
Keep unverified catch-alls off main domains
Send only catch_all_verified addresses from your primary domains. Anything unresolved goes to a separate, warmed domain or nowhere.
Suppress hard bounces everywhere
Add bounced addresses to your sequencer's blocklist and your CRM, so the next export doesn't bring them back.
Watch bounces per inbox
Pause a sending inbox that starts bouncing. The cause is usually one bad list, and it's cheaper to find it early.
Authenticate every domain
SPF, DKIM and DMARC on every sending domain. Verification fixes list problems, not authentication problems.
Verifying inside an automated pipeline
If leads flow in from an enrichment workflow rather than a CSV, verify them in the pipeline before they reach the sequencer. Call GET /v1/verify for each new lead (the account limit is 2,000 requests a second), or batch them into POST /v1/bulk jobs and act on the bulk.completed webhook. Both return the same results and reason codes as the uploader. Start with /docs/quickstart or /docs/bulk.
Cold email verification questions
Do I need to verify emails exported from Apollo or ZoomInfo?
Yes, right before you send. Lead databases run their own checks, but at some point in the past and often without a verdict on catch-all addresses. Re-verifying just before a campaign catches what has changed since.
Should I send cold emails to catch-all addresses?
Send to the ones MailVet verifies as deliverable (catch_all_verified) and remove the ones it marks undeliverable. For the few that stay unknown, skip them or send at low volume from a separate, warmed domain.
What bounce rate is safe for cold email?
Lower is always better. A common rule of thumb is to stay under 2%, and to pause any inbox or domain whose bounces suddenly jump, whatever the number.
Can I verify a list from Instantly, Smartlead or Lemlist?
Export the leads as a CSV, verify the file in MailVet, and import the deliverable file back. Your original columns are kept, so field mappings still work.
How often should I re-verify a cold email list?
Before every campaign if the list is more than a few weeks old. People change jobs constantly, and an address that was fine last quarter may bounce today.
Verify your next lead list free
Upload a CSV and see how many addresses are deliverable, dead or catch-all before a single email goes out. 100 free credits, no card.
Related
Last updated November 13, 2026