How ZeroBounce handles catch-all domains (and what it misses)
10 min read · Published April 2026
ZeroBounce flags catch-all emails with a dedicated status label. That is genuinely helpful. But the label itself does not solve the problem. You still have to decide what to do with 30-40% of your lead list, and ZeroBounce cannot protect you after you make that decision.
Key Takeaways
- ▸ ZeroBounce returns a "catch-all" status for domains that accept all emails. It does not risk-score individual addresses
- ▸ Skipping all catch-all leads means losing a third of your B2B pipeline. Sending to all of them risks 5-8% bounce rates
- ▸ ZeroBounce has no post-send monitoring. If catch-all leads bounce, nobody auto-pauses your mailbox
- ▸ The practical approach: use ZeroBounce for initial verification, then layer Superkabe for catch-all risk distribution and bounce monitoring
Table of Contents
Quick refresher: what catch-all domains are
A catch-all domain is one where the mail server accepts emails sent to any address. Real employee, former employee, typo, completely made-up name — the server says "sure, I will take it" at the SMTP level. What happens after that varies. Some servers dump unmatched emails into a shared inbox. Others silently discard them. Others bounce them internally, hours or days later.
The problem for cold outreach teams: your verification tool cannot tell whether a specific address on a catch-all domain belongs to a real person. The server looks valid for everything. We covered this in depth in our catch-all domains deep dive — read that if you want the full technical breakdown. For this article, the key point is simple: catch-all domains make verification results unreliable for those addresses.
How ZeroBounce handles catch-all
ZeroBounce takes a straightforward approach. When it checks an email address, it probes the mail server. If the server accepts a test email to a clearly fake address, ZeroBounce classifies the domain as catch-all. Every email on that domain then gets a "catch-all" status in your results.
ZeroBounce catch-all behavior
- ▸ Status label: Returns "catch-all" as a distinct status (not valid, not invalid, not unknown)
- ▸ No risk scoring: Every catch-all address gets the same label regardless of other signals. No 0-100 risk score, no confidence level
- ▸ Decision is yours: ZeroBounce flags it. What you do with that flag is entirely up to you
- ▸ No per-mailbox awareness: The tool has no concept of which mailbox will send to that address or how many risky leads that mailbox already has
- ▸ No memory across runs: If you verify the same domain next month, ZeroBounce checks it fresh. No cached domain intelligence
This is an honest approach. ZeroBounce does not pretend it can verify individual addresses on catch-all domains. It tells you the domain type and lets you decide. The question is whether a binary label gives you enough information to make a good decision.
What ZeroBounce does well
Before getting into limitations, ZeroBounce deserves credit for what it does right. This is one of the top verification tools for a reason.
ZeroBounce strengths
- ▸ Non-catch-all accuracy: Around 98% detection rate for truly invalid addresses on standard domains. Best-in-class
- ▸ Spam trap detection: Identifies known spam trap addresses. Valuable for cold email where one spam trap hit can tank your sender score
- ▸ Activity scoring: Tells you if an email address has been active recently. Helps you prioritize leads beyond just "is this address valid?"
- ▸ Data append: Returns name, gender, location, and account creation date. Useful enrichment if your CRM data is sparse
- ▸ Catch-all detection itself: The fact that ZeroBounce flags catch-all domains at all is valuable. Some cheaper tools just return "valid" for everything on a catch-all domain
For emails on non-catch-all domains, ZeroBounce is excellent. You get a clean valid/invalid result with high confidence. The data enrichment is a nice bonus. If your entire list happened to be on standard domains, ZeroBounce would be all you need.
But your list is not all standard domains. Not even close.
The gap after you press send
Here is where ZeroBounce's catch-all handling falls short. Not because the tool is bad, but because the problem extends beyond what any verification tool was designed to solve.
You run your list through ZeroBounce. You get back 400 "valid" results, 50 "invalid" results, and 200 "catch-all" results. You remove the invalids. Now what? You have 200 catch-all leads and two options:
Option A: Skip all catch-all leads
Safe for your infrastructure. Terrible for your pipeline. You just threw away 200 leads. If those leads came from Clay at $0.02-0.05 each, you burned $4-10 in enrichment costs for nothing. More importantly, some of those 200 leads are real people at real companies who would have responded. You will never know which ones.
Option B: Send to all catch-all leads
Risky. Catch-all addresses bounce at roughly 27x the rate of verified addresses. If you dump 200 catch-all leads into one campaign spread across 4 mailboxes, each mailbox absorbs 50 uncertain leads. If 10% of those bounce (a reasonable estimate), each mailbox picks up 5 extra bounces. That can push a mailbox from a healthy 1% bounce rate to 3-4% in a single day. One bad batch.
ZeroBounce cannot help with either outcome because its job ended when it returned the "catch-all" label. There is no:
What is missing after the label
- ▸ No bounce monitoring: If catch-all leads bounce after sending, ZeroBounce does not know and cannot alert you
- ▸ No auto-pause: If bounces from catch-all leads push a mailbox over threshold, nothing stops the bleeding automatically
- ▸ No risk distribution: ZeroBounce has no concept of "this mailbox already has 5 catch-all leads today, send the next one through a different mailbox"
- ▸ No domain-level intelligence: No caching of catch-all status per domain. No tracking of historical bounce rates from specific catch-all domains
- ▸ No healing: If a mailbox or domain takes damage from catch-all bounces, there is no graduated recovery process
This is not a criticism of ZeroBounce specifically. NeverBounce, MillionVerifier, Clearout — they all have the same limitation. Verification tools verify. They do not monitor, protect, or heal. As we covered in our guide on why verified emails still bounce, even addresses that pass verification can cause problems. Catch-all is just the most common example.
The real numbers on catch-all risk
Let us put actual numbers to this so it is not abstract.
Roughly 30-40% of B2B leads sit on catch-all domains. The percentage is higher if you target enterprise companies (Fortune 500, government, large healthcare systems). Lower if you target startups and SMBs running Google Workspace or Microsoft 365.
For a team sending 500 emails per day across 10 mailboxes, that is 150-200 catch-all leads daily. If you skip them all, you are capping your outreach at 300-350 emails per day. You are paying for 10 mailboxes but only using the capacity of 6-7.
If you send to all of them, expect a bounce rate somewhere between 5-8% on catch-all segments. Industry standard for maintaining good deliverability is under 2%. So your catch-all segment alone can push you well past the danger zone.
The cost of getting this wrong is not trivial. A burned domain takes weeks to recover. A blacklisted IP can take months. And during recovery, every campaign on that domain is either paused or sending to the spam folder. The recovery process for a burned domain is painful and slow.
Risk-aware distribution: the middle ground
There is a third option beyond "skip all catch-all" and "send to all catch-all." Risk-aware distribution means sending to catch-all leads, but with guardrails that limit how much damage any single mailbox or domain can absorb.
This is the approach Superkabe takes. When a lead is ingested, Superkabe checks the recipient domain. If the domain is catch-all, that status is cached in the DomainInsight table so every future lead from that domain is automatically flagged. The lead gets a validation score penalty, which feeds into routing decisions. Then the routing engine distributes the lead with per-mailbox caps: a maximum of 2 risky leads per 60 sends on any given mailbox.
If catch-all bounces start accumulating on a mailbox, Superkabe's 60-second monitoring cycle catches it. The mailbox gets auto-paused before the bounce rate crosses the threshold that damages the domain. And if a domain does take damage, the 5-phase healing pipeline brings it back gradually rather than slamming it back to full volume.
ZeroBounce vs Superkabe: catch-all handling
| Feature | ZeroBounce | Superkabe |
|---|---|---|
| Catch-all detection | Labels as "catch-all" status | Detects + caches per domain in DomainInsight |
| Risk scoring | No scoring. Binary label only | 0-100 validation score with catch-all penalty |
| Send recommendation | User decides | Send with per-mailbox risk caps |
| Per-mailbox risk caps | No | Max 2 risky per 60 sends |
| Post-send bounce monitoring | No | 60-second monitoring cycle |
| Auto-pause on bounce spike | No | Yes, configurable threshold |
| Domain-level caching | No. Checks fresh each time | Cached in DomainInsight table |
| Healing after damage | No | 5-phase graduated recovery |
These tools are not competitors. They solve different parts of the same problem. ZeroBounce tells you the address might be risky. Superkabe manages that risk during and after sending.
The best setup for teams that want to send to catch-all leads safely: verify your list with ZeroBounce (or any verification tool you trust) to remove definite invalids and spam traps. Then route through Superkabe, which handles the catch-all risk distribution, monitors bounces in real-time, and auto-pauses before damage accumulates.
For a broader look at how verification tools compare on catch-all handling, see our ZeroBounce vs NeverBounce vs Superkabe comparison. And for the complete list of verification options beyond ZeroBounce, check our ZeroBounce alternatives guide.
Stop choosing between pipeline and safety
You should not have to skip 30-40% of your leads because your verification tool cannot protect you after the send. Superkabe lets you send to catch-all leads with per-mailbox risk caps, real-time bounce monitoring, and auto-pause. Keep your pipeline full without burning your domains. See how Superkabe handles catch-all risk.
Frequently asked questions
How does ZeroBounce classify catch-all emails?
ZeroBounce returns a "catch-all" status for emails on catch-all domains. This is separate from "valid," "invalid," or "unknown." It means ZeroBounce detected that the domain accepts all emails regardless of whether the specific mailbox exists. The tool does not attempt to determine if the individual address is real.
Should I send to emails ZeroBounce marks as catch-all?
It depends on your risk tolerance and infrastructure setup. Skipping all catch-all leads means losing 30-40% of your pipeline. Sending to all of them without protection risks bounce rates of 5-8%. The practical middle ground is sending with volume caps per mailbox and bounce monitoring so you can pause before damage occurs.
Does ZeroBounce monitor bounces after I send to catch-all leads?
No. ZeroBounce is a pre-send tool. Once you decide to send, ZeroBounce has no visibility into what happens. It cannot track whether the email bounced, whether your mailbox bounce rate spiked, or whether your domain reputation took damage.
What percentage of B2B emails are on catch-all domains?
Roughly 30-40%. The number skews higher for enterprise and mid-market companies. Government organizations and large corporations are especially likely to run catch-all configurations. If your ICP includes companies with 200+ employees, expect a third or more of your leads to be catch-all.
Can ZeroBounce tell me if a specific address on a catch-all domain is real?
No. The server accepts everything at the SMTP level, so there is no way for ZeroBounce to distinguish a real mailbox from a fake one. ZeroBounce can tell you the domain is catch-all but not whether your specific contact exists.
What is the difference between ZeroBounce catch-all and unknown status?
Catch-all means ZeroBounce confirmed the domain accepts all emails. Unknown means ZeroBounce could not determine the email status — the server may have been unreachable, rate-limiting, or using greylisting. Catch-all is a definitive classification. Unknown is inconclusive.