Verification for cold email at volume
Cold email teams run on infrastructure that is expensive to replace. Warmed domains, aged mailboxes, and a sending reputation built over months. A bounce rate that crosses a threshold burns the lot.
Every serious sending platform now ships some verification built in. Understanding what that check is doing, and what it is not, decides whether a second pass is worth the credits.
Built-in verification is a filter, not a verdict
Instantly, Smartlead and the rest bundle a check because the bounces hurt them too. What they bundle is usually a syntax and MX check plus a cached lookup, which is fast and cheap and catches the obvious dead domains.
What it does not do is run a full SMTP handshake against every address at send time, and it cannot, because doing that at their volume from their infrastructure would get their probe addresses blocked. A cached verdict from six weeks ago is also not a current one on data that decays this fast.
The gap is the catch-all handling. A bundled check that reports accept-all domains as valid is not lying to you, it is simply not probing for it, and around 28% of a B2B list sits on one. Knowing which addresses are unconfirmable is the difference between a segmented send and a surprise.
How the work gets done
The order that matters for cold email teams, rather than a generic checklist.
Verify the scraped list before it reaches the sender
Scraped and enriched data is where the invalid addresses are. Checking before import keeps the sending platform's own bounce statistics clean, which matters because that is what its throttling reads.
Split catch-alls into their own campaign
Separate domains, separate ramp. If that segment bounces, the damage is contained to the infrastructure you assigned to it rather than to every mailbox you own.
Keep the unknowns out of the first send
Unknown means a server refused to answer. Re-check in a couple of weeks, when greylisting and throttling have moved on, before committing sending reputation to them.
Re-verify anything older than a month
Prospect data decays fast, and a list sitting in a sequence queue for six weeks is not the list you verified.
What verification will not do here
What it costs
At outbound volumes the $549 tier for 500,000 works out at $0.0011 an address. Unknowns and duplicates are never billed, which on scraped data with heavy overlap is a meaningful share of the row count.
Every tier works the same way. Unknown results and duplicates are never billed, and credits do not expire.
Questions we get asked
Instantly already verifies. Why pay twice?
Their bundled check is a fast filter, usually syntax, MX and a cached lookup. It is not a live SMTP handshake with a catch-all probe on every address, and the catch-all segment is exactly where a cold list surprises you.
What bounce rate is safe?
Under 2% is healthy. Past 5% you are being treated as a sender who does not maintain a list, and on cold email that reputation is the asset you cannot rebuild quickly.
Should I send to catch-all addresses at all?
As their own campaign on separate infrastructure, with a ramp. That way the bounce rate on that segment is information rather than an incident.
Does verification remove spam traps?
No, and treat any vendor claiming it does with suspicion. A pristine trap is indistinguishable from a working mailbox at the protocol level.
Try it on your own list first
100 free checks a month, no card. Run a sample and read the unresolved count before you decide anything.