Catch-all email addresses: should you send to them?

What is a catch-all email address?

A catch-all email address is one on a domain whose mail server accepts mail for any name before the @, so no verifier can confirm that the specific mailbox exists. The domain is also called an accept-all domain. Send a message to anything-at-all@theirdomain.com and the server answers yes, whether or not anyone with that name works there.

Hunter describes three outcomes. If the address exists, the message is delivered. If it does not, the message may land in a shared catch-all inbox or bounce later.

Catch-all is usually a setting, not a sign of a careless company. Google Workspace has an admin option that routes mail for non-existent addresses into one mailbox. In Exchange Server, a relay domain is one where Exchange is not responsible for sending non-delivery reports for recipients that do not exist (Microsoft). When every recipient for a domain is in Exchange Online, Microsoft 365 instead rejects unknown recipients at the edge with a 550 5.4.1 error (Microsoft).

Gateways blur the picture further. Allegrow reports that 55% of the Fortune 500 primary domains it tested sit behind a visible secure email gateway, a filtering layer that can answer a verifier before the real mailbox does, with a similar effect on verification.

Catch-all email verification: why no tool can confirm the mailbox

An email verifier opens a conversation with the receiving server and, in a typical check, stops before sending any message. It names the recipient and reads the reply. Under RFC 5321 (section 3.3), a server that knows a recipient is not deliverable replies with a 550 code.

To spot a catch-all, the verifier also asks about an address that cannot exist, such as a random string. If the server accepts that, it accepts anything, and its yes for your contact carries no information. That is why verifiers usually label these addresses catch-all, accept-all or risky instead of valid.

Three details make it harder.

• Late checks. RFC 5321 notes that some servers check the recipient only after the message text arrives, and a server that accepted a message must deliver it or report the failure. The bounce then comes later. QuickEmailVerification, a vendor, says it can arrive hours or days afterward.
• Silence. BounceZero found that 64.9% of what its checks flagged as catch-all came from two consumer providers, Yahoo and T-Online. It reads those as providers that will not say whether a mailbox exists, not companies that chose to accept everything.
• Labels. Scrupp points out that vendors give the same situation different names, and some return valid. Without extra signals, a valid label on a catch-all domain describes the domain's setting, not the mailbox.

Re-verifying the same address does not help, because a catch-all domain will accept it again. An unknown result is different: a failed check that can resolve on a retry.

Some vendors go beyond the handshake (Hunter's confidence score rests on the number and freshness of web sources where an address appears), but their accuracy claims are measured on their own data and we could not test them.

How common are catch-all addresses?

Published estimates disagree. All come from companies that sell verification or email-finding tools. We read each figure on 17 October 2026.

The numbers differ for several visible reasons: the unit (domains, addresses or checks), the audience (the Fortune 500 is not a typical small firm), whether providers that refuse to answer are counted, and the sample. Where vendors describe their data, none is a random sample of business email domains.

A cautious planning range is one address in five to one in three on a typical B2B list, more if you sell to large companies. It is an assumption, not a measurement, and BounceZero's stricter count came out far lower. Replace it with a count of your own list.

What catch-all addresses do to your bounce rate

The clearest measurement we found is from Hunter: it sent the same campaign to 100 accept-all addresses and 100 addresses verified as valid, and 27% of the first group bounced against 1% of the second. That is one small experiment by a vendor, so treat it as a warning, not a benchmark.

What a bounce costs is easier to look up. Amazon SES recommends keeping the bounce rate below 2%, puts an account under review at 5% and may pause sending at 10%. For complaints it recommends staying below 0.1% and reviews accounts at 0.1% or more.

Those lines apply to SES accounts, not to your own mailbox, but they are explicit public numbers. We found no published bounce limit for an ordinary Google Workspace or Microsoft 365 mailbox. Google's sender guidelines set a spam-rate target instead (below 0.10%, never 0.30% or higher) for mail to personal Gmail accounts. More in our guide to what Gmail, Yahoo and Outlook require.

Here is the arithmetic for a hypothetical team with 600 contacts: 480 confirmed valid, bouncing 0.5% (an assumption), and 120 catch-all. If all 120 are sent, the blended bounce rate depends on how the catch-all addresses behave:

The same team limited to a 10% share would send 53 catch-all addresses. At 27% that still produces about 3.1% overall. A cap limits the damage, and only a test tells you whether the segment is worth sending.

Should you send to catch-all emails? A rule by list size and risk

Send some of them, in a measured share, from an established mailbox. Skip them on a new or fragile one.

Two facts drive the rule. A catch-all address has an unknown bounce rate until you send to it. And you cannot measure a rate on a handful of sends: with zero bounces in n sends, the 95% upper bound on the true rate is about 3 divided by n (the rule of three, a good approximation above 30 sends). Zero bounces in 30 sends leaves a ceiling near 10%. It takes about 100 sends to reach 3%, and 300 to reach 1%.

Hunter suggests keeping accept-all addresses to 2% to 5% of a list. We treat 10% as the outer limit for a mailbox with a clean history. With 90% valid addresses bouncing at 0.5% and 10% catch-all addresses bouncing at 15%, the blended rate is 1.95% (0.9 x 0.5% plus 0.1 x 15%), just under 2%. It is a rule of thumb, not a standard, and it is also FoxKnock's default cap.

The table assumes an established mailbox with a clean recent history. On a new mailbox still ramping up, with a bounce rate already above 1%, or on a domain you cannot replace, exclude catch-all addresses (QuickEmailVerification likewise advises none during warm-up). For a short list of accounts worth the risk, send every address that has a second signal, whatever the share, under the stop rule below. The 10% share and the 1% flag are our rules of thumb, not published standards.

A 100-send test with a bounce stop rule

1. Rank by source. Put addresses the person gave you or the company publishes first, guessed patterns last. Never send to purchased, scraped or very old lists.
2. Send up to 100, in tranches of about 25 over several days. With a smaller list, keep a running tally across campaigns. Never send catch-all addresses first in a campaign, and keep to your normal daily volume (see how many cold emails per day).
3. Wait before judging. Bounces on these domains can arrive late. Read each tranche about three days after its last send. QuickEmailVerification describes delayed bounces arriving 72 hours or more after a send, so treat three days as a minimum.
4. Apply the lines below, and suppress every hard bounce immediately. If two addresses at one catch-all domain bounce, pull the rest of that domain from the test. That is our judgment, not a published rule.

The thresholds in this table are our rules of thumb, built on the SES lines above. They are not published standards.

What to do instead of guessing

Find a second signal

A second signal is evidence, other than the server's yes, that this person reads this mailbox. SimpleVerifier ranks risk by where an address came from. Our version, strongest first:

• Given to you: a reply, a form fill or a business card.
• Published with the person's name on the company's site, a conference page or a byline.
• Found with a source you can open, or scored on several fresh web sources. Hunter says a score of 85 to 100 can be treated as valid but is still slightly more likely to bounce.
• A confirmed pattern: another person at the same domain has replied to you from an address in the same format. A pattern guessed with no confirmation is high risk.

Hunter also reports that Google-hosted addresses that Google Sheets converted to people chips bounced 0% against 56% for those that did not. It is one writer's experiment and sample sizes were not stated, so treat it as an idea to test. For more on finding addresses, see how to find someone's work email.

Use a different channel

For accounts worth reaching where no second signal turns up, call, send a LinkedIn note you write and send by hand, use the company's contact form, ask a mutual contact for an introduction, or reply in a public thread where the person is already asking. Hunter suggests other channels for the same reason. A hard bounce counts against your sending reputation. A call or a hand-sent note does not.

If an address does bounce, remove it and stop sending to it at once, as SES advises.

How FoxKnock handles catch-all addresses

FoxKnock finds work emails with a waterfall of finders and verifies them with in-house checks (syntax, disposable domains, MX records) and then third-party verification providers. If a provider reports an address as catch-all, FoxKnock stores it as catch-all, not as valid, and a pattern guess is never reported as valid. Each field records its provider and its source URL when there is one, so you can rank by source. At default credit prices (they may change), a find that ends in a catch-all address is charged like one that ends valid. See pricing and the email finder page.

Two guardrails apply by default:

• Catch-all policy (Settings, Compliance): either never email catch-all addresses, or allow them up to a share of each sequence, set to 10% by default and adjustable. The share is checked when you enroll contacts, and addresses over it are skipped with the reason shown.
• Bounce auto-pause: a mailbox pauses itself when more than 2% of its last 100 sends bounced, once it has at least 20 sends. With 20 sends, one bounce is 5% and pauses it. With 100 sends it takes three.

A hard bounce marks the address invalid, suppresses it and stops its sequences. The email-find credits FoxKnock charged for that address are refunded once. Late bounces arrive as bounce emails in the sending mailbox, so FoxKnock sees them through that mailbox's IMAP sync.

FoxKnock connects mailboxes with an app password over SMTP and IMAP: Google Workspace or any SMTP and IMAP mail server. Microsoft 365 is limited. Microsoft no longer accepts passwords for IMAP in Exchange Online and is retiring them for SMTP AUTH, so a Microsoft 365 mailbox may not connect or may not sync bounces and replies, and FoxKnock does not offer Microsoft sign-in. On such a mailbox, check bounces in the mailbox yourself.

These are guardrails, not a test: the pause watches each mailbox as a whole, so count the catch-all group's own bounces yourself. FoxKnock cannot make a catch-all address verifiable, and no tool can promise inbox placement. On LinkedIn, FoxKnock drafts the note and you send it.

This guide covers deliverability, not law. Whether you may email a person at all depends on their country and your lawful basis, and nothing here is legal advice.

To see how this works on your own contacts, create a free account. The free plan includes 500 one-time credits (granted after you verify your email) and needs no card. Find and verify a few addresses, then look at the status and source recorded on each.