What is a catch-all email?
A catch-all (or accept-all) domain is configured to accept email sent to any address at that domain, including mailboxes that don't exist. Because the mail server never rejects a recipient, standard SMTP verification can't confirm whether an individual address is real.
How catch-all domains work
Most mail servers reject delivery to addresses that don't exist by returning a 550 error during the SMTP conversation. A catch-all domain disables that rejection: instead of bouncing unknown recipients, the server accepts everything and routes it to a single inbox, a forwarding rule, or quietly discards it.
Administrators enable catch-all for convenience — so that typos like jon@company.com instead of john@company.com still arrive, or so a small team can receive mail to any departmental alias without creating each mailbox. It's common on corporate domains and on email hosting plans that include unlimited aliases.
Why catch-all breaks email verification
SMTP verification works by asking the receiving server whether it will accept mail for a given address. On a normal domain, an invalid address gets rejected and you learn the address is undeliverable. On a catch-all domain the server says yes to everything, so a positive response no longer means the mailbox exists.
This is why naïve verifiers either mark every catch-all address as valid (inflating your list with addresses that may bounce) or mark them all as risky (rejecting good corporate contacts). Neither is acceptable when a large share of B2B traffic sits behind catch-all domains.
How to handle catch-all addresses
The right approach is to detect that a domain is catch-all and then apply additional signals rather than a single SMTP probe. Mailbeam flags catch-all domains explicitly and returns an AI-derived quality score (0–100) based on syntax, domain reputation, role-based patterns, and historical deliverability, so you can accept high-confidence enterprise addresses and only challenge the genuinely risky ones.
In practice you set an acceptance threshold appropriate to your funnel: a signup form might accept scores above 60, while a cold-outreach list might require 80+. This keeps real customers from being blocked while still protecting your sender reputation.
In practice
You verify priya@acme-corp.com. The domain is catch-all, so the SMTP server accepts it regardless of whether the mailbox exists. Mailbeam returns catchAll: true with a score of 88 — high enough to accept because the syntax is clean, the domain has strong MX and reputation signals, and it isn't a role address. A score of 22 on the same catch-all domain would instead warrant a double opt-in before sending.
Frequently asked questions
Verify emails with confidence
Mailbeam handles all of this for you — syntax, MX, SMTP, catch-all, and disposable checks in one API call. 1,000 free verifications/month, no credit card.