Verify a B2B list by running syntax, MX, SMTP and catch-all checks before the first send, then holding hard bounces under half a percent.

Key takeaways

  • Deliverability guidance in 2026 treats a total bounce rate above 2 percent as poor list hygiene, and a hard bounce rate above 2 percent as a risk to the whole sending domain.
  • For mail sent to personal Gmail accounts, Google asks bulk senders to keep reported spam under 0.10 percent and never to reach 0.30 percent, and since November 2025 non-compliant mail can be rejected temporarily or permanently.
  • B2B contact data decays about 22.5 percent a year and work emails 20 to 30 percent, so a list verified in January is a different list in September.
  • EmailAddress.ai puts catch-all addresses at 23 to 31 percent of B2B databases, and no SMTP check can resolve them.
  • At the 10,000-address tier, vendor pricing pages put bulk verification at $3.90 to $6.00 per thousand addresses, which is cheap against the cost of one burned domain.

A verified list is not a cleaner list. It is a list that will not cost you the domain you send from. That is the whole argument, and the arithmetic below makes it.

Why does a bought B2B list bounce?

Because it was accurate when it was collected and nobody collected it recently. B2B contact data decays continuously as people change roles, companies rename domains and mailboxes are retired. The decay is not a defect of one vendor. It is the physics of the category, and it is measurable.

Cleanlist's data decay analysis puts B2B data decay at about 22.5 percent a year and work email decay at 20 to 30 percent, citing Dun & Bradstreet and Validity. Landbase's compilation reports job title changes at 65.8 percent annually and phone number changes at 42.9 percent. It also gives a monthly rate near 2.1 percent, which it attributes to SMARTe and which compounds to about 22.5 percent a year.

That is why a list is a perishable good, and why the question is never whether to verify but how recently.

What bounce rate is actually safe in 2026?

Under 2 percent total, under 0.5 percent on hard bounces, is the working answer for B2B. Gmail and Outlook.com now reject non-compliant bulk mail to personal inboxes rather than only filtering it, so crossing the line can arrive as a 550 error and a damaged sending reputation instead of a quiet dip in opens.

MetricSafeWarningDanger
Total bounce rateUnder 2 percent2 to 5 percentAbove 5 percent
Hard bounce rateUnder 0.5 percent0.5 to 2 percentAbove 2 percent
Spam complaints (Google Postmaster)Under 0.10 percent0.10 to 0.30 percent0.30 percent and above
List age since last verificationUnder 30 days30 to 90 daysAbove 90 days

The bounce thresholds follow 2026 deliverability guidance compiled by EmailAddress.ai and Instantly. The spam figures come from Google's email sender guidelines FAQ. The 30-day list age row matches Instantly's advice to re-run validation on any list older than 30 days.

One precision matters for B2B lists. Google's sender requirements and its 0.10 and 0.30 percent spam thresholds apply to mail sent to personal Gmail accounts, and Google states that they do not apply to messages sent to Google Workspace accounts. Microsoft's 5,000-a-day rule covers Outlook.com, Hotmail and Live addresses. Most addresses on a B2B list sit on company domains, where the receiving gateway applies its own filtering, so the bounce thresholds above are the ones that protect you everywhere.

The five checks a verification pass must run

A complete pass runs five checks in order, each cheaper than the one after it. Syntax rejects malformed addresses for free. Domain and MX lookups confirm the domain can receive mail at all. SMTP probing asks the receiving server whether the mailbox exists. Role and disposable detection strips addresses that will never reply. Catch-all classification handles what is left.

The verification pass, cheapest check firstEach check shrinks the set the next one has to pay for.
  1. Syntax
  2. Domain and MX
  3. SMTP mailbox check
  4. Role and disposable addresses
  5. Catch-all classification
  6. Three files, valid, catch-all, invalid

Run them in that order because each one shrinks the set the next one has to pay for. Syntax and MX are essentially free and typically remove a meaningful slice of an old file before you spend anything on SMTP. Instantly's 2026 upload quality guide describes the same sequence as the standard pipeline, with format validation, duplicate detection, MX verification and SMTP mailbox checks as the core.

The check most teams skip is role detection. Addresses like info@, sales@ and contact@ pass every technical test and still produce complaints rather than replies, which is the metric that actually decides your sender reputation.

What does verification cost per thousand addresses?

At the 10,000-address tier, published prices run from $3.90 to $6.00 per thousand, and they fall under a dollar per thousand only at million-address volumes, where MillionVerifier lists 1 million verifications for $449. The spread between vendors is smaller than the spread created by how each one bills catch-all and unknown results, which is where the real cost difference hides.

ToolEntry pricePrice at 10,000 addressesAccuracy claimed by the vendorUnknown and catch-all results
Freelvy€49 a month for 1,500 creditsFinds and verifies emails rather than checking a list you hold, 3 credits per verified emailNot publishedA row that fails verification is never delivered and never billed
MillionVerifier$39 for 10,000$39, about $3.90 per thousand99%+Catch-all checks included at no extra cost, refund on risky results
Bouncer$8 for 1,000$60, about $6.00 per thousandNot stated on the pricing pageUnknown results and duplicates not billed
NeverBounce$8 for 1,000Not listed on the pricing page, down to $0.002 per credit at 2 million creditsNot stated on the pricing pageNot stated on the pricing page
ZeroBounce$39 for 2,000ZeroBounce ONE subscription from $99 a month, 10,000 credits minimum99.6% guaranteedUnknown results free, activity scoring costs one extra credit

Prices and claims were read on each vendor's pricing page on September 23, 2026: MillionVerifier, Bouncer, NeverBounce, ZeroBounce and Freelvy. Accuracy figures are the vendors' own claims rather than independent tests.

The last column is the one to read twice. On a list where a third of records are catch-all, being billed for those results raises the effective price per usable result by about half.

How do you handle catch-all domains?

You cannot resolve them with SMTP, so you classify them and decide how much risk to carry. A catch-all server accepts mail for every address at the domain, valid or not, which means the protocol gives the same answer for a real mailbox and an invented one.

EmailAddress.ai's processing data puts catch-all addresses at 23 to 31 percent of B2B databases, with actual deliverability on those records ranging from 40 to 85 percent depending on the domain. In LaGrowthMachine's tests, Bouncer flagged 87 percent of catch-all addresses as risky, using an algorithm that scores 47 signals beyond the SMTP response.

Three workable policies exist. Drop catch-alls entirely, which is the safe choice on a new domain. Send to them from a separate secondary domain, so a bad batch cannot hurt the mailbox you rely on. Or send to the scored subset above a confidence threshold and watch the bounce rate for the first 200 sends. Pick one before the campaign, not after the first bounce report.

When the address is a guess built from the owner's name, our guide on how to find the owner's email behind a contact form shows how to confirm the pattern first.

What does skipping verification actually cost?

More than verification, by roughly an order of magnitude, and the loss is not the wasted sends. Take a 10,000-row list bought at market rates and left unverified for six months. At a 22.5 percent annual decay rate, about 11 percent of it is already dead.

That is 1,100 hard bounces on a 10,000-send campaign, an 11 percent bounce rate, which is five times the level 2026 guidance treats as dangerous. Verifying the same file at $3.90 per thousand costs $39. The alternative is a burned domain, a warmup cycle of three to six weeks before you can send at volume again, and every campaign in that window postponed. There is no version of the arithmetic where $39 loses.

What changed for list verification in 2025 and 2026?

Enforcement hardened in 2025. Microsoft began rejecting non-compliant mail from domains sending more than 5,000 messages a day to Outlook.com, Hotmail and Live addresses on May 5, 2025, with the error 550 5.7.515, per Microsoft's announcement. Since November 2025, Gmail has been ramping up enforcement on mail to personal Gmail accounts that fails its sender requirements, with temporary and permanent rejections.

The second change is procedural. The IETF published DMARC as a Proposed Standard, RFC 9989, in May 2026, replacing RFC 7489. Google has required DMARC from bulk senders since February 2024, so authentication is not a recommendation you can defer while you fix your list. The practical effect for anyone verifying a list is that bounce hygiene and authentication now fail together, since a domain with a poor reputation gets less tolerance on everything else.

A verification pass you can run this afternoon

Export the list. Deduplicate on the address, then on the domain plus person, because vendor exports carry both kinds of duplicate. Strip role addresses and known disposable domains. Run the remainder through a verifier that does not bill you for catch-all results. Split the output into three files, valid, catch-all and invalid. If that pass is one of seven steps eating your Monday, our time audit of list building shows which steps to batch, automate or delete.

Send to valid first, at your normal volume, and watch the bounce rate over the first 500 messages. If it stays under 1 percent, add the catch-all file from a secondary domain. Add the invalid addresses to a suppression list in your sending tool or CRM rather than deleting them, as Instantly's upload guide recommends, so the next export that brings them back is blocked on import instead of verified and paid for again. Then diary the next pass for 30 days out, because the decay rates above start working the moment you finish. Deciding which companies deserve those verified sends first is the subject of our guide to B2B buying signals worth prioritising.

Where Freelvy sits in this conversation

Freelvy is our product, an AI sales platform. It works the way ChatGPT or Claude does. You describe the customer you want in one prompt, and Freelvy searches 40+ live sources at query time, maps, official company registries, job boards, storefronts and ad libraries, rather than filtering a stored database. It then enriches every row with verified contact data, 18 providers in cascade for emails and 12 for phone numbers, and writes and sequences the outreach from the same brief. The waterfalls find and verify more than 92% of emails and find more than 90% of phone numbers.

Freelvy screenshot: a table of web agencies in Austin that use HubSpot, with website, headcount, city, HubSpot status and what they do
In Freelvy, a single prompt returns the matching companies as a table.

For RevOps teams that own data quality, the verification question changes shape when the data is fetched at query time rather than read from a warehouse. A row that fails verification is never delivered and never billed, so every email in the file you receive has passed verification. The published credit catalogue prices a verified email at 3 credits and a verified phone at 15, and plans start at €49 per month for 1,500 credits with unlimited team members. An existing CSV can be pushed through the same data enrichment waterfalls. There is a free 7-day trial, no credit card, at freelvy.com.

How we verified these numbers

Vendor pricing pages (MillionVerifier, Bouncer, NeverBounce, ZeroBounce, Freelvy), Google's email sender guidelines FAQ, Microsoft's Outlook.com announcement and the IETF record for RFC 9989 were read on September 23, 2026. Decay rates, bounce benchmarks and catch-all shares come from the 2026 analyses linked inline, read on September 13 and again on September 23, 2026. The 10,000-row cost comparison is our own arithmetic on the published decay rates.

FAQ

What bounce rate is acceptable for cold email?

Under 2 percent total and under 0.5 percent on hard bounces is the working standard in 2026. EmailAddress.ai warns that a hard bounce rate above 2 percent can trigger inbox suppression across the whole sending domain. Strong senders sit under 1 percent. Gmail and Outlook.com now reject non-compliant bulk mail to personal inboxes, so the penalty can arrive as a hard failure rather than a slow decline.

How often should a B2B list be re-verified?

Every 30 days for a list in active use, and always before a campaign if the file is older than 90 days. With B2B data decaying about 22.5 percent a year and work emails 20 to 30 percent, a quarter of a stale file can be dead. Verification is cheap enough that frequency costs less than a single bounce incident.

Should you send to catch-all addresses?

Only from a secondary domain, and only after your valid segment has proved a bounce rate under 1 percent. Catch-all servers accept mail for any address, so SMTP cannot confirm the mailbox exists. EmailAddress.ai reports real deliverability on those records between 40 and 85 percent depending on the domain.

Which email verification tool is the most accurate?

Vendors publish their own figures rather than a shared test. ZeroBounce guarantees 99.6 percent and MillionVerifier claims 99 percent or more, while the Bouncer and NeverBounce pricing pages state no figure. Third-party tests report other numbers, such as 99.1 percent for Bouncer in LaGrowthMachine's 2026 comparison. The gap between the top tools is small enough that how each one bills catch-all and unknown results matters more to total cost.

Does verification stop emails landing in spam?

No. Verification stops bounces, which protects the sender reputation that decides placement. Spam placement is driven by authentication, complaint rate, content and sending patterns. Both matter, and a clean list with no DMARC record will still struggle. Our cold email deliverability checklist covers the other half.

Can you verify emails for free?

Small volumes, yes. Bouncer, MillionVerifier and ZeroBounce each offer 100 free verifications, and syntax plus MX checks can be run with open tooling. Free tiers rarely include catch-all scoring, which is the part that needs real infrastructure. At $3.90 to $6.00 per thousand on the 10,000 tier, paid verification is not the line item worth optimising.

What is a role address and why remove it?

An address tied to a function rather than a person, such as info@, sales@ or support@. They pass every technical check and still produce complaints instead of replies, because nobody owns the inbox. Removing them keeps your complaint rate down, and Google asks bulk senders to hold that rate under 0.10 percent on mail to personal Gmail accounts.

Sources and methodology

Third-party pages below were read on September 13, 2026 and again on September 23, 2026. Vendor pricing pages and provider documentation were read on September 23, 2026. Figures from third-party analyses are attributed in the text. Cost comparisons are our own calculations on those published rates.

  • millionverifier.com
  • usebouncer.com, pricing
  • neverbounce.com, pricing
  • zerobounce.net, email validation pricing
  • support.google.com, answer 14229414
  • techcommunity.microsoft.com, strengthening email ecosystem outlook’s new requirements for high‐volume senders 4399730
  • datatracker.ietf.org, doc rfc9989
  • instantly.ai, blog email list validation upload quality checks
  • lagrowthmachine.com, email verification software 2026
  • emailaddress.ai, blog email bounce rate benchmarks 2026
  • cleanlist.ai, blog 2026 01 22 b2b data decay statistics
  • landbase.com, blog data decay rate statistics
  • https://freelvy.com/pricing

Next in this cluster: how to build a company list from a description, the cold email deliverability checklist, the best AI prospecting tools of 2026, and what data quality costs on a database, in our Apollo pricing breakdown.