Catch-all emails in cold outreach: send or skip?
Catch-all email in cold outreach is a judgment call. A sender's guide to the deliverability risk and how MailFleet flags catch-alls so you can decide.
Catch-all email in cold outreach is one of the judgment calls that splits experienced senders. Some drop every catch-all address the moment a verifier flags it, others send to all of them and shrug at the bounces, and both habits cost you either good conversations or a healthy domain. The right answer sits in between, and it depends on your sending reputation, how much of your list is catch-all, and how much risk you can absorb this week.
What a catch-all address is
A catch-all domain, sometimes called an accept-all domain, is set up to accept mail to any address at the domain instead of rejecting unknown mailboxes. Send to jane@company.com, info@company.com or asdfgh@company.com and the receiving server returns the same accepted response at the door. That acceptance is not proof that a real inbox is behind the address. A verification tool confirms an ordinary mailbox by asking the receiving server whether it exists; a catch-all server answers yes to everything, so the tool cannot separate a live person from a typo or a guess.
That single behaviour is the whole problem, and it is worth understanding before you decide anything. For the full picture, see what a catch-all address actually is.
The deliverability risk of catch-all email in cold outreach
A catch-all address is not automatically bad. Plenty of real companies run catch-all domains on purpose. The risk is that you cannot tell the good ones from the dead ones, and in cold outreach dead addresses are expensive.
When you send to a catch-all that has no real mailbox behind it, one of two things happens. The server accepts the message and silently discards it, so you never learn anything, or it accepts first and bounces later with a delayed rejection. The second case is the dangerous one: those late bounces land in your bounce rate days after the send, and bounce rate is one of the clearest signals a receiver uses to judge a sender. Keep it under roughly 2% and you are fine; let it climb toward 4% or higher and you start damaging the reputation of the whole domain, which pushes your good mail toward spam. The ordered way to protect that number is in our cold email deliverability checklist.
Catch-alls carry a second, quieter risk. Spam traps and recycled addresses can hide behind an accept-all domain, where no verifier can see them, and hitting those is one of the faster routes to a reputation problem. If you want the longer list of what quietly sinks cold mail, we cover it in why cold emails go to spam.
Send or skip: a decision framework
There is no universal rule, because the cost of a bounce depends entirely on the state of your sending setup. A healthy, well-warmed domain can absorb a modest share of catch-alls without noticing; a new or struggling one cannot. Weigh these factors before you decide.
| Factor | Lean toward sending | Lean toward skipping |
|---|---|---|
| Your domains | Warmed, established, bounce rate well under 2% | New, cold, or already under pressure |
| Share of list that is catch-all | A small slice you can dilute into good mail | A large block that would dominate the send |
| The account's value | A named decision-maker at a target account | A generic scrape you can easily replace |
| Address confidence | Follows the company's known email pattern | A guess, or a role address like info@ |
| Your capacity to watch | You can check bounces daily and pause fast | You cannot babysit the campaign |
Read the table as a balance, not a checklist. If most of your answers sit in the left column, sending to catch-alls is a reasonable, controlled bet. If they cluster on the right, skip them, or at least hold them back until your setup is stronger. A warmed domain is the single biggest thing in your favour here, which is why warming the domain first changes what you can safely send to.
The size of the catch-all slice matters as much as any single factor. A handful of catch-alls mixed into a few hundred confirmed-valid sends barely moves your numbers, so the downside of a few dead ones is small. A list that is half catch-all is a different thing entirely: send it blind and you are betting your domain on addresses no tool could confirm, and a bad guess shows up as a bounce spike rather than a rounding error.
How MailFleet flags catch-alls during verification
MailFleet does not make this decision for you, by design. Its job is to tell you honestly what each address is, then let you choose. Email verification is included on Pro, with 300 checks a day, and Scale, with 1,000 a day.
Run a list through Email Verification in one of three ways: upload a CSV, paste up to 5,000 addresses at once, or check the leads you already have. Every address comes back with a status, and catch-all gets its own. Catch-all means the domain accepts every address, so the mailbox cannot be confirmed. It sits alongside Verified (the mailbox exists and accepts mail), Role email, Unknown, Invalid, Disabled, Disposable, Spam trap and a few more, so a catch-all is never quietly lumped in with confirmed-good addresses.
What you do with those catch-alls is your call. When you send a check's results into a campaign or save them as a lead list, you tick which statuses to include, and only valid addresses are ticked to start. Catch-all is a separate box you add when you want to take the bet. The same choice appears if you verify while importing: you decide whether catch-all, role and unknown addresses are let in, while the truly bad categories such as invalid, disabled, disposable and spam-trap addresses are never imported at all.
The counting is simple. One credit per address checked, an address you checked in the last 30 days is free to check again, and a malformed address is marked Invalid for free. Re-verifying a catch-all later therefore costs you nothing within the month, which matters, because a domain's configuration can change and today's catch-all is not always next month's.
Putting it into practice
The cleanest workflow treats catch-alls as their own segment rather than a decision you make address by address.
- Verify the whole list before it goes near a campaign, so every address carries a status.
- Split the catch-alls out from the confirmed-valid addresses.
- Send the confirmed-valid ones normally, and send catch-alls in a smaller proportion from your healthiest, most-warmed domains.
- Watch the bounce rate on those sends daily, and pause the moment it drifts up.
- Re-verify anything marked Unknown or catch-all later, since the recheck is free within 30 days.
Treated this way, catch-all email in cold outreach stops being a gamble and becomes a measured part of the list you can turn up or down. You are not guessing; you are sending to a known-risk segment with the dial in your hand and your bounce rate in view. That is the real answer to send or skip: not a fixed yes or no, but a decision you make with the facts in front of you and a way to pull back the moment the numbers tell you to.
FAQ
Should I ever send to catch-all addresses in cold outreach?
Yes, when your sending setup can absorb the risk. A warmed, established domain with a low bounce rate can send to a modest share of catch-alls and watch the result. A new or struggling domain should skip them until it is stronger, because a catch-all bounce costs far more when your reputation is already thin.
Does a catch-all result mean the email is fake?
No. A catch-all result means the domain accepts mail to any address, so the verifier cannot confirm whether a real mailbox exists, not that the address is dead. Many catch-all addresses belong to real people, and the uncertainty is the point, which is why you treat them as a separate, higher-risk group rather than discarding or trusting them outright.
How do catch-alls affect my bounce rate?
If a catch-all address has no real mailbox, the server may accept the message and bounce it later, and that delayed bounce counts against your rate like any other. Sending to a large block of unverified catch-alls is a common way bounce rates creep over the 2% line, which is where receivers start treating a sender as careless and deliverability slips.
Can MailFleet confirm a catch-all address beyond "catch-all"?
Not to a confirmed yes or no, because no verifier can. The receiving server answers accepted for every possible address on a catch-all domain, so there is no honest way to confirm the specific mailbox. MailFleet reports the status as Catch-all rather than guessing, and leaves the send-or-skip choice to you.