Home / Outbound Benchmarks / AgentsVerify vs No2Bounce vs BillionVerify

AgentsVerify vs No2Bounce vs BillionVerify on the same 455 real bounce outcomes

The same 455-address ground-truth set, re-run through AgentsVerify in October 2026. It keeps 270 of 280 good addresses, really probes catch-all domains, costs 2.7x less than No2Bounce, and still misses bounces caused by security gateways.

Key finding: AgentsVerify's 'valid' gate kept 270 of the 280 addresses that delivered (BillionVerify kept 230, No2Bounce strict kept 140) and brought the bounce rate of the kept set from 38.5% to 32.2%. When it rejects an address, it is right 84% of the time (47 real bounces among 56 rejections). It still labeled 128 of 175 real bounces 'valid', 78 of them on domains behind security gateways that no verifier can see.
Measured onOctober 26, 2026
Sample455 email addresses with a verified send outcome (175 bounced, 280 delivered); 10 invented addresses on catch-all domains; first production run of 290 catch-all addresses
MethodSame ground-truth set as the August test (per-lead bounce status recorded by the sending platform, July 2026 sends). Bulk verification through the AgentsVerify API (POST /verifications/bulk), compared with the stored No2Bounce and BillionVerify verdicts.
SourceVision Media internal measurement (campaign and API logs)
Gate 'keep valid only', same 455 addresses, three tools
ToolGood addresses kept (of 280)Bounce rate of kept setInvented address on 10 catch-all domains
No gate28038.5%n/a
AgentsVerify (Oct 2026)27032.2%10 of 10 'invalid'
BillionVerify (Aug 2026)23036.3%9 of 9 'valid'
No2Bounce strict: Deliverable and not catch-all (Jul 2026)14043.3%flags the domain as catch-all
Price per verified address (list prices at test dates)
ToolPriceNotes
AgentsVerify$0.00045 (100,000 credits for $44.70)500 free credits; 'unknown' and malformed addresses not charged; credits do not expire
No2Bounce$0.0012 to $0.0017100 free credits
BillionVerify$0.0004 (20,000 per year for $96)600 free per month

What AgentsVerify gets right

What it still misses

128 of the 175 real bounces were labeled 'valid'. 78 of those sit on recipient domains whose MX points to a security gateway (Sophos and similar) that rejects mail based on the sender's reputation, after accepting the SMTP conversation. No SMTP-based verifier can observe that. On Google and Microsoft 365 recipients, its 'valid' addresses still bounced at 16 to 19% in this (deliberately difficult) set.

First production run

290 catch-all addresses from a fresh B2B pool (addresses that a first verifier had left undecided) were sent to AgentsVerify: 279 'valid' (96%), 9 'invalid', 2 'catch_all'. A 96% pass rate on catch-all addresses is high enough that we put those leads in separate campaigns to read their bounce rate on its own at day 2 before trusting it at scale.

Decision

After this test we moved all verification to AgentsVerify once remaining No2Bounce credits are used, with the MX gateway filter kept in front of it. The choice is driven by one thing: it decides catch-all addresses instead of discarding half of the good leads, at about 2.7 times lower cost.

What this measurement does not say

Questions

Which email verifier handles catch-all domains?

In our tests AgentsVerify was the only one of the three that correctly rejected invented addresses on accept-all domains (10 of 10). No2Bounce flags the domain as catch-all without deciding; BillionVerify accepts them.

Does a good verifier remove the need for an MX filter?

No. Bounces caused by security gateways (Mimecast, Sophos) are invisible to SMTP verification. We filter those recipient domains with a free DNS lookup before verifying anything.

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