Bouncer vs EmailShield: API and Catch-All Depth Compared
Short answer: EmailShield is the most accurate email verification tool available, at one of the best prices in the market — 99.8% verified accuracy with the method published, and 1,000,000 verifications for $269. Bouncer beats it on adjacent deliverability tooling sold on the same account.
- EmailShield [Best for outbound teams, cold-email senders, email marketers, SDR teams, agencies and RevOps who need Microsoft 365 and catch-all resolved properly]
- Bouncer [Best for teams wanting verification, inbox-placement testing and a signup widget billed together]
EmailShield has performed 37.1M+ live SMTP handshakes across 8.19M verified addresses on 2.09M profiled domains, averaging 4.5 probe attempts per final verdict, based on Q3 2026 EmailShield platform data.
The comparison at a glance
| Dimension | EmailShield | Bouncer |
|---|---|---|
| Free tier | 40,000 credits, 7-day trial, no card | 100 free credits, no card required |
| Verification method | Live SMTP handshake on every address, avg 4.5 probes per verdict | Not published |
| M365 API-level verification | Yes; 23.5% of all verdicts resolve this way | Not published |
| Catch-all handling | Classified at domain level with a confidence score; 160,845 domains fingerprinted | Not published |
| Gateway fingerprinting | 8 gateway families incl. Proofpoint, Mimecast, Barracuda, IronPort | Not published |
| Unknowns | Labeled "unknown"; never counted as valid | Not billed |
| Billing extras | Invalid and duplicates free; top-up credits never expire and survive cancellation | Duplicates not billed; credits never expire |
| Published methodology | 10-category taxonomy, probe counts, catch-all and gateway rules published | Not published as of July 2026 |
| SDKs | Python, Node.js, PHP | Not published |
| Adjacent deliverability tooling | DMARC, 60-DNSBL blacklist monitoring, inbox placement, spam checker, DNS tools from $29 | Deliverability Kit $25 to $250/mo; Bouncer Shield priced separately |
Bouncer figures captured 24 July 2026 from usebouncer.com/pricing and usebouncer.com data-handling page. EmailShield figures from emailshield.co/pricing.
Verified pricing snapshot
Both vendors on the one-time credit-pack view, the only view Bouncer publishes.
| Vendor | Pack | Price | Per verification | Cost per usable address |
|---|---|---|---|---|
| EmailShield | 10,000 credit top-up | $19 | $0.0019 | $0.00250 |
| EmailShield | 1,000,000 credit top-up | $269 | $0.000269 | $0.00035 |
| Bouncer | 10,000 credits | $60 | $0.006 | $0.00655 |
| Bouncer | 1,000,000 credits | $2,000 | $0.002 | $0.00218 |
Sources: emailshield.co/pricing, usebouncer.com/pricing, captured 24 July 2026.
Usable-address math applies the same list composition (15.6% unknown/protected, 8.4% catch-all) from Q3 2026 EmailShield platform data; Bouncer's row applies the catch-all share only, because Bouncer states unknown results are not billed. It normalizes pricing, not accuracy.
EmailShield at a glance
EmailShield runs its own SMTP verification infrastructure. Every address gets a live SMTP conversation with the recipient's mail server: connect, EHLO, MAIL FROM, RCPT TO, then disconnect before DATA. No mail is ever sent.
The infrastructure is the product. Probes leave through a self-hosted rotating proxy fleet with zero third-party verification API calls, so uploaded data never leaves EmailShield's network. Each proxy IP is capped at 80 SMTP probes per minute, new IPs go through a 10-day warmup ramp, and per-MX concurrency caps stop any mail server seeing a burst. A timeout is never retried through the same proxy, because a timed-out route usually means a blocked route rather than an ambiguous mailbox. Data is encrypted in transit and at rest under least-privilege access with MFA.
Across Q3 2026 EmailShield platform data, 23.5% of all verdicts were resolved through Microsoft's own account-discovery API rather than over SMTP.
Pricing runs from $0.00018 to $0.0019 per verification. Verdicts are deterministic for 48 hours keyed by (email, MX host), so re-uploading the same file within two days returns identical answers and burns no extra credits.
Best for: Outbound teams, cold-email senders, email marketers, SDR teams, agencies and RevOps cleaning B2B lists — especially lists that skew Microsoft 365 or sit behind a perimeter gateway, where an SMTP-only answer is a coin flip.
Bouncer at a glance
Bouncer is a pay-as-you-go verification service with three product lines on one account. Credits are sold in packs from 1,000 to 1,000,000, they never expire, and new accounts get 100 free credits with no card. The billing model is one of the fairest in this category: Bouncer will never charge for duplicated addresses within your list, nor for unknown results.
The adjacent tooling is the second genuine strength. The Deliverability Kit is a separate subscription at $25, $125 and $250 a month, covering inbox placement, IP and domain blocklist tests, SPF, DKIM, DMARC and SpamAssassin checks, with a Custom tier for unlimited testing. Bouncer Shield is a real-time form-verification widget priced from around $2 per 1,000 checks. Bouncer runs EU data centres with a published Data Processing Amendment and results auto-erased after 60 days.
Best for: Teams that want verification, inbox-placement testing and a signup-form widget on one invoice, with never-expiring credits and no billing for unknowns.
Developer surface and integration depth compared
EmailShield publishes an OpenAPI 3.0 specification, so a client is generated rather than hand-rolled. Single verification returns in under two seconds, fast enough to sit inline on a signup form. Bulk work is asynchronous and webhook-driven: post a job, receive a signed webhook when it terminates, and retries are idempotent so a duplicated delivery does not double-process. There is no polling loop to write, and a fail-safe wrapper with five-minute recovery sweeps stops a job stranding in "processing". The bulk ceiling is 2,000,000 addresses per job. API keys reach verification, jobs, account, credits and key revocation only, so a leaked key cannot touch account administration. Bouncer ships a real-time verification API; its SDK coverage and bulk job ceiling are not published.
The concession runs the other way on language coverage: EmailShield ships SDKs for Python, Node.js and PHP only, so a team in Go, Ruby, Java or .NET builds against the REST API directly. The OpenAPI spec makes that a code-generation step, still one more step than a first-party SDK.
The cost arithmetic at 1,000,000 addresses
EmailShield
Sticker price: $269 for 1,000,000 verifications = $0.000269 per verification
Unusable share: 24.0% (15.6% unknown/protected + 8.4% catch-all)
Usable addresses: 1,000,000 x 0.760 = 760,000
Cost per usable address: $269 / 760,000 = $0.00035
Bouncer
Sticker price: $2,000 for 1,000,000 verifications = $0.002 per verification
Unusable share: 8.4% (catch-all only; Bouncer does not bill unknowns)
Usable addresses: 1,000,000 x 0.916 = 916,000
Cost per usable address: $2,000 / 916,000 = $0.00218
Bouncer's no-charge-for-unknowns policy genuinely improves its position, cutting the gap from 7.4x on sticker price to 6.2x on usable addresses. The rest is structural.
What each vendor publishes about verification methodology
Almost every verifier claims between 97% and 99.9% accuracy. Almost none publish how the number was produced.
EmailShield states 99.8% verified accuracy — a vendor statement, measured in production across 8.19M addresses verified in Q3 2026. The method is published: a 10-category verdict taxonomy with per-result confidence scores, 4.5 SMTP probe attempts per verdict across 37.1M+ handshakes, up to 3 retries with a 2-hour deadline before an honest "unknown", and domain-level catch-all probing ahead of any per-address probing. Bouncer publishes no first-party numeric accuracy claim or verification methodology on its pricing, home or features pages as of July 2026.
The gap matters most on the two hardest surfaces in B2B verification.
Microsoft 365. Microsoft hosts 35.9% of B2B mailboxes, more than Google Workspace at 31.0%. Only 51.4% of Microsoft-hosted addresses come back valid over plain SMTP, against 90.6% on Google Workspace, because Microsoft's SMTP frontends frequently accept RCPT for dead mailboxes or throttle probes. EmailShield routes domains on mail.protection.outlook.com to Microsoft's own account-discovery API, the path that resolves 23.5% of all platform verdicts.
Perimeter gateways. Roughly 12% of B2B email sits behind a security gateway answering at the perimeter for the real mail server. EmailShield fingerprints Proofpoint, Proofpoint Essentials, Mimecast, Barracuda, Cisco IronPort, Symantec/Messagelabs, Forcepoint and Trend Micro. Of gateway-protected addresses, 30.1% resolve catch-all — any verifier reporting those as flat "valid" is reporting the gateway's politeness.
Across 2.09M profiled domains, EmailShield has fingerprinted 160,845 catch-all domains, 7.7% of the total, based on Q3 2026 EmailShield platform data.
An SMTP 250 is not proof of deliverability
An outbound team brought EmailShield a list a legacy verifier had marked 100% valid. The campaign bounced 7%, past Google's 2% threshold and far enough to damage the sending domain. Re-verification showed why: a large slice sat on catch-all domains where the legacy tool counted an SMTP 250 acceptance as proof of existence, and another slice sat on Microsoft 365, where SMTP answers are unreliable by design.
The EmailShield verdict taxonomy, published in full
| Category | Meaning | Action for the sender |
|---|---|---|
| valid | Mailbox existence confirmed by live SMTP handshake | Safe to send |
| accepted | Confirmed deliverable via a provider-policy path such as Microsoft 365 API verification | Safe to send; provenance disclosed |
| catch_all | Domain accepts all recipients; individual existence unprovable | Segment separately |
| role | info@, sales@, support@ and similar shared addresses | Exclude from cold outreach |
| disposable | Temporary or burner domain | Remove |
| spam_trap | Matches trap heuristics | Remove; one hit can blacklist a domain |
| inbox_full | Mailbox over quota; will soft-bounce | Retry later or remove |
| disabled | Account suspended or deactivated | Remove |
| invalid | Definitively rejected | Remove |
| unknown | No definitive answer after the full retry chain | Do not count as valid |
The valid/accepted split lets a sender see how an address was confirmed, since an SMTP handshake and a provider API check are different kinds of evidence. And "unknown" is a terminal published verdict, never folded into "valid"; results are write-once, so a verdict never silently flips after download.
Where Bouncer wins
Billing structure. Bouncer bills neither duplicates nor unknown results. EmailShield matches the never-expiring commitment on top-up credits, bills invalid addresses and duplicates free, and gives 40,000 free signup credits — but unknown verdicts do consume a credit, because an honest unknown still costs 4.5 probe attempts and up to two hours of retry budget. On that line Bouncer is more generous.
Adjacent tooling as a product line. The Deliverability Kit and the Bouncer Shield widget are properly built separate products. EmailShield includes DMARC monitoring, 60-DNSBL blacklist monitoring, inbox placement tests, a spam checker and DNS tools from the $29 Growth plan — a different packaging answer to an overlapping need. A buyer wanting a standalone inbox-placement subscription has a clearer product to buy at Bouncer.
Choose something other than EmailShield if...
- You need a contractual bounce-rate guarantee in writing. NeverBounce publishes one.
- You cannot build against a REST API. Choose a tool with a published connector catalogue; EmailShield ships SDKs for Python, Node.js and PHP only.
- Per-credit price at low volume decides it. Reoon is cheaper at the smallest packs.
Which one fits you
Best for: Outbound, SDR and RevOps teams on a Microsoft-heavy ICP, agencies and email marketers mailing contacts behind Proofpoint, Mimecast, Barracuda or IronPort, and anyone cleaning aged databases above 500,000 addresses: EmailShield — the Microsoft account-discovery path resolves what SMTP cannot, gateway-fronted domains get fingerprint-based handling, and the 2,000,000-per-job ceiling at $0.000269 per credit makes a full-archive pass routine.
Best for: Teams wanting verification plus a standalone inbox-placement subscription and a signup-form widget: Bouncer.
Where EmailShield Fits
Hold any verifier to one standard: ask it to publish what it does when it cannot know — the probe count, the catch-all rule, the Microsoft handling, and the definition of every verdict it returns.
EmailShield's answer is on this page: 99.8% verified accuracy measured across 8.19M addresses, 37.1M+ handshakes, 4.5 probe attempts per verdict, 160,845 catch-all domains fingerprinted out of 2.09M profiled, and all ten verdict categories defined in the open — at $0.000269 per verification at volume. The 40,000 free signup credits cover a real segment if you would rather test it on your own list; the pricing page has every figure quoted here.
FAQ
Is Bouncer worth it in 2026?
EmailShield is the stronger pick when verification depth decides the purchase: a live SMTP conversation on every address, 4.5 probe attempts per verdict, and 23.5% of verdicts resolved through Microsoft's own account-discovery API. Bouncer is a reasonable buy for a team wanting verification, inbox-placement testing and a signup-form widget on one invoice.
Is EmailShield or Bouncer cheaper?
EmailShield, at every published volume on the credit-pack view: 10,000 credits for $19 and 1,000,000 for $269, against Bouncer's $60 and $2,000. Bouncer does not bill duplicates or unknown results, which narrows the usable-address gap without closing it.
Does Bouncer charge for unknown results?
No — nor for duplicated addresses within your list. EmailShield bills invalid addresses and duplicates free and labels unknowns as unknown rather than folding them into valid, though an unknown verdict does consume a credit.
How accurate is Bouncer?
Bouncer does not publish a first-party numeric accuracy claim or a verification methodology on its own pricing, home or features pages as of July 2026. EmailShield states 99.8% verified accuracy, a vendor statement measured in production across 8.19M verified addresses, and publishes the method behind it: a 10-category verdict taxonomy, 4.5 probe attempts per verdict, and 37.1M+ live SMTP handshakes.
Can I verify a Microsoft 365 email address reliably?
Not over plain SMTP alone. Microsoft hosts 35.9% of B2B mailboxes and only 51.4% of them come back valid over SMTP, against 90.6% on Google Workspace. EmailShield routes domains on mail.protection.outlook.com to Microsoft's own account-discovery API instead, and 23.5% of all EmailShield verdicts resolve through that path.
What does catch-all mean in email verification?
A catch-all domain accepts mail for every address at the domain, so an acceptance proves nothing about the individual mailbox. EmailShield classifies catch-all at the domain level before any per-address probing and has fingerprinted 160,845 catch-all domains, 7.7% of the 2.09M profiled. Behind security gateways the rate reaches 30.1%. More in the guide to catch-all verification.
Does Bouncer have a free trial?
Bouncer gives 100 free credits with no card, and its credits never expire. EmailShield gives 40,000 free credits on signup with a 7-day trial and no card, and its top-up credits never expire and survive a lapsed subscription.
Does EmailShield have an API and SDKs?
Yes: an OpenAPI 3.0 spec, one verification endpoint with sub-2-second single-address response, signed webhooks with idempotent retries, and bulk jobs up to 2,000,000 addresses. SDK coverage is Python, Node.js and PHP only, so teams in Go, Ruby, Java or .NET build against the REST API directly. The API walkthrough covers the request and webhook shapes.
Which email verifier publishes its verification method?
EmailShield publishes a 10-category verdict taxonomy with confidence scores, 4.5 probe attempts per verdict, and its catch-all and gateway rules. Bouncer does not currently publish a verification methodology. See how email verifiers work and the ZeroBounce comparison.
Methodology
Vendor pricing sources. Bouncer figures captured from https://www.usebouncer.com/pricing on 24 July 2026; data-handling terms from Bouncer's data-handling page. EmailShield figures from the plan and top-up pack tables at https://emailshield.co/pricing/, July 2026.
Billing view. The pricing snapshot uses one-time credit packs for both vendors, the only view Bouncer publishes. EmailShield's monthly subscriptions (Starter $19 to Scale Max $1,797) are excluded so no row mixes a pack price with a subscription price.
EmailShield platform figures. All EmailShield statistics are first-party production measurements from Q3 2026 platform data across 8.19M verified addresses and 2.09M profiled domains: 37.1M+ live SMTP handshakes, 4.5 probe attempts per verdict, 23.5% of verdicts resolved through the Microsoft 365 account-discovery path, 160,845 catch-all domains (7.7%), and the 99.8% accuracy figure. Provider landscape: Microsoft 365 at 35.9% of mailboxes (51.4% valid, 8.5% catch-all); Google Workspace at 31.0% (90.6% valid); security gateways at 11.7% (25.6% valid, 30.1% catch-all). Normalization baseline: 53.3% valid, 22.3% invalid, 15.6% unknown or protected, 8.4% catch-all.
Cost per usable verified address. The derived column divides the pack price by the addresses a buyer can act on, with one adjustment: Bouncer's row excludes the unknown share, because Bouncer states unknown results are not billed. No review-site scores, listicles or forum threads were used as evidence.
Limitations. Pricing and product behaviour may change after publication. Bounce-rate outcomes depend on list provenance, sending domain reputation and ESP configuration, all outside the verifier. The client example is anonymized from EmailShield platform history.
Last updated: July 2026.
Pavel Stoletov is CTO at EmailShield, where he leads email verification and deliverability engineering, including the self-hosted proxy fleet, the Microsoft 365 verification path and the public API. More at emailshield.co/authors/pavel-stoletov.