The short answer
A catch-all (or "accept-all") email address is one on a domain whose mail server accepts mail for any address at that domain, whether or not a mailbox by that name exists. Because the server says yes to everything, an email verifier can't tell if a specific person's mailbox is real, so these addresses are marked unknown, risky, or not confirmed. They may work fine, but send to them carefully.
A catch-all address is not a bad address. It's an address that can't be proven good or bad from the outside. The domain is real and receives mail. What's missing is a clear answer about the one mailbox you care about.
How catch-all works at the mail server
When you verify an email address, the verifier finds the domain's mail server and starts the same conversation a sending server would. It says who the mail is from, then names the recipient, and waits for the server's reply. It stops there. No message is sent.
On a normal domain, the server answers the recipient question honestly:
jane@company.comexists: the server replies that it will accept mail for her.jnae@company.comdoesn't exist: the server replies that there is no such user.
On a catch-all domain, the server accepts both. It might deliver mail for unknown names to a shared inbox, to an administrator, or nowhere at all. Some servers accept everything at this stage and reject the message later, after it has been fully received. Either way, the answer during the check is the same "yes" for every address.
A verifier can spot this by also asking about an address that almost certainly doesn't exist, such as a long random string at the same domain. If the server accepts that too, the domain is catch-all, and its "yes" for the real address doesn't mean much.
Why companies set up catch-all domains
There are ordinary reasons to configure a domain this way:
- Don't lose mail to typos. If a customer writes to
jon@instead ofjohn@, the message still lands somewhere a person can see it. - Keep mail for people who left. Messages to former employees keep arriving instead of bouncing, so a customer or vendor isn't left hanging.
- Make up addresses on the fly. Some people give each website a different address (like
shop-name@theirdomain.com) to track who shares their address. A catch-all lets all of them work without setup. - Hide who works there. If the server accepts every name, outsiders can't use it to test which addresses are real.
- Security filtering. Some organizations route all incoming mail through a filtering service that accepts first and sorts later.
- Default settings. Some hosting plans turn it on, and nobody changed it.
Catch-all setups are common at small businesses with their own domain. They show up at larger organizations too.
Why verifiers label catch-all addresses "unknown" or "risky"
Verification works by asking the mail server about one address and reading its reply. A catch-all server gives the same reply for every address, so there's no signal to read. The verifier knows:
- The domain exists and has a working mail server.
- The server said it would accept mail for the address.
It does not know whether a person will ever read it. The address might be a real inbox. It might go to a shared folder nobody checks. It might be quietly discarded. It might bounce after the server has had a closer look.
That's why you'll see labels like "unknown," "risky," "accept-all," or "not confirmed." They all mean the same thing: the check ran, and the server wouldn't give a straight answer.
Catch-all is a property of the domain, not the address. Every address at that domain will get the same label. If one contact at a company comes back catch-all, expect the rest of that company's addresses to come back catch-all too.
How to decide whether to send to a catch-all address
There's no rule that fits every list. These questions help you decide.
Where did the address come from?
An address the person typed into your form, wrote on a business card, or sent you in an email is very likely real. Catch-all just means you can't prove it. An address that was guessed from a naming pattern, scraped from a site, or bought in a list is much riskier, because nothing tells you a person by that name works there.
Does it follow the company's pattern?
If other confirmed contacts at the domain use first.last@ and this one does too, that's a good sign. A name that doesn't match the pattern, or an address with an obvious typo, deserves more doubt.
Send small, then watch
- Put catch-all addresses in their own segment rather than mixing them into a large send.
- Send to a small batch first, and send your most trusted addresses before the guessed ones.
- Check bounces after each send. Remove any address that hard-bounces. Our guide to hard bounces vs. soft bounces explains the difference.
- Watch engagement over time. Replies, clicks, and opens suggest a real reader. If an address never responds across several sends, consider dropping it.
When to skip them
If you're sending from a new domain, or your recent sends have had bounce problems, it may be wise to hold back catch-all addresses you didn't get directly from the person until your sending is in good shape.
How the Email Verification add-on labels catch-all addresses
The Email Verification add-on for Google Sheets marks these addresses deliverable? (catch-all, not confirmed). The question mark is deliberate. The server said yes, but the mailbox couldn't be confirmed.
To pull them into their own group, turn on a filter with Data › Create a filter and show only that status. Then you can copy them to a separate tab and send to them on their own schedule. The help page on catch-all results has more detail, and the guide to verifying emails in Google Sheets walks through a full run.
FAQ
Is a catch-all email address valid?
It may be. The domain is real and accepts mail, but the server accepts mail for every address, so nobody outside the company can confirm that this specific mailbox exists or is read.
Will email sent to a catch-all address bounce?
Usually not at first, because the server accepts it. Some catch-all servers check more carefully after accepting a message and send a bounce later. Others deliver unknown names to a shared inbox or discard them without notice.
Can any email verifier confirm catch-all addresses?
Not with a mail server check alone. The server gives the same answer for real and made-up addresses, so there is nothing to tell them apart. Signals from your own sending, like bounces and replies, are the best evidence.
Should I delete catch-all addresses from my list?
Not automatically. Keep the ones people gave you directly, send to them in small batches, and watch for bounces and replies. Be more cautious with guessed, scraped, or purchased catch-all addresses.
Want to know which of your addresses are catch-all before you send? Install Email Verification free and check your first 50 addresses right in Google Sheets.