NeverBounce catch-all detection: what it does and what it does not
10 min read · Published April 2026
NeverBounce flags catch-all domains with an "accept_all" status. Their recommendation? Do not send to those addresses. That is technically the safe move. But when 30-40% of your B2B leads are on catch-all domains, "do not send" is not a strategy. It is a pipeline killer.
Key Takeaways
- ▸ NeverBounce returns "accept_all" for catch-all domains and recommends not sending to them
- ▸ Following that recommendation means losing 30-40% of your B2B pipeline
- ▸ NeverBounce has no post-send monitoring, auto-pause, or risk distribution for catch-all leads
- ▸ The practical approach: use NeverBounce for pre-send filtering, then layer Superkabe for catch-all protection during and after sending
Table of Contents
How NeverBounce handles catch-all domains
NeverBounce uses SMTP probing to verify email addresses. For each address, it connects to the recipient's mail server and checks whether the server would accept the email. On a standard domain, this works well. The server says yes or no, and NeverBounce returns "valid" or "invalid."
Catch-all domains break this model. The server says yes to everything. It accepts emails to real employees, former employees, typos, and completely fabricated addresses. NeverBounce detects this by probing with a fake address. If the server accepts the fake address, NeverBounce labels the domain as "accept_all."
NeverBounce catch-all classification
- ▸ Status label: "accept_all" (separate from valid, invalid, disposable, and unknown)
- ▸ Official recommendation: Do not send to accept_all addresses
- ▸ No risk differentiation: All accept_all addresses get the same label. No scoring, no confidence level, no distinction between likely-real and likely-fake
- ▸ Separate from "unknown": accept_all is a definitive classification. NeverBounce confirmed the domain accepts everything. Unknown means it could not determine the status
NeverBounce is transparent about this limitation. They do not pretend they can verify individual addresses on catch-all domains. The accept_all label is honest. The recommendation not to send is conservative. But that conservatism comes at a cost most outbound teams cannot afford.
What NeverBounce does well
NeverBounce has built a solid verification product with real strengths. Before talking about gaps, it is worth recognizing where the tool delivers.
NeverBounce strengths
- ▸ Fast bulk processing: Handles large lists quickly. Upload a 50,000-email CSV and get results back in minutes, not hours
- ▸ Reliable real-time API: The API is well-documented and fast. Good for teams integrating verification into automated workflows
- ▸ Good accuracy: Around 96-97% detection rate for invalid addresses on non-catch-all domains. Not quite ZeroBounce level, but close
- ▸ Competitive pricing: Roughly $0.80 per 1,000 at volume. Cheaper than ZeroBounce ($3-4 per 1,000), more expensive than MillionVerifier ($0.50 per 1,000)
- ▸ Good integrations: Native connections with HubSpot, Zapier, and several other platforms. Makes it easy to plug into existing workflows
For pre-send list cleaning, NeverBounce is a dependable choice. It filters out the obvious invalids, catches disposable email addresses, and processes lists fast enough for high-volume teams. If every domain on your list were a standard non-catch-all domain, NeverBounce would give you clean, actionable results.
The "don't send" problem
NeverBounce recommends not sending to accept_all addresses. On paper, that is the safe move. In practice, it is not realistic for most outbound teams.
Between 30-40% of B2B email addresses sit on catch-all domains. Enterprise companies, government agencies, healthcare systems, financial institutions, law firms. These are not fringe targets. For many sales teams, they are the primary ICP.
Run the math on a real outbound operation. You enrich 1,000 leads through Clay at $0.03 each. That is $30 in enrichment costs. NeverBounce verification adds another $0.80. Your total list investment is about $31. NeverBounce returns 350 of those leads as accept_all. If you follow the recommendation and skip them, you just wrote off $10.50 in enrichment costs and lost access to 350 potential conversations.
Scale that to 10,000 leads per month. You are discarding 3,500 leads and $105 in enrichment costs monthly. Over a year, that is 42,000 leads and $1,260 in wasted enrichment. And the real cost is not the money. It is the pipeline you never built because your VP of Sales at a Fortune 500 company happened to be on a catch-all domain.
We covered the full scope of the catch-all challenge in our catch-all domains deep dive. The short version: you need a way to send to catch-all leads without destroying your infrastructure. "Don't send" is not that way.
The gap after verification
Suppose you ignore NeverBounce's recommendation and send to accept_all leads anyway. Now you are in unprotected territory. NeverBounce flagged the risk. You accepted it. What happens next is entirely on you.
What NeverBounce cannot do after verification
- ▸ No post-send monitoring: NeverBounce does not watch your bounce rates. If catch-all leads bounce at 8%, you will not hear about it from NeverBounce
- ▸ No infrastructure protection: If bounces from catch-all leads push a mailbox past its threshold, nothing stops the sending automatically
- ▸ No risk distribution: NeverBounce does not know which mailbox will send to which lead. It cannot spread catch-all risk across your infrastructure
- ▸ No domain intelligence: If a particular catch-all domain has historically caused bounces, NeverBounce has no memory of that. It checks the same domain fresh each time
- ▸ No healing: If a mailbox or domain takes damage from catch-all bounces, there is no recovery system. You are on your own figuring out when and how to resume sending
NeverBounce was not designed to do any of this. It is a verification tool. Verification answers: "Is this address deliverable?" Infrastructure protection answers: "Is it safe to send from this mailbox right now, and what should happen if things go wrong?" These are different questions that require different systems. For more on this distinction, see our validation vs verification breakdown.
The practical approach for NeverBounce users
The goal is not to replace NeverBounce. NeverBounce does its job well. The goal is to add the protection layer that makes it safe to send to those accept_all leads instead of discarding them.
Two-layer approach
Layer 1: NeverBounce (pre-send filter)
Run your list through NeverBounce first. Remove all "invalid" and "disposable" results. These are definite bad addresses that should never reach a sender. NeverBounce catches these reliably. Keep the "valid" results. And keep the "accept_all" results too — those are the leads you are about to protect rather than discard.
Layer 2: Superkabe (send-time protection + post-send monitoring)
Route all remaining leads (valid + accept_all) through Superkabe. For accept_all leads, Superkabe detects catch-all status at the domain level and caches it in the DomainInsight table. The lead gets a validation score penalty. Routing caps limit each mailbox to a maximum of 2 risky leads per 60 sends. After sending, Superkabe monitors bounce rates on a 60-second cycle and auto-pauses any mailbox that crosses the threshold.
This combination gives you the best of both worlds. NeverBounce removes the definite junk before it reaches your infrastructure. Superkabe manages the uncertain (catch-all) leads with risk distribution and real-time monitoring. You send to catch-all leads. But you do it with guardrails.
If you already use NeverBounce and want to keep it, this is the cleanest path. If you want to consolidate tools, Superkabe includes MillionVerifier in its built-in validation pipeline, so you could drop NeverBounce entirely and let Superkabe handle both verification and protection. Either setup works. For the full list of verification options, see our best email validation tools guide.
What NeverBounce checks vs what Superkabe adds
| Capability | NeverBounce | Superkabe |
|---|---|---|
| Invalid email detection | Yes (~97% accuracy) | Yes (via MillionVerifier) |
| Catch-all detection | Yes (accept_all label) | Yes (detects + caches per domain) |
| Catch-all recommendation | Don't send | Send with risk caps |
| Risk scoring | No | 0-100 validation score |
| Domain-level intelligence | No (checks fresh each time) | DomainInsight cache |
| Per-mailbox risk caps | No | Max 2 risky per 60 sends |
| Bounce monitoring | No | 60-second monitoring cycle |
| Auto-pause | No | Configurable threshold |
| Infrastructure healing | No | 5-phase graduated recovery |
The pattern is clear. NeverBounce covers the left side of the timeline: what happens before you send. Superkabe covers the right side: what happens during and after you send. For catch-all leads specifically, the right side is where the risk lives.
For a side-by-side look at how NeverBounce and ZeroBounce compare on catch-all handling (and where Superkabe fits in), read our three-way comparison.
Send to catch-all leads. Safely.
NeverBounce says do not send. But you need those leads. Superkabe lets you send to catch-all addresses with per-mailbox risk caps, real-time bounce monitoring, and auto-pause protection. Keep NeverBounce for pre-send cleaning. Add Superkabe for everything after. See how it works.
Frequently asked questions
What does NeverBounce accept_all status mean?
Accept_all means NeverBounce detected that the recipient's mail server accepts emails sent to any address at that domain. The server does not reject fake addresses during SMTP verification, so NeverBounce cannot confirm whether the specific email address belongs to a real mailbox.
Does NeverBounce recommend sending to accept_all emails?
No. NeverBounce officially recommends not sending to accept_all addresses because the deliverability risk is higher. However, 30-40% of B2B leads are on catch-all domains. Following this recommendation strictly means losing a significant portion of your addressable market.
Can I use NeverBounce and Superkabe together?
Yes. They solve different problems. Use NeverBounce for initial verification to filter out definite invalid addresses. Then route leads (including accept_all) through Superkabe for catch-all risk scoring, per-mailbox distribution caps, bounce monitoring, and auto-pause protection.
What is the difference between NeverBounce unknown and accept_all?
Accept_all means NeverBounce confirmed the domain accepts all emails. Unknown means NeverBounce could not reach a conclusion. The server may have been unreachable or used greylisting. Accept_all is definitive. Unknown is inconclusive.
How accurate is NeverBounce for catch-all detection?
NeverBounce is reliable at detecting whether a domain is catch-all. The SMTP probe technique works well for this. The limitation is that detecting catch-all status does not tell you whether the specific person you want to email has a real mailbox.
Does NeverBounce monitor what happens after I send to catch-all leads?
No. NeverBounce is a pre-send tool. Once you send, it has no visibility into bounce events, mailbox health, or domain reputation. You need a separate infrastructure monitoring layer for post-send protection.