Bouncer: email verification for marketing teams at large B2C brands

Email verification for large B2C brands is a different buying question from the one a small marketing team asks: the file is in the hundreds of thousands or millions, nearly all of it on free-mail domains, it grows at the checkout every minute, and once or twice a year the whole history is mailed at once. The tool is therefore judged on three things: how it handles Gmail and Outlook catch-all addresses, whether it can stop bad addresses at the form rather than after, and whether a million-address file can be bought and run without a contract. Bouncer's pages answer with catch-all resolution on Google and Microsoft infrastructure, a form script called Bouncer Shield, and a published ladder to 1,000,000 credits (email-verification and pricing pages, read 4 November 2026).

In Cllimber's 8 September 2026 test, 199 of 957 consumer addresses sat on accept-all domains and Bouncer classed 164 of them deliverable, 31 risky, 2 undeliverable and 2 unknown; on 11 September 2026 four single checks returned a gmail.com suggestion for a gnail.com typo, a disposable flag for a Mailinator address, a rejection for a role address and deliverable for a real Gmail address, each in seconds (email verification software for ecommerce stores). Accuracy was not measured: no control addresses were seeded and no campaign was sent. Bouncer Shield on a live form, the API and AutoClean were not run.

This article covers Gmail catch-all verification, signup form email validation and checkout protection with Bouncer Shield, consumer email list cleaning before a peak send, and what high-volume email verification costs pay as you go.

Who Bouncer fits, and what to weigh

Bouncer fits a brand whose list looks like Cllimber's test file, which was 96.2% free-provider addresses across 62 domains, more than half of them Google-hosted: the catch-all problem is a Gmail and Outlook problem, and Bouncer's stated resolution is specifically on Google and Microsoft infrastructure (email-verification page, read 4 November 2026). It also fits a brand that wants the same engine at three points: Bouncer Shield or the API at the form, bulk verification on the stored file, and AutoClean on the connected sending platform, with results graded by status, reason, score and toxicity rather than valid or invalid. Where that platform is Klaviyo, the write-back and scheduling mechanics are covered in Cllimber's article on email verification for Klaviyo.

What to weigh. Shield is a second subscription in addition to credits, priced on monthly checks, and Cllimber did not install it on a live form. The catch-all figures are counts of what Bouncer returned, not a measure of whether those 164 mailboxes exist; nothing was sent to them. A million-address run was not tested: Cllimber's 957 addresses took 20 seconds, which is not a basis for extrapolation, and Bouncer's own published figure is that a 10,000-address list typically finishes within an hour (email-verification page, read 4 November 2026). And the export presets make the caution trade-off visible but do not make it: the brand decides how many customers it gives up for each tenth of a point. Across all of these, accuracy was not measured: no control addresses were seeded and no campaign was sent.

Hands-on test: 199 catch-all addresses and four single checks

Two parts of Cllimber's September 2026 sessions bear on a consumer brand: the catch-all subset of the 957-address bulk run on 8 September, and four single checks on 11 September that stand in for what a form would meet. Both are logged with times and screenshots in Cllimber's email verification software for ecommerce stores article (published 16 September 2026, updated 4 October 2026).

Cllimber hands-on tests, 8 and 11 September 2026. The single checks were made in the app, which uses the same engine as the API and Bouncer Shield; Shield itself was not run on a live form. Accuracy was not measured: no control addresses were seeded and no campaign was sent.

The catch-all count is the one that scales. On a consumer file where one address in five sits on an accept-all domain, a verifier that parks the whole group as risky hands the brand a suppression decision on 20% of its list; one that resolves them, as Bouncer returned here, leaves a smaller residue. A rule that dropped every catch-all in Cllimber's list would have removed the 164 addresses Bouncer expected to deliver, 17.1% of the whole file. Those are counts of what Bouncer returned: accuracy was not measured, no control addresses were seeded and no campaign was sent.

At the checkout: Bouncer Shield and the typo prompt

Signup form email validation for a brand with a high-traffic checkout has to run without a developer release, and that is what Bouncer Shield is built as. Bouncer's Shield page describes three steps: choose which types of email address and which IPs to block, copy the script and paste it onto the website, and leave it to block undesired addresses automatically; the page says it identifies invalid, malicious or fraudulent addresses at the moment of entry and blocks by IP as well as address (read 4 November 2026). The pricing page lists Shield as a monthly subscription priced on monthly checks, with one shield included, every shield able to run its own domain and configuration, and options for styling, custom CSS and hiding the "Powered by Bouncer" mark; the slider also shows a peak-checks-per-hour figure for each tier. Cllimber did not install Shield on a live form.

What a form would see is what the single checks returned: a mistyped domain came back with a suggested correction, which at a checkout goes back to the shopper before the order is placed, and a throwaway domain came back flagged disposable, which a brand running welcome discounts may choose to block at signup. Both are Cllimber's in-app observations of the engine Shield uses, not a test of Shield.

Before Black Friday: the whole customer history, cut by caution level

Black Friday email list cleaning is the one send where the entire history goes out at once, including addresses collected years ago, and the order of work is to verify the file, look at what came back risky or unknown, and cut segments by caution level before anything is sent. Bouncer's export builder puts a number on each cut. In Cllimber's 8 September 2026 run the six preset positions ran from all 957 addresses at a 4% bounce estimate, to 915 at 1.6%, 910 at 1.3%, 864 at 1.1%, 605 at 0.6% and 601 at 0.6% (email verification software for ecommerce stores). The first 42 addresses removed took the estimate from 4% to 1.6%; the step from position 4 to 5 cost 259 addresses for half a point, almost all of them addresses classed deliverable but excluded on toxicity. Bounce estimates are Bouncer's figures before any send; accuracy was not measured, no control addresses were seeded and no campaign was sent. The arithmetic of that trade-off, and the bounce thresholds sending platforms publish, are set out on Cllimber's reactivating dormant customer databases page.

At the volume a large brand holds, the same cut is made on a file of 500,000 or a million addresses. How the credit ladder behaves at that size, and what Bouncer publishes about how long a large list takes, is covered in Cllimber's article on bulk email verification for lists with 100,000+ contacts.

Tool types compared: standalone verification and in-platform list hygiene

Hygiene built into a brand's sending platform acts on the list that platform already holds, after it has seen a bounce or a complaint. A standalone service such as Bouncer reaches the checkout form through a script, the stored file through a bulk run, and the sending platform through an integration, from one account and one credit pool, before the send rather than after. The cost is one more vendor with the customer file and a second subscription for the form; the gain is that the catch-all and typo decisions are made at entry and before the peak send instead of in the bounce report. The other categories a store's stack is chosen from are covered in Cllimber's software for ecommerce hub.

Pricing and volume tiers

High-volume email verification is bought pay as you go up to a million credits with no contract, and above that by contacting sales. The ladder below is from the Bouncer pricing page, read 4 November 2026. Per-1,000 figures are calculated from the listed totals.

Bouncer pricing page, read 4 November 2026. Credits never expire on demand or on subscription; duplicates within a list and unknown results are not charged; 100 free credits on signup with no card; auto-refill is available. Bouncer Shield is billed separately as a monthly subscription on monthly checks: 1,000 checks $2, 10,000 $20, 250,000 $300, 1,000,000 $1,050; intermediate points sit on a slider. Credits pay for the database and the API, Shield for the forms. No subscription prices for credits, payment methods or VAT treatment are listed.

Related Bouncer articles on Cllimber

• Email verification API for developers
• Email verification for Klaviyo: How to clean lists and protect campaign deliverability
• Enterprise email verification
• Email verification for marketing teams
• Automated CRM email list cleaning
• Bulk email verification for lists with 100,000+ contacts
• GDPR-compliant email verification for European businesses
• email verification software for marketing agencies
• email verification software for ecommerce stores