A verifier hands back a column of labels, and every label needs a decision before the list goes anywhere near a sending tool. This playbook turns each status into one action.
These rules apply to cold and marketing sends from shared or third-party sending infrastructure, where a provider bounce ceiling applies. Teams on their own dedicated IPs can accept more catch-all and unknown risk, as NeverBounce notes. Verification reads signals from the recipient's mail server without sending an email. It cannot confirm a catch-all mailbox or predict engagement, so it narrows risk rather than removing it.
What Email Verification Statuses Mean
An email verification status is a verifier's reading of an address's format, domain, MX records and SMTP response, and every major verifier, from ZeroBounce to Hunter, sorts those readings into five families, which are valid, invalid, unknown, catch-all or risky, and do-not-mail flags such as role or disposable.
Hunter's documentation describes the method plainly. It checks the address format, the domain, the MX records and the SMTP server, and it does this without sending an email. Every status you see is a summary of what those checks returned. That is why email verification reduces uncertainty but never removes it.
The five families look like this across vendors:
- Valid or deliverable: The mail server accepted the mailbox during the check.
- Invalid or undeliverable: The mailbox, the domain or the syntax failed, and the failure is permanent.
- Unknown: The server gave no definitive answer, often because of greylisting, a timeout or an anti-spam gateway.
- Catch-all, accept-all or risky: The domain accepts any address, so the specific mailbox cannot be confirmed.
- Do-not-mail flags: Role addresses, disposable addresses, spam traps and known complainers, which can appear on top of a valid result.
The scale of each family matters for planning. ZeroBounce's own Email List Decay Report for 2026, which covers the more than 11 billion addresses ZeroBounce processed in 2025, found that only 62% of submitted emails were valid. In the same vendor data, 23% were invalid, more than 9% were catch-all and 0.01% were spam traps. These are ZeroBounce's figures from its own customers' uploads, not an independent study, but they show why a status column is never all green.
Read every status in two layers. The top-level label tells you the family. The sub-status, reason or flag tells you why, and the why decides whether you suppress, hold or re-check.
Valid, Invalid And Unknown Results Explained
Valid, invalid and unknown describe three different server responses, since ZeroBounce defines valid as safe to email yet still subject to bounces from blacklisting or throttling, invalid as an address to delete, and unknown as a check that failed because the server was offline, slow or protected by anti-spam systems.
What the three core statuses mean
| Status | What the server did | Default action |
|---|---|---|
| Valid | Accepted the mailbox | Send |
| Invalid | Rejected mailbox or domain | Suppress permanently |
| Unknown | Gave no definitive answer | Re-verify before sending |
Valid. ZeroBounce describes a valid address as safe to email and says these addresses bounce at under 2%. It still names three causes of bounces on valid addresses, which are IP blacklisting, recipient allowlists and per-domain throttles. A valid result confirms the mailbox exists. It says nothing about whether your message lands in the inbox or gets read.
Invalid. An invalid result is treated as permanent for sending decisions. ZeroBounce's invalid sub-statuses show the range of causes:
- mailbox_not_found, where the mailbox does not exist
- no_dns_entries, where the domain has no usable DNS records
- failed_syntax_check, where the address is malformed
- possible_typo, where the address looks like a misspelling of a real domain
- mailbox_quota_exceeded, does_not_accept_mail and unroutable_ip_address
Delete or suppress invalid addresses, with two exceptions worth a second look:
- possible_typo: The corrected address may be real. Bouncer offers a similar hint with its didYouMean field.
- mailbox_quota_exceeded: A full mailbox is a temporary condition in Verifalia's quality levels, so re-check it later rather than deleting it.
Unknown. An unknown result means the check did not finish with an answer. NeverBounce says its unknown code means the server gave no definitive answer in time, often because of greylisting or a security gateway, and calls it not a negative result. ZeroBounce lists unknown sub-statuses such as greylisted, antispam_system, timeout_exceeded, failed_smtp_connection and mail_server_temporary_error.
The practical difference is simple. Invalid is a fact about the address. Unknown is a fact about the check. That is why invalid goes straight to suppression while unknown goes back for a second pass.
What Catch-All And Accept-All Results Mean
A catch-all or accept-all result describes the recipient's domain rather than the person, because the mail server accepts every address, and NeverBounce's own rule of thumb is that catch-all addresses bounce at about half the rate of the list's invalid addresses.
NeverBounce labels these results "Accept All (Unverifiable)" and stresses that the label is a setting on the recipient's server, not a verdict on the address. Many of these addresses are valid. The verifier simply cannot prove it without sending a message.
Vendors attach different extra signals to help you sort catch-alls:
- Hunter shows a confidence score on accept-all and unknown results, and its FAQ suggests a score above 85% as a guide for accept-all addresses. Hunter does not publish how the score is calculated.
- Bouncer returns a score from 0 to 100 and a toxicity value from 0 to 5, plus an acceptAll domain flag. Bouncer's documentation does not describe the method behind either number.
- ZeroBounce advises segmenting catch-all addresses and expecting some bounces.
Because neither score has a published method, treat a score as a tiebreaker within the catch-all segment, not a verdict that moves an address into your valid list.
The decision rule for catch-all and accept-all results:
- Separate them from valid results before any send.
- Prioritise engaged contacts and recently sourced contacts within the segment.
- Send small, segmented batches and watch bounces after each one.
- Stop the segment when bounces rise toward your provider's ceiling.
Should You Email Role Addresses
Role addresses such as sales@ and info@ are shared inboxes defined in RFC 2142, the IETF list of standard mailbox names, and Constant Contact blocks role addresses that consistently produce high spam complaints, so most cold outreach teams should suppress them even when a verifier returns them as valid.
RFC 2142 defines the standard mailbox names organisations should support for their functions. They include business mailboxes such as INFO, MARKETING, SALES and SUPPORT, network mailboxes such as ABUSE, NOC and SECURITY, and service mailboxes such as POSTMASTER, HOSTMASTER and WEBMASTER. Nobody owns these inboxes personally, so a cold message reaches whoever monitors them.
Constant Contact's policy shows how a sending platform treats the risk. It says role addresses can lead to higher complaint and opt-out rates. It refuses to send to prefixes such as all@, marketing@, sales@, noreply@ and webmaster@. It still mails others, such as info@, support@ and office@, but does not troubleshoot deliverability for any role address, and it recommends importing role addresses as unsubscribed contacts.
The verifier trap is that role addresses often pass. ZeroBounce puts role_based inside its do_not_mail status, flags those addresses as valid, and describes them as strongly linked to spam and abuse reports. Bouncer returns a separate role flag on the account alongside the main status. A list filtered on valid alone will still mail info@ and sales@.
Filter the flag, not the status. The decision rule:
- Cold outreach: Suppress every role address, whatever its status.
- Existing customers or transactional mail: Keep a role address only where no named contact is available.
- Abuse@ and postmaster@: Never mail them for outreach.
How Status Labels Map Across Verification Tools
The five main verifiers use different words for the same server responses, since ZeroBounce and NeverBounce say valid and invalid while Bouncer and Verifalia say deliverable and undeliverable, and they disagree most on catch-all domains, which ZeroBounce can mark valid, NeverBounce marks unverifiable and Verifalia lets each account reclassify.
How five verifiers label the same results
| Tool | Top-level labels | Catch-all label | Unknown handling | Extra signal |
|---|---|---|---|---|
| ZeroBounce | Valid, invalid, catch-all, do_not_mail | accept_all can sit in valid | Unknown, not charged | gold, alternate sub-statuses |
| NeverBounce | Valid, invalid, disposable | Accept All (Unverifiable) | Unknown, re-verify first | Result codes 0 to 4 |
| Bouncer | Deliverable, risky, undeliverable | acceptAll flag, risky | Unknown, with retryAfter | Score and toxicity values |
| Hunter | Valid, invalid, disposable | Accept all, with score | Unknown or Blocked, scored | Separate not-verified state |
| Verifalia | Deliverable, risky, undeliverable | Risky by default, movable | Unknown, inconclusive codes | 40+ codes, custom scheme |
ZeroBounce returns seven top-level labels, which are valid, invalid, catch-all, spamtrap, abuse, do_not_mail and unknown. Its accept_all sub-status sits inside valid for domains on ZeroBounce's accept_all list, flagged to monitor engagement. Role_based sits inside do_not_mail. Its valid sub-statuses also include gold for high-engagement contacts and alternate for likely secondary addresses with low engagement.
NeverBounce returns five results with numeric codes, which are Valid (0), Invalid (1), Disposable (2), Accept All (Unverifiable) (3) and Unknown (4).
Bouncer returns deliverable, risky, undeliverable or unknown, with a reason such as accepted_email, low_deliverability, rejected_email, dns_error or timeout. Flags include acceptAll, disposable and free at domain level, and role, disabled and fullMailbox at account level.
Hunter uses Valid, Invalid, Accept all, Disposable and Unknown or Blocked, with a confidence score on accept-all and unknown results. Bulk rows that were never checked read "Not verified, out of credits" or "Not verified, canceled", which are not the same as Unknown.
Verifalia maps more than 40 status codes into Deliverable, Undeliverable, Risky and Unknown through each account's classification scheme. The default scheme marks ServerIsCatchAll as Risky, and an account can move it to Deliverable. Classification overrides with wildcard expressions apply before the scheme.
The result is that the same address can be valid in one tool and risky in another, because catch-all placement is a vendor choice. Map every tool's labels to your five families before you write rules, and keep the sub-status column, not just the label. If you are still deciding which verifier to use, our comparison of the best email verification tools covers that choice.
An Email Verification Workflow For Every Status
A working email verification workflow gives every status one fixed action before a list is sent, which means suppressing invalid, spam trap and abuse results, filtering role and disposable flags, re-verifying unknowns, test-sending catch-all addresses in small batches and sending only what is left as valid.
Run the steps in this order:
- Dedupe the list before upload, so the export holds one status per address and is easier to audit.
- Run the verifier and export the status plus the sub-status or reason and every flag.
- Suppress invalid, spam trap, abuse, toxic and global_suppression results permanently.
- Suppress disposable and role flags for cold outreach.
- Re-verify unknowns after a delay, as the next section explains.
- Split catch-all and accept-all results into a small test batch.
- Send the remaining valid addresses.
- Write the status and the verification date back to the CRM so nobody re-mails the list blindly.
Once the steps run, every status or flag maps to one action:
One action per status
| Status or flag | Action | Reason |
|---|---|---|
| Valid | Send | Mailbox accepted |
| Invalid | Suppress permanently | Permanent failure |
| Spam trap, abuse, toxic | Suppress permanently | Reputation risk |
| Role or disposable flag | Suppress for cold sends | Complaint risk |
| Unknown | Re-verify | Check did not finish |
| Catch-all or accept-all | Hold for test batch | Mailbox unconfirmed |
| Not verified | Re-run the check | Row never checked |
ZeroBounce's do_not_mail status deserves a careful read in step three. Global_suppression covers known complainers, purchased addresses and litigators, and possible_trap marks a likely spam trap. ZeroBounce skips validation for both, so neither ever becomes valid. Verifalia's MailExchangerIsHoneypot code is its spam trap result, and Verifalia advises removing it.
Permissions And Limits That Change The Results
Some statuses come from how the tool was configured, not from the recipient's server. Three documented limits matter when you build the workflow:
- Bouncer timeouts: Bouncer's real-time verification endpoint has a timeout parameter that defaults to 10 seconds, with a maximum of 30. A check that hits the timeout returns unknown with reason timeout. The default rate limit is 1,000 requests per minute, so high-volume real-time checks need throttling on your side.
- Hunter credits: Hunter labels bulk rows it never checked as "Not verified, out of credits" or "Not verified, canceled". These rows are not unknown results, and treating them as unknown hides a billing gap rather than a server problem.
- Verifalia schemes: A change to Verifalia's classification scheme takes effect only for new verifications. Moving ServerIsCatchAll from Risky to Deliverable does not reclassify a list you already ran.
If you are verifying addresses that came from a finder, the playbook on verifying an address you have just found covers the step before this one.
How To Re-Verify Unknown Results
An unknown result usually means the mail server delayed or blocked the check, through greylisting, a timeout or an anti-spam gateway, so the fix is a second pass after a delay, which ZeroBounce says often validates greylisted addresses and Verifalia builds into its High and Extreme quality levels.
Each vendor gives a different handle on the retry:
- ZeroBounce says greylisted results often validate on resubmission and advises resubmitting large numbers of unknowns. ZeroBounce also claims that about 80% of unknowns are invalid. That is the vendor's own claim, not an independent finding.
- Bouncer returns a retryAfter value when results may come after greylisting, which tells you when to re-run the check.
- Verifalia runs 1 validation pass with 5 seconds of anti-tarpit and greylisting time at Standard, 3 passes with 50 seconds at High and 9 passes with 2 minutes at Extreme.
- NeverBounce advises re-verifying unknowns before sending and treating whatever remains like accept-all.
A Verifalia code such as MailboxTemporarilyUnavailable is a good example of why the retry pays off. Verifalia says it is often greylisting and does not mean the mailbox is missing.
What Each Status Costs In Credits
Most verifiers do not charge for unknown results, as ZeroBounce, Bouncer and Hunter each state in their own documentation, so the real cost of a status rule is in re-checks and quality levels, such as Verifalia charging 2 credits per address at High quality and 4 at Extreme.
The credit rules that drive spend:
- ZeroBounce: One credit per email verified or scored. Unknown results are not charged and are credited back, and subscription credits never expire.
- Bouncer: No charge for duplicated addresses within a list or for unknown results, and verification credits never expire.
- Hunter: 0.5 credit per verified email, in bulk too. A failed verification counts no credit and shows as Unknown, disposable addresses are skipped without a credit, and the same verification counts once per billing period.
- Verifalia: 1, 2 or 4 credits per address at Standard, High or Extreme, and duplicate entries from the second onward use no credits.
- NeverBounce: Pay-as-you-go credits expire 12 months after purchase, so buy close to the volume you will verify.
The decision rule is that re-verifying unknowns costs no extra credits at ZeroBounce, Bouncer and Hunter. At Verifalia, moving a list to a higher quality level doubles or quadruples the per-address cost, so run High or Extreme on the unknowns only, not on the whole file.
Plans and prices for ZeroBounce, Bouncer and NeverBounce:
ZeroBounce pricing
| Plan | Price | Billing | Notes |
|---|---|---|---|
| Freemium | $0 | per month | per credit |
| Pay-As-You-Go | $39 | per month | per credit |
| ZeroBounce ONE | $99 | per month | per credit |
Bouncer Email Verification pricing
| Plan | Price | Billing | Notes |
|---|---|---|---|
| 1000 credits | $8 | one-time | per credit |
| 10000 credits | $60 | one-time | per credit |
| 100000 credits | $400 | one-time | per credit |
| 1000000 credits | $2,000 | one-time | per credit |
| 250000 credits | $750 | one-time | per credit |
| 5000 credits | $35 | one-time | per credit |
| 50000 credits | $250 | one-time | per credit |
| 500000 credits | $1,250 | one-time | per credit |
Bouncer Deliverability Kit pricing
| Plan | Price | Billing | Notes |
|---|---|---|---|
| Starter | $25 | per month | |
| Standard | $125 | per month | |
| Pro | $250 | per month | |
| Enterprise | Custom pricing |
NeverBounce pricing
| Plan | Price | Billing | Notes |
|---|---|---|---|
| Growth | $49 | per month | |
| Enterprise | Custom pricing | per contact | |
| Pay as you go | $8 | one-time | per credit |
How To Measure Whether Your Status Rules Work
Status rules work when each segment's bounce rate stays under your sending provider's ceiling and complaints stay low, and Google tells senders to keep their spam rate below 0.1% and never let it reach 0.3%, the threshold that also governs bulk senders mailing close to 5,000 messages a day to Gmail.
0.1%
Google's ceiling for a healthy spam rate. Bulk senders that pass 0.3% lose eligibility for mitigation until their rate stays below 0.3% for 7 consecutive days.
Current Gmail sender guidelines · Senders to personal Gmail accounts · Source
Measure three numbers after every send, split by the segment each address came from:
- Bounce rate per segment: Valid, the catch-all test batch and re-verified unknowns, each tracked on its own.
- Spam complaint rate: Against Google's 0.1% target and 0.3% limit.
- Unsubscribe rate: A rising rate on one segment points to the wrong audience, not a bad address.
NeverBounce gives a useful reference point for bounces. For senders whose third-party provider requires a bounce rate below 4%, NeverBounce advises mailing accept-all addresses selectively and monitoring bounces. Use your own provider's ceiling wherever it differs.
The decision rules:
- If a catch-all test batch bounces above your provider's ceiling, stop that segment and suppress the rest of it.
- If re-verified unknowns bounce more than valid addresses, move persistent unknowns to suppression instead of the test batch.
- If complaints rise, tighten your role and abuse filters first, since those flags carry the complaint risk.
Verification is one input to deliverability, not the whole of it. Authentication and campaign setup are covered in the guide to setting up your first cold email campaign.
For inbox placement testing after the list is clean, see our comparison of email deliverability tools.
Frequently Asked Questions
Does a valid status guarantee the email reaches the inbox?
No. A valid status does not guarantee inbox placement, because verification only confirms the mail server accepted the mailbox. ZeroBounce notes that valid addresses can still bounce from IP blacklisting, recipient allowlists or sending throttles, and placement also depends on your sender reputation and content.
Should you keep disposable addresses on a B2B list?
No. Disposable addresses are temporary accounts, such as Mailinator inboxes, and they rarely belong to a buyer. NeverBounce marks them do not send, and Hunter says they should not be used for cold outreach and skips them without charging a credit. Suppress them, even when a verifier flags them as valid.
How often should you re-verify a list?
Re-verify any list before each send once it has sat unused. ZeroBounce reports that only 62% of the emails its customers submitted in 2025 were valid, a snapshot of incoming lists rather than a decay rate. Hunter re-verifies saved leads every month on its paid All in One Outreach plans and shows the last verification date.
Sources
Sources
- About role addresses, group addresses and aliases · knowledgebase.constantcontact.com
- RFC 2142: Mailbox Names for Common Services, Roles and Functions · datatracker.ietf.org
- Email sender guidelines FAQ - Gmail Help · support.google.com
- neverbounce.com
- verifalia.com
- verifalia.com
- neverbounce.com
- zerobounce.net
- The Email List Decay Report for 2026 · zerobounce.net

