Email & OutreachUpdated Nov 13, 2026

Catch-All Email

A catch-all email setup (also called accept-all) is a mail server setting that accepts messages for any address at a domain, including addresses that don't exist, and delivers them to one chosen mailbox. Because the server says yes to every address, an email verifier can't tell whether a specific person's mailbox is real.

Related search catch all emailcatch-all emailcatch all email address

What is a catch-all email?

A catch-all email is a mail server setting that accepts messages for every address at a domain, whether or not a mailbox exists, and routes them to one chosen mailbox. It is also called an accept-all domain. Without a catch-all, mail to a nonexistent address at a company bounces back to the sender. With one, the message is delivered to whoever owns the catch-all mailbox.

Admins switch it on in their email provider. Google’s Workspace help page, Get misaddressed email in a catch-all mailbox, describes a routing rule that replaces the recipient for “all inactive and unrecognized accounts” with the catch-all address, which can be a user or a Google Group. Zoho Mail’s admin guide says that with a catch-all, “emails sent to any email address related to the domain will not be bounced back.”

For anyone sending email, the catch-all setting matters for one reason: it makes a domain answer “yes” for every address, so you can’t confirm that the person you are writing to exists.

Why do companies set up a catch-all?

ReasonWhat it solvesThe cost
TyposMail to jnae@ instead of jane@ still arrivesSomeone has to sort it
Former employeesCustomer mail to a departed rep isn’t lostOld addresses keep getting sales email
Role addressessupport@, help@ and info@ land in one place without separate mailboxesMore junk in one inbox
Harder to guess addressesZoho notes it discourages spammers who learn valid addresses from which ones bounceVerifiers can’t confirm anyone either

Security gateways can have the same effect. BounceZero’s July 2026 data accuracy study says large companies increasingly accept all addresses at the edge to defeat address harvesting, which is why catch-all rates were highest at companies with more than 1,000 employees.

Why does a catch-all break email verification?

Email verifiers check an address without sending an email. They open an SMTP conversation with the domain’s mail server, name the recipient and read the server’s reply code, then hang up before any message is sent. The reply codes are defined in RFC 5321, the standard for SMTP:

Server replyMeaning in RFC 5321What a verifier concludes
250”Requested mail action okay, completed”Address accepted
550”Requested action not taken: mailbox unavailable (e.g., mailbox not found, no access, or command rejected for policy reasons)“Invalid, unless it’s a policy block
450”Mailbox unavailable (e.g., mailbox busy or temporarily blocked for policy reasons)“Unknown; try again later
252”Cannot VRFY user, but will accept message and attempt delivery”Unknown

A normal server answers 250 for real mailboxes and 550 for fake ones, so the verifier can tell them apart. A catch-all server answers 250 for both. To spot this, verifiers also test an address that can’t exist (a random string at the same domain). If the server accepts that too, the domain is flagged as catch-all, and every address at it gets a “catch-all” or “accept-all” result instead of “valid.”

RFC 5321 also lets servers refuse to confirm addresses at all. Section 7.3 says a server that disables the VRFY command for security reasons “MUST return a 252 response, rather than a code that could be confused with successful or unsuccessful verification.” The protocol never promised senders a way to check mailboxes.

How common are catch-all emails in B2B lists?

Common enough to plan for. In BounceZero’s test of about 50,000 contacts exported from paid Apollo, ZoomInfo and Lusha accounts between May 12 and June 2, 2026:

ProviderValidCatch-allInvalidRisky or unknown
Apollo64.9%18.2%12.8%4.1%
ZoomInfo71.2%15.6%9.3%3.9%
Lusha66.4%16.9%12.1%4.6%

At companies with more than 1,000 employees, the study put the catch-all share at 21% to 24% across providers. BounceZero sells email verification, so treat its numbers as one vendor’s test, not an industry average. Our B2B data providers comparison covers the rest of that study.

The practical point: if you sell to enterprises, roughly one contact in five may come back as catch-all. Deleting them all can remove a large part of a target account list.

How should you treat catch-all contacts in cold email?

Neither “send to all” nor “delete all” is right. A catch-all result means “unknown,” so manage the risk:

  1. Verify first, then split the list. Send to confirmed-valid contacts first. Put catch-all contacts in their own segment.
  2. Send to catch-alls in small batches. Start with a few dozen and check bounces before sending more. If hard bounces climb, stop and look at the domain.
  3. Confirm the person another way. A recent LinkedIn profile at the company, a name pattern that matches verified colleagues, or a contact from a second data source raises confidence. For named accounts, a minute of research per contact is worth it.
  4. Use the company’s real email pattern. If verified colleagues use first.last@, write to first.last@. Our email permutator lists the common patterns.
  5. Remove anyone who bounces. A hard bounce from a catch-all domain means the message was rejected after it was accepted. Suppress the address and never send again. See hard bounce vs soft bounce for how to read the bounce code.
  6. Watch your total bounce rate. Catch-all contacts add risk to a campaign’s bounce rate, which feeds your sender reputation.

For opt-in lists such as newsletters, the rules are softer. Someone who signed up with a catch-all address and opens your emails is a real reader. Remove them only if they bounce or stop engaging, as you would anyone else on a clean list. Our list hygiene guide covers the routine.

Catch-all vs invalid vs role address

ResultWhat it meansWhat to do
ValidServer confirmed this mailbox existsSend
Catch-all (accept-all)Server accepts every address, so this one can’t be confirmedSend carefully, in small batches
InvalidServer said the mailbox doesn’t exist, or the domain has no mail serverDon’t send
Role addressA shared address such as info@ or sales@Send only if a shared inbox is the right audience
UnknownServer didn’t answer, or answered with a temporary codeRe-verify later

Should you set up a catch-all on your own domain?

Not on the domains you send cold email from. A catch-all on a sending domain fills up with auto-replies and spam aimed at made-up addresses, and makes it harder to see real replies. On your main company domain, a catch-all can save customer mail sent to old addresses, but route it to a shared group that someone reads and clears every week. Google’s guide allows a Google Group as the catch-all destination for this reason.

Common questions about Catch-All Email

What is a catch-all email address?

A mailbox that receives every message sent to any address at a domain, including addresses that were never created. If a company sets up a catch-all at its domain, mail to jane@company.com, jnae@company.com and anything-else@company.com all lands in one mailbox instead of bouncing. Google Workspace and Zoho Mail both document it as an admin routing setting.

Are catch-all emails valid?

Some are and some aren't, and you can't tell from the outside. The server accepts every address, so a verifier gets the same 'yes' for a real employee and a typo. A July 2026 test by BounceZero, an email verification company, found 15.6% to 18.2% of contacts exported from Apollo, ZoomInfo and Lusha sat on catch-all domains, and 21% to 24% at companies with more than 1,000 employees.

Should I remove catch-all emails from my list?

Not by default. For cold email, send to catch-all contacts separately: in small batches, after your verified contacts, and stop if bounces rise. Remove a catch-all contact if it bounces, if you can't confirm the person works there, or if your list is already near your bounce limit. For opt-in newsletters, keep them if the person engages.

Why do companies use catch-all email?

To avoid losing mail sent to misspelled names, old role addresses or former employees. Zoho's admin guide also says a catch-all discourages spammers who guess addresses by watching which ones bounce. The trade-off is that the catch-all mailbox collects a lot of junk.

How do I know if a domain is catch-all?

Use an email verifier. It connects to the domain's mail server and asks it to accept a made-up address. If the server accepts an address that clearly doesn't exist, the domain is catch-all, and the verifier marks every address there as catch-all or accept-all instead of valid.

Can a catch-all email bounce?

Yes. The server accepting the address during the SMTP conversation doesn't guarantee delivery. Some servers accept every recipient at the edge and reject or bounce the message later, for example after a security gateway scans it. That is why catch-all contacts carry more bounce risk than verified ones.

Start with one process.

We learn the business and build your first go-to-market process on us this month.