Catch-all emails explained

A catch-all domain accepts mail for every address at that domain, whether or not a mailbox with that name exists. Because its mail server says "yes" to any address during a check, no verifier can confirm a specific mailbox there without actually sending a message.

Why domains are catch-all

Organisations turn catch-all on so that mail with a misspelled name still reaches someone, to collect mail for former employees, or because their mail provider is set up that way by default. Some route everything to one shared inbox; others accept the message first and bounce it later.

What it means for verification

During a check, the mail server answers the same way for jane@example.com and for xq7-not-a-person@example.com. The check therefore cannot tell you whether Jane's mailbox exists. In email-validation.org such results are:

• risky with the reason catch_all, action send_with_caution;
• risky with role_catch_all for team addresses such as sales@ on a catch-all domain;
• deliverable with trusted_catch_all when the domain accepts every address but mail sent to it has a strong record of arriving.

How to handle catch-all results

1. Keep them in their own segment so their bounces do not hide among your confirmed addresses.
2. Send to them when they matter: a customer who just signed up, a lead from a known company. Be more careful with old or purchased lists.
3. Watch the first send. If a catch-all segment produces hard bounces or no engagement at all, suppress the addresses that bounced and slow down.
4. Use engagement over time. An address that opens or replies is real; one that never does after several sends is worth removing.
5. Confirm at capture. For sign-ups, a confirmation email settles the question for that person.

Catch-all is not the same as risky in general

Other risky reasons, such as disposable inboxes, spam traps or frequent complainers, carry the action remove. Catch-all results are different: many of them are perfectly good addresses that a check simply cannot confirm.

Related

• The risky status and every risky reason.
• How to reduce your email bounce rate.
• Glossary: catch-all domain.

How we wrote this: drafted by the email-validation.org team with the help of AI writing tools, from our product documentation and the sources linked in the text.