Must read!Check a list from $1.49

What Is a Catch-All Email Address (and Should You Send to It)?

By David Ray · Veml articles · Updated November 2026

You run your list through a checker and a handful of addresses come back marked "catch-all" or "risky." They aren't flagged as bad, but they aren't confirmed as good either. So what are they, and should you send to them?

The short answer: a catch-all address belongs to a domain that accepts mail for any name you put in front of the @. That makes it impossible to prove the person is real before you send. Here's what that means in practice and how to decide what to do.

What a catch-all email address is

Normally, a company's mail server knows which mailboxes exist. Send to jane@company.com and, if Jane has an account, the server accepts the message. Send to nobody@company.com and the server rejects it, which is what you see as a bounce.

A catch-all (sometimes called "accept-all") server works differently. It is set up to accept mail for every address at the domain, real or not. Google Workspace, for example, lets administrators route messages "sent to non-existent or incorrect email addresses in your domain" into one catch-all mailbox, so mail meant for help@ or a misspelled name still lands somewhere.

Businesses do this for understandable reasons. They don't want to miss a customer who typed a name wrong, or mail sent to an old address after someone left. Some small companies point everything at one shared inbox simply because it's easy.

Why catch-all addresses are hard to verify

A live mailbox check works by asking the receiving mail server a simple question: "Would you accept mail for this address?" The server's answer is what tells you whether the mailbox exists. No email is actually sent.

A catch-all server answers "yes" to everything. Ask about jane@company.com and it says yes. Ask about zz9-random@company.com and it also says yes. Because the answer is always the same, it tells you nothing about whether a real person is behind the address you care about.

Even the official rulebook for email, a technical standard called RFC 5321, allows for this. It includes a special reply a server can give when an address "appears to be valid but cannot reasonably be verified in real time." In plain English: sometimes the honest answer is "I don't know."

What can happen when you send to one

Because the server accepts everything, one of three things usually happens to your email:

None of these is a disaster on its own. The problem comes when a large share of your list sits on catch-all domains and many of those addresses turn out to be dead. Both bounces and unread mail can count against you with the big inbox providers.

Why it matters for your sender reputation

Gmail and Yahoo both ask senders to keep their lists clean. Google's sender guidelines tell senders to "automatically unsubscribe recipients who have multiple bounced messages" and to consider unsubscribing people who don't open or read their messages. Yahoo's Sender Hub says to "remove invalid recipients from your list promptly" and warns that sending to people who aren't reading your mail "will harm your delivery metrics and reputation."

Catch-all addresses can quietly feed both problems: some bounce, and some go to inboxes nobody opens. A few won't hurt. Hundreds of unknown ones on an old list can.

Check your list before you sendVeml checks every address with a live mailbox check, without sending any email, and spots catch-all domains for you. Each address comes back Passed, Risky, Unknown or Invalid, with a reason and a 0-100 score. Catch-all addresses are marked Risky so you can decide.
Check a list from $1.49

Should you send to catch-all addresses?

There's no single rule, but these questions will usually point you the right way.

Where did the address come from?

If the person typed it into your signup form, booked a call, or bought from you, the address is very likely real, even if the domain is catch-all. Keep it. If it came from a bought list, a scraped directory or a list you inherited years ago, be much more careful. Google's sender guidelines tell senders plainly not to buy email addresses from other companies.

Has this contact ever engaged?

Opens, clicks and replies are the best proof that a catch-all address is alive. If someone replied to you last month, send to them. If an address has never opened anything in a year, it's a candidate for removal whether or not it's catch-all.

How big a share of your list is it?

A business-to-business list can contain a lot of catch-all addresses, because some companies set their mail up that way. In that case you can't simply drop them all. Instead, send to them in smaller batches first and watch your bounce numbers before sending to the rest.

A simple way to handle catch-all addresses

  1. Separate them. Put Risky catch-all addresses in their own group instead of mixing them into your main send.
  2. Keep the ones you know. Contacts who gave you the address directly, or who have engaged before, can go back in.
  3. Test the rest gently. Send to a small batch first. If those come back clean, send to the next batch.
  4. Remove hard bounces straight away. Anything that bounces with a permanent error should come off your list for good. Our guide to hard vs soft bounces explains the difference.
  5. Watch engagement. If an address never opens after several sends, stop sending to it.

The bottom line

A catch-all address isn't bad, it's just unconfirmed. The domain works and the server accepts mail, but nobody can tell from the outside whether a person is reading it. Treat these addresses as "handle with care": keep the ones with a real relationship behind them, test the unknown ones in small batches, and remove anything that bounces.

Frequently asked questions

Is a catch-all email address valid?

Maybe. The domain is real and accepts mail, but the server says yes to every address, so there is no way to confirm from the outside that a particular person reads that inbox. Treat it as risky, not as valid or invalid.

Will emails to a catch-all address bounce?

Often they won't bounce at all, because the server accepts everything. But some servers accept a message first and send a bounce notice later, and some catch-all inboxes are never read. You can't tell in advance.

Should I delete catch-all addresses from my list?

Not automatically. If the contact gave you the address themselves or has opened your emails before, keep it. If it came from an old or bought list and nobody has ever engaged, it is safer to leave it out of big sends.

How does Veml handle catch-all domains?

Veml detects catch-all domains and marks those addresses as Risky, with a reason, so you can decide whether to keep them.

Sources

More articles: