What is a catch-all email domain — and should you send to one?

Catch-all domains accept every incoming message whether or not the mailbox exists. That makes them impossible to verify with SMTP alone. Here's how to identify them and decide whether to include them in your sends.

A catch-all domain — also called an accept-all domain — is a mail server configured to accept any email sent to any address at that domain, regardless of whether the mailbox actually exists. From the outside, there is no way to tell whether [email protected] and [email protected] both exist, or if only one does, or if neither does. The server says yes to everything.

Why domains use catch-all configuration

Catch-all is often configured intentionally by businesses that want to ensure they never miss an email due to a typo in the recipient address. An IT admin might set it up so that misspelled variations of employee addresses still get delivered. Small businesses sometimes use it as a general catch bucket for all inbound mail.

The problem for email senders

When you're building a marketing list or prospecting outbound, catch-all addresses look exactly like valid addresses during verification. Your validation tool returns CATCH_ALL — not VALID, not INVALID. If you send to a catch-all address where the mailbox doesn't exist, the receiving server might silently discard the message, bounce it asynchronously (a delayed bounce that your ESP sees as a hard bounce), or deliver it to the catch-all inbox where no one reads it.

Catch-all domains typically make up 8–15% of B2B contact lists. They can't be confirmed — they can only be tested.

The test-and-observe strategy

The only reliable way to assess catch-all addresses is to send to them and observe. Create a separate segment of your catch-all addresses and send them a low-stakes email — an onboarding message, a newsletter. Watch your bounce reports for the next 72 hours. Addresses that bounce hard should be removed immediately. Addresses that deliver without complaint can be moved to your main list.

Should you include catch-all addresses?

• For high-volume marketing sends: exclude until tested
• For one-to-one sales outreach: include — the risk per send is low
• For transactional email: include — you need to reach the user regardless
• For list-building and lead gen: flag internally but don't block sign-up