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.
| Gate applied before sending | Addresses kept | Bounce rate of the kept set | Good addresses thrown away |
|---|---|---|---|
| No verification (baseline) | 455 | 38.5% | 0 |
| BillionVerify: keep 'valid' only | ~405 | 36.3% | 50 of 280 (18%) |
| No2Bounce: 'Deliverable' and not catch-all | ~207 | lower, but 140 of 280 good leads rejected | 140 of 280 (50%) |
| Tool | Real bounces it marked 'valid' | Real bounces it caught |
|---|---|---|
| BillionVerify | 131 of 175 (75%) | 44 of 175 |
| No2Bounce strict | 107 of 175 | 68 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.
- The two tools are not interchangeable: they contradict each other precisely on the addresses that matter (the dead ones).
- The only way to settle the 57 disputed addresses would be a live send on sacrificial infrastructure. We did not run it.
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.
| Tool | Free tier | Annual / volume price | Pay as you go |
|---|---|---|---|
| BillionVerify | 600 credits/month + 20/day without a card | 20,000/year for $96 ($0.0004 per address) | from $0.001 |
| No2Bounce | 100 credits | 10,000 for $17 ($0.0017); 100,000 for $126 ($0.0012); 1M at $0.0007 | $0.001 |
What we concluded
- Neither tool sees the two causes behind most of our bounces: security gateways (Mimecast) that reject new sending domains after accepting the SMTP handshake, and catch-all domains that accept everything.
- The lever that moved our bounce rate was not the verifier: it was a free DNS-level filter on the recipient's MX records plus a per-lead bounce guard on each campaign.
- We kept No2Bounce as the default verifier after this test. It was later replaced by AgentsVerify (see the related measurement from October 2026), which does run the catch-all probe.
What this measurement does not say
- The 455-address set was chosen because it had bounced heavily; it is not a random sample of B2B lists. Absolute bounce rates are inflated, the comparison between tools is what the test measures.
- Addresses were about one month old at the time of re-verification. Some bounces may have been caused by the sending domain's reputation rather than the address itself.
- Single day of testing, one API account per tool. Vendor behavior can change.
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
- AgentsVerify vs No2Bounce vs BillionVerify on the same 455 real bounce outcomes
- Which email verifiers actually detect catch-all domains? The invented-address test
- Cold email bounce rate by recipient security gateway: Mimecast, Sophos, Proofpoint, Microsoft 365, Google
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