Home / Outbound Benchmarks / BillionVerify vs No2Bounce

BillionVerify vs No2Bounce: tested against 455 real bounce outcomes

We verified 455 B2B addresses with BillionVerify and No2Bounce, then compared both verdicts with what actually happened when the emails were sent. BillionVerify marked 75% of the real bounces as valid.

Key finding: On 455 addresses with a known delivery outcome (175 bounced, 280 delivered), BillionVerify returned 'valid' for 131 of the 175 addresses that had actually bounced (75%). Filtering on its 'valid' status only lowered the bounce rate from 38.5% to 36.3%. No2Bounce's strict gate caught 68 of 175 bounces but also rejected 140 of the 280 good addresses.
Measured onAugust 20, 2026
Sample455 email addresses with a verified send outcome (175 bounced, 280 delivered), plus a second fresh pool of 300
MethodAddresses taken from B2B pools sent through a sending platform in July 2026; ground truth = per-lead bounce status recorded by the platform. Each address re-verified through both APIs on the same day. Mimecast domains excluded beforehand.
SourceVision Media internal measurement (campaign and API logs)
Test 1: 455 addresses, delivery outcome known
Gate applied before sendingAddresses keptBounce rate of the kept setGood addresses thrown away
No verification (baseline)45538.5%0
BillionVerify: keep 'valid' only~40536.3%50 of 280 (18%)
No2Bounce: 'Deliverable' and not catch-all~207lower, but 140 of 280 good leads rejected140 of 280 (50%)
Where each tool failed
ToolReal bounces it marked 'valid'Real bounces it caught
BillionVerify131 of 175 (75%)44 of 175
No2Bounce strict107 of 17568 of 175

Test 2: a fresh pool of 300 addresses, the two tools disagree on the core job

On a newly sourced pool (300 addresses, No2Bounce verdict two days old), 86 addresses were dead according to No2Bounce. BillionVerify called 57 of them (66%) 'valid, smtp_deliverable' and only 9 'invalid'. In the other direction, on 100 addresses No2Bounce rated 'Deliverable', BillionVerify answered 'unknown' (smtp_blocked, rate_limited, unverifiable) for 51.

Why BillionVerify says 'valid' so often

We sent an invented address (random local part) to 9 domains known to be catch-all, with check_smtp and force_refresh on. BillionVerify returned 'valid, smtp_deliverable, is_catchall=false' for 9 out of 9. A single SMTP '250 OK' is enough for it to call an address valid; it does not run the random-recipient probe that identifies accept-all servers. There is no client-side catch-all setting in its API (only check_smtp and force_refresh exist).

On the 208 addresses that No2Bounce flagged as catch-all in test 1, BillionVerify labeled 9 as 'catchall' (4%) and 161 as 'valid'; those 'valid' addresses bounced at 30%, the same rate as its 'unknown' ones.

Pricing at the time of the test

BillionVerify is roughly 3 to 4 times cheaper at equal volume. On this data it is not more accurate, only cheaper.

ToolFree tierAnnual / volume pricePay as you go
BillionVerify600 credits/month + 20/day without a card20,000/year for $96 ($0.0004 per address)from $0.001
No2Bounce100 credits10,000 for $17 ($0.0017); 100,000 for $126 ($0.0012); 1M at $0.0007$0.001

What we concluded

What this measurement does not say

Questions

Is BillionVerify accurate for B2B cold email lists?

In our test it marked 75% of addresses that really bounced as valid and called invented addresses on catch-all domains valid 9 times out of 9. It is usable on clean opt-in consumer lists, not as the only gate on B2B discovery data.

Is No2Bounce better than BillionVerify?

It caught more real bounces (68 vs 44 of 175) because it flags catch-all domains, but its strict gate also rejected half of the good addresses. It is more conservative, not more precise.

Related measurements

Want this run on your pipeline?

We operate multichannel outbound (cold email, LinkedIn, paid retargeting, newsletters) for B2B companies, and we measure it the way these pages do.

Book a call