You verify an email address, it comes back "valid" — and it still bounces two weeks later, or worse, disappears into a spam folder no one ever checks. A common cause: the domain is catch-all, and standard verification can't see through it.
The short answer
A catch-all (also called accept-all) email address is any address at a domain configured to accept mail sent to any username, whether or not that specific mailbox exists. If hello@company.com, asdf1234@company.com, and a genuine typo like jonh@company.com all get accepted by the mail server, company.com is catch-all.
The domain isn't broken — it's a deliberate mail server setting, usually so the company never bounces a legitimately misspelled address (jon@ vs john@) or an old alias someone forgot to remove.
Why it matters for you
Normal email verification works by asking a mail server, in effect, "does this specific mailbox exist?" (technically, an SMTP RCPT TO handshake). On a normal domain, the server answers honestly — yes or no — and that's most of what a verifier relies on to call an address "valid."
A catch-all domain answers "yes" to everything, including addresses nobody actually reads. That means:
- A "valid" result doesn't mean the mailbox exists. It means the domain accepts anything, which is a much weaker signal.
- You can't detect a typo this way.
jane.smith@company.comandjame.smith@company.comwill both verify "clean" on a catch-all domain, even if only one is real. - Bounces get deferred, not prevented. Some catch-all servers accept the message at the SMTP level, then silently drop or bounce it later (a "soft bounce" or backscatter) — which shows up in your sender reputation days after you already sent the campaign.
How to tell if a domain is catch-all
| Method | What it tells you |
|---|---|
Verify an address you're confident doesn't exist (e.g. zzz-nonexistent-xyz@company.com) via a tool that actually attempts an SMTP mailbox probe |
If it comes back "accepted," the domain is catch-all — this is the only direct test |
| Check for unusually high acceptance rates in bulk lists | If every single address at one domain verifies clean, that's a catch-all tell, not a coincidence |
| Look at the mail provider | Some hosting setups enable catch-all by default, so a small company may run one without choosing to — treat it as a hint, never proof |
One honest caveat, and it applies to most free verifiers, including ours: real-time SMTP mailbox probing (the RCPT TO handshake above) is blocked by most cloud hosts and refused or faked by most mail servers — which is the exact mechanism that makes catch-all domains possible in the first place. So a verifier that skips SMTP probing entirely (checking format, MX, disposable and role status instead — which is what the LeadQuasar Email Verifier does) genuinely can't tell you whether a domain is catch-all. It still catches the majority of bad addresses — dead domains, disposable providers, typo'd formats — just not this specific failure mode. Treat "not flagged as catch-all" from any such tool as "unknown," not "confirmed not catch-all."
What to actually do about a catch-all address
A catch-all result isn't a reason to throw the contact away — some of your best prospects sit behind catch-all domains. It just means you can't lean on verification alone. In order of effort:
- Confirm the pattern independently. If you already have one verified email at the company (
first.last@company.com), and your target uses the same visible pattern elsewhere (LinkedIn, a press release, a GitHub commit), confidence goes up even without a clean SMTP check. - Send low-risk first. A single, well-targeted first email does less damage to your sender reputation than a bulk blast if it bounces. Don't put unverified catch-all addresses straight into a large automated sequence.
- Watch engagement, not just bounces. On a catch-all domain, "no bounce" tells you nothing — a reply, an open, or a click is your first real confirmation the mailbox is live.
- Start from data that already accounts for this. LeadQuasar holds 7.5 million+ B2B records across 170+ industries, each with a 0–100 quality score you can see before you unlock it, so you have a stronger starting signal than a fresh, unverified catch-all guess.
Frequently asked questions
What is a catch-all email address?
A catch-all (or accept-all) email address is any address at a domain whose mail server is configured to accept mail sent to any username, including ones that don't correspond to a real mailbox. It's a server-level setting, not a property of one specific address.
How do I know if an email is catch-all?
The direct test is verifying an address at the same domain that you're confident doesn't exist — something like zzz-test-12345@company.com — through a tool that performs a real SMTP mailbox probe. If it comes back accepted, the domain is catch-all. Most cloud-hosted, no-signup verifiers (including the LeadQuasar Email Verifier) skip SMTP probing entirely, since most mail servers block or fake the response — so they can rule out disposable, malformed, and dead-domain addresses, but can't confirm or rule out catch-all specifically.
Are catch-all emails bad for deliverability?
Not inherently — but they're riskier because verification can't confirm the specific mailbox exists. Sending to a genuinely wrong address at a catch-all domain can still bounce (sometimes as a delayed "soft bounce"), which hurts your sender reputation the same as any other bad send. Treat catch-all addresses as unverified rather than invalid.
Should I remove catch-all addresses from my list?
No — removing them throws away real prospects along with bad guesses. Instead, confirm the address pattern independently where you can, send to catch-all contacts with lower initial volume, and watch for engagement (opens, replies, clicks) as your real signal that the mailbox is live.
Catch the typos, dead domains, and disposable addresses before you send: LeadQuasar Email Verifier, free and no signup.