# Email verification software: what a result can tell you

Compare email verification coverage, catch-all results, billing and CRM workflows before choosing a verifier.

Canonical page: https://quillwell.com/guides/email-verification-software/
Updated 2026-10-30
Publisher: Quillwell Guides (https://quillwell.com/guides/about/). Editorial standards: https://quillwell.com/guides/editorial/

## The short answer

- A larger share of classified addresses does not prove that those classifications are accurate.
- Catch-all is a domain setting; an individual mailbox may be resolved or remain uncertain. Keep both fields.
- If your CRM needs ongoing checks, start with a documented workflow and test what happens to existing contacts.
- Compare the same list and verification mode, including unknown results and any messages sent during checking.

## Read the result before counting coverage

Choose a policy for uncertain results before comparing how many addresses each tool classifies. Coverage measures the share given a label; accuracy requires evidence that the label is correct.

[Hunter’s verification FAQ](https://help.hunter.io/en/articles/15899247-email-verification-faqs) distinguishes valid, invalid, accept-all, disposable and unknown results. Hunter says verification cannot guarantee zero bounces, and its confidence score does not change the verdict.

[Bouncer’s terminology](https://docs.usebouncer.com/terminology) separates address status and reason from the domain accept-all flag. Bouncer includes full mailboxes and disposable addresses in risky results, while unknown can mean a timeout or unsupported provider.

[ZeroBounce status codes](https://www.zerobounce.net/docs/email-validation-api-quickstart/v2-status-codes) place a temporarily exceeded mailbox quota under invalid. ZeroBounce also permits alias or AI-agent descriptors on valid results, so validity alone does not prove that a person reads the mailbox.

A catch-all server accepts mail for a domain without necessarily confirming a particular mailbox. [ZeroBounce’s explanation](https://zerobounce.net/docs/frequently-asked-questions/questions-about-our-services) separates that domain indicator from mailbox validity and treats scoring as additional information. Some addresses remain unresolved.

[Emailable’s accept-all guide](https://emailable.com/docs/email-verification/special-email-types/understand-accept-all-verification/) says some addresses can be resolved as deliverable or undeliverable. Emailable leaves unresolved cases as Risky (Accept-All). Preserve the raw result so your own policy can distinguish those cases.

A valid result is a dated signal about an address. It does not prove inbox placement, permission to contact the recipient, or a future delivery outcome. Treat unknown as an unresolved check and decide whether to recheck or hold it.

## Compare billing and controls

Price your actual volume and check the result fields that reach your workflow. The table summarizes documented terms checked October 29, 2026; verify your plan before ordering.

Documented comparisons to check against your needs

| Product | Billing unit | Limit that matters | Control or output |
| --- | --- | --- | --- |
| Bouncer | [PAYG verification credits](https://www.usebouncer.com/pricing/) | [1,000-credit minimum; unknown uncharged](https://www.usebouncer.com/faq/) | [Status and reason; separate accept-all flag](https://docs.usebouncer.com/terminology) |
| Emailable | [One credit per verification](https://emailable.com/docs/manage-your-account/billing/how-credits-work/) | [5,000-credit PAYG minimum; unknown and same-list duplicate copies uncharged](https://emailable.com/docs/manage-your-account/billing/how-credits-work/) | [HubSpot export creates a new list](https://emailable.com/docs/app-integrations/native-integrations/integrating-with-hubspot/) |
| ZeroBounce | [One credit per validation](https://zerobounce.net/docs/frequently-asked-questions/billing-and-payments) | [2,000-credit PAYG minimum; unknown and duplicates uncharged](https://zerobounce.net/docs/frequently-asked-questions/billing-and-payments) | [Optional Verify+ sends a test email](https://zerobounce.net/docs/email-list-validation/verify-plus) |
| Hunter | [0.5 unified credit per verification on All-in-one](https://help.hunter.io/en/articles/1911617-how-do-credits-work-in-hunter) | [Unknown uncharged; bulk uploads still consume credits](https://help.hunter.io/en/articles/15899247-email-verification-faqs) | [API can return a verification date from an earlier check](https://hunter.io/api-documentation) |
| Findymail | [One verifier credit per API request on credit plans](https://app.findymail.com/docs/) | [Charged regardless of result; usage plans use shared limits](https://app.findymail.com/docs/) | [Bounce claim requires actual bounce evidence](https://help.findymail.com/en/article/how-does-the-bounce-guarantee-works-c2we1w/) |

Source: [Bouncer: Email verification pricing](https://www.usebouncer.com/pricing/), [Emailable: Credit exceptions and same-list deduplication](https://emailable.com/docs/manage-your-account/billing/how-credits-work/), [ZeroBounce: Billing and payments FAQ](https://zerobounce.net/docs/frequently-asked-questions/billing-and-payments)

[Bouncer pricing](https://www.usebouncer.com/pricing/) lists pay-as-you-go verification credits with a 1,000-credit minimum. Bouncer sells its Deliverability Kit separately for placement and authentication tests.

[Emailable’s credit rules](https://emailable.com/docs/manage-your-account/billing/how-credits-work/) make unknown results and duplicate copies within the same list free. Emailable’s minimum PAYG purchase is 5,000 credits. That same-list rule should not be assumed to cover repeats across separate uploads.

[ZeroBounce billing](https://zerobounce.net/docs/frequently-asked-questions/billing-and-payments) lists a 2,000-credit minimum at $39 for pay-as-you-go. [ZeroBounce’s expiry policy](https://www.zerobounce.net/docs/frequently-asked-questions/questions-about-our-services/do-email-validation-credits-expire) says 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 ONE subscription preserves validity.

[Hunter’s credit guide](https://help.hunter.io/en/articles/1911617-how-do-credits-work-in-hunter) assigns 0.5 unified credits to a verification on All-in-one. Hunter uses separate search and verification pools on Data Platform; bulk uploads still consume credits.

[Findymail API documentation](https://app.findymail.com/docs/) says credit-plan verifier requests cost one verifier credit regardless of result. Findymail usage plans instead have shared usage limits, so request the capacity and endpoint limits for your workload.

For a hypothetical small list, compare the minimum purchase with the expected repeat checks. Record whether duplicates and unknowns consume credits. A low per-check rate can leave unused credits whose expiry matters.

## Compare equivalent checks

Run the same permitted cohort through each candidate and record the mode before interpreting the results. A higher classified share can reflect fewer abstentions rather than more correct answers.

Use known outcomes where possible and keep unresolved results in the denominator. Record false positives and false negatives separately. If ground truth is incomplete, report that gap instead of declaring a winner.

[Cllimber’s Bouncer article](https://cllimber.com/bouncer-email-verification-software-for-ecommerce-stores/) reports classifications from a consumer list in a paid partnership. Cllimber explicitly did not measure classification accuracy or campaign bounces. Its raw export was not audited for this guide.

[ZeroBounce’s benchmark](https://www.zerobounce.net/benchmark) is vendor-run and uses agreement or engineer adjudication to confirm ground truth. ZeroBounce counts unknown and catch-all separately while they reduce its headline accuracy. Its method cannot be combined with Cllimber’s classifications as an independent ranking.

[Bouncer’s integration guidance](https://docs.usebouncer.com/integration-guidelines) says real-time checks can return more unknowns than batch checks. Bouncer batch and synchronous modes retain a 24-hour cache and can return partial results before the queue finishes.

[Hunter’s API documentation](https://hunter.io/api-documentation) says a verification response can reuse a check up to a month old. Hunter returns a verification date, so record that date separately from the request time.

[ZeroBounce Verify+ documentation](https://zerobounce.net/docs/email-list-validation/verify-plus) says the optional mode sends an email to test bounces. [Emailable’s FAQ](https://emailable.com/faq/) says its verification sends no emails. Decide whether a recipient message is permitted before choosing a test mode.

[ZeroBounce’s bulk guide](https://zerobounce.net/docs/email-list-validation/catch-all-email-validation) requires Verify+ and at least ten unresolved catch-all addresses for its second phase. [ZeroBounce’s send-file API guide](https://www.zerobounce.net/docs/email-validation-api-quickstart/v2-send-file) instead specifies more than five and defaults the phase off. Confirm the threshold for your route and allow time for completion.

## Read the guarantee against your list

A guarantee is a conditional remedy for particular failures. Check your list source and send timing before giving the promise weight in a purchase.

[Emailable’s guarantee](https://emailable.com/guarantee/) requires at least 1,000 unique self-collected opt-in addresses and deliverable verdicts. Emailable requires sending within 24 hours and reporting a discrepancy within 72 hours. It excludes reputation and server failures, and refunds qualifying checks.

[ZeroBounce’s accuracy guarantee](https://www.zerobounce.net/docs/email-list-validation/the-zb-guarantee) requires at least 1,000 self-collected opt-in addresses and sending within 72 hours. ZeroBounce requires the valid file after removing toxic and disposable addresses, plus a full mailing export and raw SMTP bounce evidence. Its payout example is inconsistent, so request the calculation.

[ZeroBounce’s ONE terms](https://www.zerobounce.net/terms-of-use) describe a separate first-subscription money-back offer with usage limits. Do not treat that offer as the accuracy guarantee.

[Bouncer’s guarantee](https://www.usebouncer.com/bouncer-guarantee/) offers a refund or credit for an individual deliverable check that objectively bounces within 72 hours, excluding spam and soft bounces. [Bouncer’s older cancellation terms](https://www.usebouncer.com/terms-and-conditions/) say purchases are non-refundable. Ask how the specific promise is processed and when a claim must be submitted.

[Findymail’s guarantee](https://help.findymail.com/en/article/how-does-the-bounce-guarantee-works-c2we1w/) requires at least 1,000 verified B2B addresses sent within 48 hours. Findymail reviews claims above its 5% invalid-address bounce threshold individually; claims must arrive within 30 days. Another verifier’s disagreement alone is insufficient evidence.

For a hypothetical small purchased list, the self-collected opt-in and minimum-size conditions matter immediately. Do not assume a headline percentage applies. The inspected Hunter sources did not confirm a comparable accuracy payout; ask about current terms.

## Make the CRM act on the result

A verification result only changes a campaign if the campaign or a configured workflow uses it. Decide who owns that rule and what happens when a result changes.

[Emailable’s HubSpot integration](https://emailable.com/docs/app-integrations/native-integrations/integrating-with-hubspot/) exports verified contacts into a new list. Emailable’s Maximum Reach includes deliverable, risky and unknown results; Maximum Deliverability includes only deliverable. Removing the integration leaves previously transmitted HubSpot data in place.

[Bouncer’s HubSpot integration](https://www.usebouncer.com/integrations/hubspot/) describes an initial list check, hourly checks for new contacts and a chosen recheck interval for existing contacts. Bouncer’s recommendation field can drive a configured HubSpot workflow. A recommendation alone does not prove that another list or campaign has changed.

Suppose a contact receives a risky result while already in an active marketing list. Identify the field your workflow reads and test whether that contact remains eligible. Set the intended outcome with your team; a new verification list alone does not answer the question.

[Emailable’s migration mapping](https://emailable.com/migrate/zerobounce/) has no direct equivalent for some ZeroBounce suppression categories. Keep the original source and reason alongside any mapped status, then check existing CRM rules before switching.

Save the verification timestamp and raw output before replacing a provider. Retain the rule that produced each suppression decision. Ask whether the export contains the fields needed to reconstruct that rule after the account closes.

## Trial and workflow worksheet

Use the same isolated fixtures for each candidate and keep campaigns inactive. Record an observed result separately from a vendor promise.