A catch-all email domain (also called accept-all) is one whose mail server accepts mail for every address at the domain, whether or not a mailbox with that name exists. For the domain's owner it is a setting: mail to any unknown address lands in one inbox instead of bouncing. For a sender checking a list, it is a verification result: because the server says yes to everything, nobody can confirm from outside that a particular person's address is real. In cold outreach, that uncertainty matters. Catch-all and unknown addresses bounce much more often than confirmed ones, and bounces cost you sender reputation. The careful approach is to try a second check, send only to confirmed addresses, and protect your main domain.
In this guide
- Two meanings of "catch-all email"
- How email verification decides valid, invalid or catch-all
- Catch-all is not the same as unknown
- Why sending to catch-all addresses is a risk
- What a careful cold emailer does
- How Outfound handles catch-all and unknown addresses
Two meanings of "catch-all email"
If you search for "catch all email", half the results tell you how to set one up and the other half tell you how to handle one in a list. Both are about the same mechanism, seen from opposite sides.
| Who is asking | What "catch-all" means | Why they care |
|---|---|---|
| The domain's administrator | A routing rule in the mail system (Google Workspace, Microsoft 365 and most hosting panels offer one) that delivers mail for any non-existent address to a chosen mailbox | Not losing mail sent to a misspelled or old address, such as a former employee's |
| A sender checking a list | A verification status: the domain accepts every address, so this one cannot be confirmed | Deciding whether the address is safe to send to |
Some companies turn on a catch-all on purpose. Others have one without knowing it, because their mail goes through a security gateway that accepts everything first and sorts it out later. From the outside the two look the same. This guide is about the second meaning: you have an address for a decision-maker at a company, your verifier says "catch-all", and you need to decide what to do.
How email verification decides valid, invalid or catch-all
An email verifier does not send an email. It runs a few checks and stops just before the message itself:
- Syntax. Is the address well formed? A missing @ or an illegal character ends the check.
- Domain and MX records. Does the domain exist, and does its DNS name a mail server? No mail server means no delivery.
- SMTP conversation. The verifier connects to that mail server and starts a delivery as a normal sender would. When it names the recipient, the server answers. Under the SMTP standard, RFC 5321, a server returns "250 OK" when it accepts a recipient and typically a 550 reply when the address is known not to be deliverable. The verifier then disconnects without sending anything.
- The catch-all test. The verifier also asks about an address that cannot exist, such as a long random string at the same domain. If the server accepts that too, its "yes" means nothing, and the domain is reported as catch-all.
Why can a server accept first and fail later? The same standard allows servers that do not check recipients until after the message arrives; they send back a failure notice afterwards (RFC 5321, section 3.3). Many corporate gateways work this way. So "accepted during the check" and "delivered to a person" are not the same thing.
Catch-all is not the same as unknown
Verifiers usually return four or five results. Two of them are uncertain, for different reasons:
| Result | What the server did | What it tells you |
|---|---|---|
| Valid | Accepted this address and rejected a made-up one | The mailbox exists. Safe to send, as far as a check can say. |
| Invalid | Rejected the address, or the domain has no mail server | Do not send. It will bounce. |
| Catch-all (accept-all) | Accepted this address and the made-up one | The server answered, but its answer cannot separate real from fake addresses. |
| Unknown | Did not answer clearly: timed out, said "try later" (greylisting) or blocked the check | Nothing yet. A later or second check may give a clear result. |
The difference matters for what you do next. An unknown can sometimes be resolved: a check an hour later, or by a different verification service with different infrastructure, may get a clear valid or invalid. A catch-all usually cannot, because the server will keep accepting everything; asking again gets the same yes.
Why sending to catch-all addresses is a risk
Mailbox providers watch how a sender behaves. A sender whose messages often go to addresses that do not exist looks like someone mailing an old or bought list, which is the pattern of spam. Gmail's sender guidelines tell senders to unsubscribe recipients after repeated bounces and to slow down when messages start bouncing. Yahoo's sender best practices say to monitor hard and soft bounces and remove invalid recipients promptly. Both also set a spam complaint limit: Google asks bulk senders to keep the spam rate in Postmaster Tools below 0.3%, and recommends below 0.1%.
Catch-all addresses carry three risks at once:
- Late bounces. The server accepts the message, then sends back a failure notice when it finds no mailbox. You see the bounce after the fact.
- Silent loss. The message lands in a shared catch-all inbox that nobody reads, or one person reads it who is not the person you wrote to. No bounce, but no reply either.
- Spam traps. Some domains that accept everything are watched for mail sent to addresses that never existed. Mail to a guessed address can land there.
In a mailing to customers who signed up, an occasional catch-all is harmless. In cold outreach, where every address was found rather than given to you, the uncertain addresses can make up a large share of the list, and they produce most of the bounces. A new sending domain with few messages behind it feels this fastest. Our post on getting out of the spam folder covers the other half of reputation: authentication, volume and content.
What a careful cold emailer does
- Verify every address before it enters a campaign, not only when you build the list. Addresses go stale as people leave.
- Give "unknown" a second chance. Recheck later, or with a second, independent verification service. A share of unknowns turn out valid; others turn out invalid, which is also worth knowing.
- Do not count catch-all as valid. If the company matters, look for another person there whose address verifies, or for a general inbox (info@, sales@) that verifies. Read how Outfound uses general inboxes.
- If you do send to unconfirmed addresses, keep it small. A handful per day per sending domain, mixed in with confirmed addresses, and stop at the first bounces.
- Send from a separate domain. Use a sending domain (or subdomain) that is not the one your team and customers use every day, so that a reputation problem stays there. See sending domain setup and using a subdomain.
- Warm up and watch bounces. Start a new domain with low volume and raise it slowly (warm-up). Never mail an address again after a permanent bounce (what happens to bounced emails).
- Write to fewer, better-chosen people. A short list of companies that clearly fit, each with a confirmed decision-maker, gets more replies than a long list padded with guesses.
How Outfound handles catch-all and unknown addresses
Outfound finds companies that fit your customer profile, researches each one on its live website, finds the decision-maker and writes an email for each company for you to approve. The contact's address is checked as part of finding it:
- Contact addresses are verified before sending, and the result is shown next to each contact: verified, accept-all server, no clear answer, invalid, or not checked yet (contact verification states).
- When the first check gets no clear answer, a second, independent verification service checks the address. It counts as valid only if that second check confirms it; if the second service also finds an accept-all server or gets no answer, the address stays unconfirmed.
- Since 6 November 2026, Outfound sends only to addresses confirmed valid. Accept-all and unconfirmed addresses are not sent to, and contact searches keep looking until they find people with confirmed addresses.
- Mail goes out from a separate sending domain with SPF, DKIM and DMARC, warmed up gradually, and a campaign pauses itself if inbox placement drops. Addresses that bounce permanently go to your blocked list and are never emailed again.
Across the platform, 98.8% of emails sent between 25 March and 25 September 2026 were delivered. Plans and the free trial are on the pricing page.
Last updated: · By: Tolga Tatar
