Email Verification in 2026: How to Clean a List Before It Kills Your Deliverability

Every guide to email verification opens the same way: keep your bounce rate under 2%. It is repeated so often that most people assume Gmail publishes it somewhere. Gmail does not. Neither does Yahoo, and neither does Microsoft.

Disclosure: this post contains affiliate links. We may earn a commission at no extra cost to you.

What they publish is a different number entirely, and knowing which is which changes how you spend money on list hygiene.

The short answer

Verify your list before every campaign, budget about $0.006 an email, and stop treating bounce rate as the metric that matters. Bounces damage you indirectly — through sender reputation — but the threshold the mailbox providers actually enforce is your spam complaint rate, and no verifier on earth can lower that for you.

Verification is necessary and cheap. It is not sufficient, and a lot of people buy it expecting it to fix a problem it does not touch.

The number everyone quotes, and the number that is actually enforced

Google's published requirements for bulk senders — anyone sending 5,000 or more messages a day to Gmail addresses — are specific. You must:

• Keep the spam rate reported in Postmaster Tools below 0.30%, with Google explicitly recommending you stay below 0.10% to leave yourself headroom
• Authenticate with SPF and DKIM, and publish a DMARC record at minimum p=none
• Align the domain in your From: header with either your SPF or your DKIM domain
• Support one-click unsubscribe per RFC 8058, and process unsubscribes within two days

Yahoo mirrors these. Microsoft has aligned on the authentication and unsubscribe requirements, though it has not published a spam-rate figure of its own.

Notice what is missing: a bounce-rate threshold. The 2% figure is an industry convention, not a rule any provider enforces. Google's guidance touches bounces only obliquely, in a best-practice note recommending you automatically unsubscribe recipients whose messages have bounced repeatedly.

That does not make bounces harmless. A list full of dead addresses signals to a receiving server that you acquired your data badly, and that judgement feeds the reputation score which governs whether your mail reaches an inbox at all. But the causal chain runs bounces → reputation → placement, not bounces → a threshold you are measured against. It is worth understanding the difference, because it tells you where the rest of your effort should go once the list is clean.

What a verifier actually does

A good verifier runs an address through a sequence of independent checks, each cheaper and less intrusive than the last one it protects you from:

1. Syntax — is it a validly formed address at all
2. Gibberish and disposable detection — is it a throwaway or a keyboard mash
3. Domain — does the domain resolve
4. MX records — does the domain accept mail
5. SMTP connection — does the mail server respond
6. Mailbox existence — does this specific inbox exist
7. Catch-all detection — does the server accept mail for every address, making the previous check meaningless

Steps one to four are trivial and every tool gets them right. The difference between a good verifier and a bad one lives in steps five to seven, where you are negotiating with real mail servers that may greylist you, rate-limit you, or lie.

What it costs in 2026

Verification is priced per email, and the rates have compressed to the point where the decision is rarely about money.

Bouncer is cheaper at every band up to 100,000, where ZeroBounce takes a narrow lead before falling behind again at a million. For anyone verifying under 50,000 addresses — which is nearly everyone reading this — the gap is real but small in absolute terms: about $100 a year on a 10,000-address list verified monthly.

Two things matter more than the per-email rate at that scale. Bouncer's credits never expire, which suits the lumpy way most people actually clean lists — a big purchase before a campaign, then nothing for two months. ZeroBounce's freemium tier gives 100 credits every month, which is a genuinely useful trickle if you only ever spot-check.

Bouncer starts you with 100 free credits, enough to sanity-check a sample before you commit to anything.

When the verifier you already own is enough

If you run outreach through a platform that bundles verification, buying a standalone tool may be redundant. Snov.io includes a seven-stage verifier in its base subscription and charges one credit per address checked.

The arithmetic is less flattering than it looks. Snov.io's Starter plan is $29.25 a month on annual billing for 1,000 credits, which works out at roughly $0.029 per verification — around four times Bouncer's rate at the same volume. Worse, those credits are shared with prospect search, so every address you verify is an address you did not find, and on the entry tiers they reset monthly rather than rolling over.

So the honest rule is: use the bundled verifier for the addresses your platform sourced, because those are pre-filtered anyway. Use a dedicated tool for imported lists, purchased data, and anything older than three months. Our Snov.io vs Apollo comparison covers what those credits are worth against the alternative.

The catch-all problem nobody solves

Some domains — a large minority of corporate ones — accept mail addressed to anything at all and sort it out internally. A verifier cannot tell you whether jane@company.com exists on such a domain, because the server says yes to every address it is asked about.

Every tool reports these as "accept-all", "catch-all", or "risky". What they do next is where they differ, and where marketing claims get slippery. Some tools guess using pattern matching against known-good addresses on the domain. Some decline to guess. Neither approach is verification, and any vendor implying otherwise is overselling.

The practical handling: send to catch-all addresses, but segment them into their own campaign so that if they bounce heavily they do not contaminate the reputation of your main sending domain. Treat the deliverability data from that segment as its own experiment.

The workflow that actually works

1. Verify immediately before sending, not on import. Email addresses decay at roughly 2% a month through job changes alone. A list verified in March and sent in July has already rotted.
2. Sample before you buy. Run 100 addresses through the free tier first. If a verifier flags 40% of a list you believe is clean, the problem is more likely the tool than the list.
3. Delete the invalids. Do not "try them anyway." The whole point of the exercise is not sending to them.
4. Segment the catch-alls into a separate sending domain or at minimum a separate campaign.
5. Then fix the thing verification does not fix. Set up SPF, DKIM and DMARC with proper alignment, add RFC 8058 one-click unsubscribe, and watch your spam rate in Postmaster Tools rather than your bounce rate. Our guide to email deliverability best practices walks through that setup.
6. Re-verify quarterly, or before any campaign to a list you have not mailed in 90 days.

Beyond verification: the tools that watch the rest

Once the list is clean, the remaining deliverability risk lives in your sending setup, and that needs monitoring rather than a one-off clean. Both vendors sell this as a separate product.

Bouncer's Deliverability Kit runs seed tests — sending to a set of monitored inboxes and reporting where the mail landed — plus blacklist monitoring across your IPs and domains. It starts at $25 a month for 250 test emails and 10 monitored IPs or domains, rising to $125 for 1,000 tests and 25 monitors, and $250 for 2,500 tests and 50 monitors. ZeroBounce's equivalent suite starts at $49 a month.

There is also Bouncer Shield, which verifies addresses at the point of capture on your own signup forms, priced from $2 per 1,000 checks. For anyone running paid acquisition into a form, that is the cheapest intervention on this page: it stops bad addresses entering the list at all, which is strictly better than removing them later.

Whether any of it is worth paying for depends on volume. Under a few thousand sends a month, Postmaster Tools and a quarterly verification pass cover you. Above that, a blacklisting you find out about three weeks late costs more than a year of monitoring.

Do this next

If you are sending cold and have never verified: pull your list, take a 100-address sample, and run it through Bouncer's free credits. The invalid percentage that comes back tells you whether you have a hygiene problem or an acquisition problem — and those need very different fixes.

If it comes back under 3%, your list is fine and your deliverability trouble is elsewhere: authentication, sending volume ramp, or copy that draws complaints. If it comes back over 15%, stop sending entirely until the list is cleaned, because you are actively burning a domain that will take months to rehabilitate.

And if you are still assembling the list rather than cleaning it, the B2B cold email templates and the sourcing side matter more than the verifier for now.

FAQs

What bounce rate is actually acceptable?

No mailbox provider publishes one. The widely used 2% figure is a convention rather than an enforced threshold. What Gmail does publish is a spam complaint rate below 0.30%, with 0.10% recommended. Aim to keep hard bounces under 2% because it correlates with list quality, not because a rule requires it.

Is email verification worth it for small lists?

At $8 for a thousand addresses, the cost of verifying is trivially smaller than the cost of not verifying. Even a 500-address list is worth checking if you bought or scraped it. If you collected every address through a double opt-in form on your own site, the value is much lower — those addresses were verified at the point of capture.

Do verification credits expire?

It varies, and it is worth checking before you buy in bulk. Bouncer's credits do not expire. Platform-bundled credits, including Snov.io's on the entry tiers, generally reset each billing cycle whether you used them or not.

Can a verifier stop me landing in spam?

No. It removes addresses that would bounce, which protects your sender reputation, but spam placement is driven by authentication, complaint rate, sending patterns, and content. A perfectly verified list sent from an unauthenticated domain will still land in spam.

How often should I re-verify?

Quarterly for an active list, and always before mailing anything you have left dormant for 90 days or more. Business addresses decay faster than personal ones because people change jobs.

What about catch-all addresses — send or skip?

Send, but segment them. They are not invalid, they are unverifiable, and a large share of them are real. Isolating them means a bad outcome on that segment does not damage the reputation you have built for the rest.