Catch-all emails: what they are and whether you should send to them

A catch-all email (also called accept-all) is an address on a domain whose mail server accepts mail for every address at that domain, real or not. Because the server says yes to owner@, info@ and qx7z9@ alike, an email verifier can't tell whether the mailbox you want actually exists. So a catch-all result isn't "valid" and it isn't "invalid": it's unconfirmed. Should you send to it? Only as a separate, smaller segment after your verified addresses, only for addresses the business published itself, and only after a test batch shows the bounces stay low.

This page explains how verifiers detect catch-all domains, why so many small businesses have one, how common they are, a decision rule with a worked example, and how to test catch-all sends without hurting your sender reputation.

What is a catch-all email address?#

It's any address at a domain configured to accept mail for all recipients. The domain owner sets this up, on purpose or by default, so that mail to a misspelled or unknown address lands in one inbox instead of bouncing.

For the owner, that's convenient. For a sender, it removes the one signal a verifier relies on: the server's "no such user" answer. Verifiers label the result in different ways, which causes confusion:

Catch-all and accept-all are the same thing. "Unknown" is not: it means no answer at all, and a later re-check often turns it into a real grade.

How does a verifier know a domain is catch-all?#

It asks the server about an address that can't exist. A verifier opens an SMTP conversation with the domain's mail server, names your address in a RCPT TO command and reads the reply: 250 means "I'll accept it", 550 means "no such user". Then it asks the same question about a long random string at the same domain. A normal server rejects the random one. A catch-all server accepts it too.

Once the server has said 250 to an address nobody could own, its 250 for your address carries no information. That's the whole problem, and no amount of re-checking fixes it. Our guide to how email verification works walks through the full sequence (syntax, MX lookup, the SMTP check and its limits). If you want to test a single address yourself, see how to check if an email is catch-all.

Why are so many small-business emails catch-all?#

Because catch-all is one of the simplest ways to make sure no customer email is lost, and the tools small businesses use make it easy to switch on. A few common routes:

• Google Workspace has a routing setting for a catch-all address that receives misaddressed mail sent to the domain [3].
• cPanel hosting, used by many small-business web hosts, has a "Default Address" feature that sets a catch-all for mail sent to addresses that don't exist. The alternative is to reject that mail at SMTP time with an error [4].
• "Don't miss a quote" setups. A plumber doesn't want to lose a customer who typed quotes@ instead of quote@, so everything goes to the owner's inbox.
• Filtering servers. Some mail systems accept every recipient during the SMTP conversation and sort mail out afterwards, which also hides which mailboxes exist from people probing for them.

Owner-run businesses often set up email once, through their web host or whoever built the site, and never touch it again. That's why catch-all domains show up so often in lists of local businesses, the kind you'd build from Google Maps. We haven't published a measured share for local-business domains, so we won't give you one; the next section has the published figures from verifiers.

How common are catch-all emails?#

Common enough that every list will have some. Published figures vary because they measure different things:

The spread is the point. A list of large companies on strict mail servers will have few catch-alls. A list of small businesses on shared hosting can have many. Measure your own list: the catch-all share after verification tells you how big your "maybe" segment is before you plan a campaign around it.

What happens if you send to a catch-all address?#

One of three things, and you can't tell in advance which:

1. It's delivered and read. Often true for the address on the business's contact page, which is usually the owner's main inbox.
2. It bounces later. Some servers accept during the SMTP conversation, then send a bounce once they find no such user. These count against you like any other bounce.
3. It disappears. Mail to a non-existent address lands in an inbox nobody reads. No bounce, no reply. Abandoned domains that still accept everything can also be watched by anti-spam services as traps.

How often the bad outcomes happen depends on how the addresses were found. In one published test, Hunter sent the same campaign to 100 accept-all addresses and 100 verified ones: the accept-all group bounced at 27%, the verified group at 1% [1]. That's one test of 200 sends, so read it as a warning, not a rate to plan on.

For context, the sending tools you're likely to use act on bounces at low levels: Woodpecker's default auto-pause is 2%, and Instantly pauses a campaign above 5% once it has sent 200 emails [5][6]. Gmail and Yahoo don't publish a bounce threshold, but they do publish a spam-rate limit of 0.3% and expect you to stop mailing addresses that bounce [7][8]. Our cold email bounce rate guide has the full table.

Should I send to catch-all emails? A decision rule#

Decide per address, not per domain, using where the address came from. The verifier can't help, but the source can.

Then ask one market-level question: do you need the maybes at all? If your verified segment is big enough for the campaign, skip the catch-all segment and save the risk. Catch-all addresses are most worth it in small markets, where every business counts and skipping a large share of them hurts.

A worked example (illustrative)#

Say you've found emails for 1,000 local businesses and verified them. These numbers are made up to show the arithmetic; plug in your own.

• 650 Verified, 250 Accept-all, 100 Invalid (dropped).
• Of the 250 accept-all, 180 were published on the business's own site and 70 were pattern guesses.

Apply the rule: drop the 70 guesses. Your maybe segment is 180.

Now compare two ways to send, assuming (for illustration) a 1% bounce rate on verified addresses and 8% on the published catch-alls:

Kept separate, the verified campaign stays healthy and the catch-all problem shows up in a batch of 50, where it costs four bounces instead of fourteen. If the test batch had come back at 0 or 1 bounce, you'd send the remaining 130 in small batches.

How do I test catch-all sends safely?#

Treat the catch-all segment as an experiment with a stop rule decided in advance.

1. Send your verified segment first and make sure it's healthy: bounces under 2%, no spam complaints.
2. Pick a test batch of 50 to 100 catch-all addresses, published ones only, as its own campaign so its numbers are separate.
3. Set the stop rule before you send. For example: at 50 sends, 0 to 1 bounce (2% or less) means continue; 2 to 3 means keep only main-inbox addresses from contact pages; 4 or more means stop the segment.
4. Wait two to three days before judging. Late bounces from catch-all servers arrive after the send, not during it.
5. Read the replies too. A batch with no bounces and no replies may be landing in unread inboxes. That's cheaper than bounces, but it's not a reason to scale.
6. Add every bounce to your suppression list at once, so no future campaign or client sends to it again.
7. Scale in batches, not all at once, and keep watching the segment's own bounce rate, not your account average.

Our cold email checklist for agencies covers the rest of the setup: authentication, warm-up and suppression.

FAQ#

What is a catch-all email?#

A catch-all email is an address on a domain whose mail server accepts mail for every address at that domain, whether or not a mailbox by that name exists. Because the server says yes to everything, an email verifier cannot confirm that the specific mailbox is real.

Is accept-all the same as catch-all?#

Yes. Catch-all and accept-all describe the same server behavior: it accepts every recipient during the SMTP check. Some verifiers call the result risky or accept-all. Unknown is different: it means the check itself failed, for example because the server timed out or refused to answer.

Should I send to catch-all emails?#

Sometimes. Send to catch-all addresses only as a separate, smaller segment after your verified addresses, prefer addresses the business published on its own website, skip pattern guesses, and start with a test batch of 50 to 100. If the batch bounces above about 2%, stop or tighten the rule.

Do catch-all emails bounce?#

Some do. A catch-all server can accept a message during the SMTP conversation and send a bounce afterwards, or deliver it to an inbox nobody reads. In one published test by Hunter, 100 accept-all addresses bounced at 27% against 1% for 100 verified ones. Your rate depends on how the addresses were found.

How common are catch-all emails?#

Common enough to matter. Hunter reports that 38% of email domains in a sample of 2,572 addresses were accept-all. MailerCheck reports that 8.6% of all addresses it has verified were catch-all, and that the median list had 15.25%. The numbers measure different things, so treat them as ranges, not a benchmark.

Can any tool verify a catch-all email for certain?#

No. When a server accepts every address, the SMTP check carries no information about one mailbox. Some verifiers add extra signals and score the address, but none can confirm it the way a normal server's reply does. Treat a catch-all result as a maybe, never a yes.

Sources#

1. Hunter, Accept-all and catch-all emails, November 4, 2025 (38% of domains in 2,572 addresses; 100 vs 100 send test, 27% vs 1% bounces).
2. MailerCheck, What is a catch-all email?, July 15, 2025 (8.6% of verified addresses; 15.25% median per list).
3. Google Workspace Admin Help, Get misaddressed email in a catch-all mailbox.
4. cPanel Documentation, Default Address.
5. Woodpecker, Bounce shield help article (2% default), accessed October 2026.
6. Instantly, High bounce auto-pause feature, accessed October 2026.
7. Google, Email sender guidelines.
8. Yahoo, Sender best practices.
9. IETF, RFC 5321: Simple Mail Transfer Protocol (the SMTP conversation, reply codes 250 and 550).
10. Leadraft, Verification methodology.