ZapBounce vs BounceBan
BounceBan is built around catch-all addresses, and so is this comparison. You're choosing between a vendor that markets a resolution rate for accept-all domains and one that labels them catch_all from a single probe, bills each row once and prints the price on the page.
| ZapBounce | BounceBan | |
|---|---|---|
| Accuracy reporting | Coverage stated: the share of your list with a definite verdict | States a catch-all resolution rate on its own site |
| 1,000 addresses | $5 | See their pricing page |
| 10,000 addresses | $25 | See their pricing page |
| 100,000 addresses | $139 | See their pricing page |
| Free tier | 100 a month, no card | See their pricing page |
| Credit expiry | Never | See their pricing page |
| Billed for unknowns | No | Not stated |
BounceBan prices change, so confirm theirs on their own pricing page. Ours are fixed and published on /pricing.
How BounceBan prices it
BounceBan sells volume tiers either pay-as-you-go or on a monthly plan, one credit per verification, and shows the figures only once the page's script runs. ZapBounce prints every tier as plain text: $5 for 1,000, $25 for 10,000, $139 for 100,000 and $949 for a million.
Why teams pick ZapBounce over BounceBan
What changes when your list runs through ZapBounce instead.
The short version
- Published prices on one page, from $5 for 1,000 to $949 for a million.
- Four fixed results, catch_all among them, with the literal SMTP code on every row.
- Unknown results and duplicate rows are never charged, and the pricing page says so.
- Credits never expire, and 100 free credits arrive every month with no card.
- Our own SMTP check on port 25, closed before DATA, so no message reaches the addresses you check.
Moving off BounceBan
People usually start looking past BounceBan when they try to budget it. The price per credit sits behind a JavaScript calculator, so a finance team can't read a rate off the page, and the catch-all percentage it markets is a claim you have to take on trust.
BounceBan takes a file or an API call, and so does ZapBounce, so moving is mostly repointing one endpoint. Keep your BounceBan export of the catch-all rows: when you re-run them here they come back as catch_all, labeled, and you decide what to do with them.
The hard addresses, and how they come back
Questions people ask about BounceBan
Why is there no BounceBan price on this page?
BounceBan's pricing page shows its figures only after a script runs, and this site quotes a competitor price only when it can be read and dated. Open their page in a browser to see today's rate. ZapBounce's is fixed and public: $5 for 1,000 and $139 for 100,000.
How does ZapBounce handle the catch-all rows BounceBan targets?
ZapBounce sends one probe to a random address at the same domain. If the server accepts it too, the row comes back catch_all with the reason accept_all_domain, billed once, and no message is sent.
Can I test BounceBan's catch-all claim against ZapBounce?
Yes, and it's the fairest test there is. Take 1,000 catch-all rows, send the ones each tool calls deliverable to a small campaign, and count the bounces. ZapBounce's 100 free monthly credits cover the first slice with no card.
Is ZapBounce cheaper than BounceBan?
Ours is $5 for 1,000 and $139 for 100,000, published, with no minimum. Credits never expire, and unknowns and duplicates are never billed, so the rate you see is the rate you pay.
Can I test both before deciding?
Yes, and you should. Run the same sample of a few thousand addresses through each and compare how many came back unresolved. That difference matters more than either accuracy claim.
Load BounceBan's calculator at your volume, then set it beside ZapBounce's printed $139 for 100,000, with unknowns and duplicates never billed.
Run the same sample through us and BounceBan
100 free checks a month, no card, and the unknowns come back labeled.