Catch-all email: what it is and why it matters for senders

A catch-all (accept-all) domain is configured to accept mail sent to any address at that domain, including addresses that do not exist.

How it works

A normal mail server rejects a message if the mailbox does not exist — it sends back a 550 error during the SMTP session. A catch-all server responds 250 OK to everything: asdfgh@domain.com, test123@domain.com, any string at all. The message lands in a shared inbox, gets silently discarded, or triggers a delayed bounce later.

Companies enable catch-all so typos in a recipient address do not lose mail — someone sending to jon@company.com instead of john@company.com still gets through. That logic is sound for incoming mail. For outbound senders it creates a different problem.

Why catch-all breaks email validation

Standard SMTP verification works by connecting to the recipient server and asking whether a mailbox exists, without sending a full message. On a catch-all server the answer is always yes, regardless of whether the mailbox is real. So the verification returns a false positive, and the address passes as valid.

When you actually send to one of those addresses, two things can happen. If the mailbox is real, the message arrives normally. If it is not, the server may drop it silently, route it to a spam trap, or generate a delayed bounce hours or days later. You will not know which outcome to expect until after the send.

B2B email databases can carry 23–31% catch-all addresses. Their actual deliverability varies from about 40% to 85% depending on the domain. Treating catch-all addresses the same as confirmed-valid ones can push your campaign bounce rate over 2%, the threshold at which major providers start deferring your mail.

How validators detect catch-all

You cannot confirm whether a specific mailbox exists on a catch-all domain. You can, however, detect the catch-all configuration itself. A validator sends an SMTP probe to a deliberately random address at the domain — something like xkq7r2@domain.com. If the server accepts that, it accepts everything, and the domain is flagged as catch-all. From that point on, any address at that domain gets the same flag, regardless of whether the local part looks real.

Catch-all in uChecker

uChecker detects catch-all domains and marks each address from those domains with its own status in the validation results. You can see at a glance which addresses in your list belong to catch-all servers, then decide how to handle them — send, skip, or route them to a separate campaign with a lower-risk sending domain. That is a better position than discovering the problem from a bounce report after the send.