ZeroBounce: email verification, credits and catch-all checks

Understand the result

Keep the original status and its reason alongside your own sending decision. A valid result is a dated signal, and an unknown result needs a separate policy.

ZeroBounce status codes include temporarily exceeded mailbox quota under invalid. A valid result can also carry an alias or AI-agent descriptor, so it does not prove that a person reads the mailbox.

ZeroBounce’s catch-all FAQ distinguishes a domain indicator from mailbox validity. Its email scoring adds information; it does not prove a mailbox is valid. Some addresses remain unresolved.

For example, retain the original result for a full mailbox instead of treating every invalid address as permanently nonexistent. Record when the check ran, then decide whether a temporary failure deserves another check.

A result alone does not prove permission to contact someone or guarantee inbox placement. Keep your consent record and suppression rules separate from the verification label.

Choose the verification mode

Decide whether a verification email is acceptable before enabling the optional mode. This matters when your test list contains client contacts or your policy prohibits outreach.

ZeroBounce Verify+ is an optional add-on at no extra cost that sends an email to test bounces. Its account-level setting applies to all team members, and owners or administrators can edit it.

ZeroBounce’s bulk guide requires Verify+ and at least ten unresolved catch-all addresses for its second phase. It may take twelve hours; some results can remain catch-all, and resolved valid results can be less reliable.

ZeroBounce’s send-file API guide instead describes more than five catch-all results and defaults the phase-two option to false. Confirm the threshold for your route and version before designing an automated job.

Test standard verification and any optional phase separately. Save the mode with each result so a later comparison does not mix different checks.

Price the credits you will use

Estimate validation and any scoring separately, then check how long the balance lasts for your account. A low initial purchase does not answer the cost of repeated checks.

ZeroBounce billing lists a pay-as-you-go minimum of 2,000 verification credits for $39, checked October 29, 2026. One credit verifies an address; duplicates and unknowns are uncharged.

ZeroBounce’s credit policy charges one credit each for validation and scoring. Accounts created on or before June 1, 2026 retain non-expiring credits; later accounts generally have a two-year clock reset by purchase.

An active ZeroBounce ONE subscription preserves credit validity under that policy. For a later account, ask how the clock applies after the subscription ends before buying a large balance.

For a planning example, validating a list and scoring every address uses twice the credits of validation alone under the documented rules. Actual charges depend on the results and the checks you choose.

Read the guarantee before sending

Treat the guarantee as a conditional remedy for qualifying checks. Check whether your list and sending process meet the terms before relying on it.

ZeroBounce’s accuracy guarantee requires at least 1,000 self-collected opt-in addresses and sending within 72 hours. It also requires valid-file recipients after toxic and disposable addresses are removed, plus a full mailing export and raw SMTP bounce evidence.

ZeroBounce excludes non-address failures. Its payout example conflicts with the stated calculation, so obtain the applicable remedy in writing rather than calculating a refund from that example.

ZeroBounce’s ONE terms describe a separate money-back offer for a first subscription, with a request deadline and usage limits. Ask which terms apply to your purchase; the subscription offer and accuracy guarantee have different conditions.

Run a representative trial

Use a representative cohort and preserve the raw output before applying your CRM policy. A larger classified share alone does not prove accuracy.

Include known temporary failures and catch-all domains where you have permission to use the data. Record the route, time and mode, then compare the resulting fields with your existing suppression rules.

A useful trial also traces a contact through the CRM after import. Check who changes a status and whether a separate workflow is needed to prevent sending; a file export alone does not prove suppression.

The software trial guide helps plan a consistent evaluation. Ask for current terms and verify the settings with the people who will operate the account.

How to compare the alternatives

Consider Bouncer when recurring HubSpot checks and recommendations for a configured workflow matter. Consider Emailable when a filtered list export and a documented no-email verification process fit your workflow.

Bouncer’s HubSpot integration offers AutoClean and a recommendation field that can drive workflows. Check the workflow itself before assuming a recommendation suppresses a contact.

Emailable’s HubSpot guide describes an export to a new list, while Emailable’s FAQ says verification sends no emails to checked recipients. Test the list selection and any downstream suppression.

The ZeroBounce alternatives comparison compares credit rules and migration. The email verification buying guide provides a shared worksheet for the same cohort.

Common questions

Does ZeroBounce resolve every catch-all address?

No. ZeroBounce’s bulk guide says some addresses can remain catch-all after the optional second phase.

Does Verify+ contact recipients?

ZeroBounce Verify+ sends an email to test bounces. Review the account setting before running it.

Do ZeroBounce credits expire?

ZeroBounce’s policy depends on account creation date and subscription status. Check the terms for your account.

Is ZeroBounce the best verifier?

If optional catch-all checks and its result fields fit your process, consider ZeroBounce. Compare the same cohort and workflow before deciding.

Sources and scope

We read the linked vendor documentation on October 29, 2026.

We have not run the product or measured accuracy, support or CRM behavior.