How to Verify Catch-All Emails for Cold Email in 2026

Updated June 2026 · 13 min read · By Marwene Amor

You run your shiny new list through a verifier, expecting clean green checkmarks. Instead a big slice comes back as "accept-all." Not valid. Not invalid. Just a shrug. So now what? Do you send to them and risk the bounces, or drop them and lose what might be perfectly good prospects?

This is the catch-all problem, and it trips up more cold email campaigns than almost anything else on the list-quality side. Most guides hand-wave past it. They tell you to "remove bad addresses" and move on, as if catch-all were a simple yes or no. It isn't. It's a maybe, and how you handle the maybe decides whether your bounce rate stays safe or quietly creeps toward the number that gets your domain throttled.

So let's actually deal with it. What a catch-all is, why it's dangerous, and the practical way to verify and send to them without torching your reputation.

What a catch-all actually is

Email verification normally works by a quiet conversation with the recipient's mail server. Your verifier connects, more or less asks "does john@company.com exist here," and the server answers yes or no. Clean. That yes or no is what lets a verifier sort your list into valid and invalid before you send a single email.

A catch-all domain breaks that conversation. The server is configured to say yes to everything. Ask it about john@company.com, yes. Ask it about thisisnotreal9999@company.com, also yes. It accepts all of it at the front door and sorts out what's real later, internally, where your verifier can't watch. Companies set this up for ordinary reasons, often so that a misspelled address or a department alias still gets through instead of bouncing. They're not trying to ruin your day. They just made it impossible for an outside tool to confirm a specific mailbox.

So your verifier does the honest thing and reports what it knows: this domain accepts everything, I can't confirm this one address, here's an accept-all or unknown status. That's not the tool failing. That's the tool telling you the truth about a domain that won't reveal more.

Why catch-alls are dangerous, not just annoying

The trap with catch-alls is that they feel safe. The server accepted the address, right? So it must be fine. No. Acceptance at the door is not delivery to a real person. Some portion of those accept-all addresses point to mailboxes that don't exist, and the server will quietly discard or bounce them after the fact. You sent. It looked accepted. Days later, a bounce.

Here's why that matters more than it sounds. Your bounce rate is one of the loudest signals mailbox providers use to judge you. Keep it under a couple of percent and you look like someone with a well-kept list. Let it climb past five, and you look like a spammer working off garbage data, and they start routing more of your mail to spam, including the mail to your good addresses. The whole point of verification is to keep that bounce rate low by filtering dead addresses before you send. Catch-alls are the addresses that slip the filter. They're the ones that can push your bounce rate up after you thought you'd cleaned the list. That's the danger: not that they're useless, but that they're invisible risk you can't see until the damage is done. Our deliverability checklist covers the bounce thresholds in detail.

You can't confirm a catch-all. You can shrink the doubt.

Let's be clear about the ceiling here, because some tools oversell it. There is no method that turns a catch-all into a guaranteed-valid address from the outside, short of actually sending and seeing what happens. The server won't tell you, by design. Anyone promising 100 percent certainty on catch-alls is selling you something.

What you can do is move the odds. A catch-all isn't a coin flip; with the right signals you can sort the likely-real ones from the likely-dead ones and act accordingly. Three things do most of that work.

1. Use a verifier that scores, not just flags

Basic verifiers stop at "accept-all" and leave you stranded. Better ones go further, layering in extra signals to estimate whether the specific address is probably real: does it match the company's known email pattern, has the address shown up in other data, does the local part look like a person versus a random string. The output is a confidence score instead of a blank shrug. That score is the thing you actually make decisions with. The dedicated verifiers known for handling catch-alls more intelligently include tools like Bouncer, ZeroBounce, and NeverBounce, and several finders bake decent scoring into their own verification.

2. Cross-check against a quality finder

Where the address came from matters enormously. A catch-all address that Hunter or Snov.io returned with a high confidence score is a very different animal from a catch-all you assembled yourself by guessing firstname@company.com. The finder derived it from a real source, a published address, a pattern tied to an actual employee, scraped from somewhere the person actually exists. So it already carries evidence that the mailbox is real, even though the catch-all server won't confirm it. When a finder hands you a catch-all with a strong score, lean toward keeping it. When you've got a catch-all with no provenance and no score, lean toward caution. The email finder comparison covers which tools give the most useful confidence data.

3. Let two sources agree

When an address really matters, run it through more than one tool and see if they agree. If your finder gives it a high score and an independent verifier also leans valid on its catch-all scoring, that agreement is worth more than either signal alone. It won't reach certainty, nothing will, but two independent yeses on a catch-all is a reasonable bar for putting it in your send pile. One yes and one shrug is a maybe you treat carefully. Two shrugs, and you're better off leaving it out of the main campaign.

How to send to catch-alls without burning your domain

Say you've scored your catch-alls and you've got a pile of likely-real ones you don't want to waste. Good. There are real prospects in there. The rule is simple: never let them ride along with your clean list.

Segment them. Pull every catch-all address into its own group, separate from your confirmed-valid addresses, and send to the two groups differently. Your clean list goes out as normal. Your catch-all segment goes out in smaller batches, more slowly, and ideally from a separate inbox or two that aren't carrying your primary clean traffic. The logic is containment. If the catch-all batch turns out to be 8 percent dead and bounces hard, that damage stays on the inboxes you set aside for it, while the inboxes doing your important sending stay pristine. You're treating the catch-alls like the higher-risk segment they are, and quarantining the risk.

Watch the first batch closely. Send a few hundred, look at the bounce rate that comes back, and let that real-world number tell you how to handle the rest. If the catch-alls from a given source bounce at 3 percent, they're basically fine and you can fold that source's catch-alls into your normal flow with a bit more caution. If they bounce at 15 percent, you've learned that source's catch-alls are garbage and you stop sending to them. The send itself becomes your final, most honest verifier, which is fitting, because in the end actually sending is the only thing that ever truly confirms a catch-all.

Reading the other statuses while you're at it

Catch-all is the confusing one, but your verifier spits out a few other labels worth knowing, because they change how you treat an address. A quick translation. Valid means the mailbox was confirmed, send freely. Invalid means it's dead, drop it, no debate. Accept-all is the catch-all we've been wrestling with, the maybe. Unknown means the verifier couldn't get a clear answer at all, often a timeout or a temporarily unreachable server, and those are worth re-checking later rather than judging on the first pass.

Two more deserve a flag. Role-based addresses like info@, sales@, or support@ go to a shared mailbox or a team, not a person, so they tend to convert poorly on cold outreach and some land you in front of a gatekeeper rather than a buyer. Disposable addresses, the throwaway domains people use to dodge signups, are almost never worth sending to and a decent verifier marks them for you. Treat both as low priority, and your list gets cleaner before the catch-all question even comes up.

When to just skip them

Not every campaign should bother with catch-alls at all, and pretending otherwise wastes your time. If your total list is huge and your confirmed-valid segment alone is more than enough to hit your goals, skip the catch-alls entirely. The juice isn't worth the squeeze when you've got plenty of clean addresses waiting. The catch-all dance is for when you can't afford to throw away a third of your hard-won list, not for when you're swimming in prospects.

And if you're brand new, sending from a fresh domain that's barely warmed, skip them for now without a second thought. A young domain has no reputation to spare, and the last thing it needs is a batch of risky addresses pushing its bounce rate up in week one. Build your reputation on clean, confirmed sends first. Come back for the catch-alls once your domain has earned the standing to absorb a little risk. The warmup playbook covers getting a new domain to that point.

The honest takeaway

Catch-alls are a maybe, and the whole skill is in handling the maybe like a professional instead of pretending it's a yes or a no. You can't confirm them from the outside. You can score them, cross-check them, segment them, and let a careful first send tell you the truth. Do that, and catch-alls stop being the silent killer of your bounce rate and become just another segment you manage with a bit more care than the rest. Ignore the problem, send to them blind alongside your clean list, and you'll learn the hard way why so many promising campaigns mysteriously start landing in spam.

If you want fewer of these headaches in the first place, the fix starts upstream with better data. A good finder hands you addresses with the confidence scores that make this whole decision easier, so start with the finder comparison, then run everything through the deliverability checklist before your first send.

Frequently asked questions

What is a catch-all email address?

A catch-all, sometimes called accept-all, is a domain set up so its mail server accepts email sent to any address at that domain, even ones that don't exist. So john@company.com and nonsense@company.com both get accepted at the door. For verification that's the problem: the usual check of asking the server whether an address exists comes back yes for everything, so a verifier can't confirm whether a specific mailbox is real. It returns a status like accept-all or unknown instead of a clean valid or invalid.

How do you verify a catch-all email address?

You can't confirm one with a single SMTP check the way you can a normal address, because the server accepts everything. Instead you reduce the uncertainty: use a verifier that scores catch-alls with extra signals like pattern matching and historical data rather than just flagging them unknown, cross-check against a second source such as a finder that derived the address from a real profile, and treat the survivors as a lower-confidence segment you send to carefully.

Should I email catch-all addresses in a cold campaign?

Cautiously, and never mixed in with your clean list. Catch-alls carry a higher chance of bouncing, so sending a large batch alongside your verified addresses puts the whole campaign's bounce rate at risk. Segment catch-alls into their own low-volume sends, from a separate inbox if you send a lot of them, so a bounce spike doesn't damage the inboxes carrying your clean traffic.

Why do catch-all emails hurt deliverability?

Because they hide bounces you can't see in advance. A normal verifier filters dead addresses before you send, keeping your bounce rate low. Catch-alls slip through because the server accepts them, so some turn out dead and bounce only after you've sent. A high bounce rate signals to mailbox providers that you're working off a poor list, and that hurts inbox placement for everything you send.

What percentage of a B2B list is usually catch-all?

It varies by market, but a meaningful chunk of B2B domains run catch-all, and larger companies are more likely to. It's common to see a noticeable slice of a list come back as accept-all rather than cleanly valid. That's why you need a plan for them rather than treating them as an edge case, because on many lists they're too big a segment to throw away without losing real prospects.

Do email finders return catch-all addresses?

Yes, finders like Hunter and Snov.io will surface addresses on catch-all domains, and a good one gives you a confidence score alongside them. The advantage over a raw guess is that the address was usually derived from a real source tied to an actual person, so a catch-all from a quality finder is a better bet than one you assembled from a name formula. Use the confidence score to decide how to treat it.

Bottom line

A catch-all isn't a dead address and it isn't a safe one. It's an unknown, and the campaigns that handle unknowns well are the ones that keep their bounce rate low and their domain healthy. Score them, cross-check them with a quality finder, segment the keepers into their own careful sends, and skip them entirely when your clean list is already enough or your domain is too young to take the risk. That's the whole playbook, and it's the difference between a list-quality problem you control and one that controls you.

Get verified data with Snov →

Related Reviews & Guides

Other deep dives on EmailToolsHub that pair well with this one.

Browse all reviews →