Catch-all emails: verify, guess or skip?
Catch-all domains hide the real mailbox from every verifier. Here is how to decide when to verify, when to guess with confidence and when to skip the send.
ON THIS PAGE · 8 SECTIONS
THE SHORT VERSION
- A catch-all domain accepts mail sent to any address at that domain, so standard verification cannot confirm a specific mailbox exists there.
- 14% to 40% of a typical B2B list sits on catch-all domains, more at enterprise accounts than at small companies.
- Sending blind to an unresolved catch-all address is far riskier than sending to a verified one. Treat it as a separate lane, not a coin flip.
- Verify, guess or skip is a decision you make per account tier, not once for the whole list.
- Pattern confidence, a second data source and a manual check recover most of the good addresses a verifier alone has to leave unresolved.
Catch-all emails: verify, guess or skip? The honest answer is that you do all three, split by how much the account is worth. Verification tools cannot confirm a specific mailbox on a catch-all domain, full stop, so treating every catch-all result the same way either burns good accounts you skip for no reason or burns your sending domain on accounts that were never worth the bounce risk.
This piece covers what a catch-all domain actually is, why no verifier can fully resolve it, how big the problem really is on a normal B2B list, the three ways teams handle it and a framework for picking the right one per account instead of guessing the same way every time.
What a catch-all domain actually is
A mail server is catch-all, sometimes called accept-all, when it is configured to accept mail sent to any address at that domain whether or not that specific mailbox exists. Send a message to a made-up address at a catch-all domain and the server still returns a success code. It never bounces at the protocol level, so you cannot tell from the server's response alone whether john.smith@company.com is a real inbox or a typo that happened to land on a server that says yes to everything.
Companies run their mail this way for a mix of reasons. Some use it on purpose to block the exact kind of address-guessing a cold outreach tool does. Others inherit it from a security gateway or a migration that never got cleaned up. Either way, the practical effect is the same: the usual verification signal disappears and every address at that domain comes back labeled catch-all instead of valid or invalid.
Why standard verification can't resolve it
Most verification tools lean on an SMTP check. The verifier connects to the receiving mail server and sends a RCPT TO command for the address in question, without ever sending the actual message. On a normal domain the server answers honestly: a real mailbox returns a success code, a fake one returns a rejection. That single exchange is enough to call the address valid or invalid.
On a catch-all domain every RCPT TO comes back with the same success code, real mailbox or not. The protocol gives the verifier no second question to ask. That is the whole limitation in one sentence: SMTP tells you the domain accepts mail, not that the specific person you are trying to reach actually has an inbox there. A verifier that is honest about this will label the result catch-all or risky rather than pretending to know. That honesty is exactly why the result looks less useful than a clean valid or invalid.
FROM THE YARD
Watch out for prospecting tools that export catch-all addresses as "verified." Several popular platforms soften the label at export time because an unresolved result looks bad in a demo. Check the raw status field, not the summary column, before you trust what you were handed.
How big the problem actually is
This is not a rare edge case you can ignore. On most B2B lists, a meaningful share of contacts sit on a domain where the standard check simply cannot confirm the individual address. That share climbs with company size because larger organizations are more likely to run a security gateway or a catch-all mail policy.
Source: QuickEmailVerification, 2026
That range is wide because it depends on your market. A list of startups and mid-market software companies skews toward the low end, since smaller mail setups tend to reject unknown addresses outright. A list weighted toward enterprise accounts, government-adjacent organizations or any company running a managed security gateway skews toward the high end. If you have never pulled the catch-all rate on your own list, do that before you plan around someone else's average. Our piece on waterfall enrichment covers how a second or third data source changes the picture. Catch-all rate is one of the numbers that shift most between providers.
Three ways teams handle it
Almost every team lands on one of three approaches once they notice catch-all addresses in their export. Each one is defensible on its own. None of them is correct for every account on your list.
| Approach | What it actually does | Main cost | Fits best when |
|---|---|---|---|
| Verify everything, drop the rest | Keeps only addresses a verifier can confirm outright | You lose real contacts at every enterprise-heavy account | High volume, low value per account |
| Guess with confidence signals | Sends to a catch-all address only when pattern match, enrichment and a second source agree | Needs a second data source and a review step | Mid-tier accounts worth a careful shot |
| Skip and verify by hand | A person checks LinkedIn, the company site or calls the front desk before anyone sends | Slow, does not scale past a short list | Named strategic accounts |
None of the three rows is the universal right answer. The account's value and the volume you need to hit decide which row applies.
A decision framework by account tier
The fix is to stop treating catch-all as one bucket and start routing it by what the account is worth. This is the sequence we run.
- Tier the account first. You should already know which accounts are tier one, worth a slower and more careful approach. Volume tier accounts, where speed matters more than any single contact, are different. If you have not built that tiering yet, start with how you scored the account during market mapping, not with the verification result.
- Set a confidence floor per tier. Tier one accounts get the full check: pattern confidence, a second enrichment source and a human glance at LinkedIn before anyone sends. Volume tier accounts get a lower bar, usually pattern confidence plus one corroborating source. Short of that, they get skipped entirely.
- Route, don't guess uniformly. An address that clears the floor for its tier goes into the send. One that does not gets skipped for that account, not for the whole list.
- Cap catch-all volume per send. Even confident guesses carry more bounce risk than a verified address. Keep catch-all sends to a small share of any single day's volume so a bad batch cannot move your bounce rate on its own.
- Review the bounce data weekly, split by catch-all versus verified. If your catch-all bounce rate on guessed addresses creeps toward your verified rate, your confidence signals are working. If it stays far higher, tighten the floor or drop that tier back to skip.
What actually improves the guess
A plain pattern guess, first name plus last name at the domain, is not good enough on its own to send against a catch-all result. A few checks stack the odds in your favor without slowing you down much.
- Pattern confidence from the provider: most enrichment tools report how often a naming pattern has already been confirmed at that exact domain, not just guessed.
- A second source agreeing on the same address, pulled from a different provider than the one that returned the catch-all flag in the first place.
- A LinkedIn profile that matches the name, title and company, confirming the person is current rather than a former employee whose old address still resolves.
- Recent engagement history, if you have sent to that domain before and know which pattern actually delivered.
Stack two or more of these and a catch-all guess starts to behave closer to a verified address than a coin flip. Stack none of them and you are sending into a black box on every single record.
A catch-all result is not a dead end. It is a question the SMTP protocol cannot answer. Everything else on this list exists to answer it a different way.
Protecting the domain after you send
Whatever mix of verify, guess and skip you choose, the sending domain pays the price if you get the mix wrong. A hard bounce still counts against you whether the address was catch-all or plainly invalid. Mailbox providers do not care which one it was. Google and Yahoo automatically restrict bulk senders whose spam complaint rate crosses 0.3%. A rising bounce rate tends to drag spam complaints up with it because more of your mail lands in front of people who never asked for it.
Source: Google, Email sender guidelines, 2026
Keep catch-all sends on the same domains and inboxes you already monitor, not on a separate untracked batch. If you run the kind of sending setup we cover in our guide to outbound infrastructure architecture, add a bounce-rate split by catch-all versus verified to your weekly check. A clean overall number can hide a catch-all segment that is quietly running hot. By the time it shows up in the blended rate, the domain reputation damage is already done.
Questions about catch-all email verification
Is it safe to email a catch-all address?
It carries more risk than a verified address but it is not automatically unsafe. The risk depends on how many confidence signals agree on that specific address. One pattern guess alone is risky. A pattern match confirmed by a second data source and a current LinkedIn profile is a reasonable bet for an account worth the effort.
How do I know if an email address is catch-all?
Run it through a verification tool that explicitly reports a catch-all or risky status rather than collapsing every uncertain result into valid or invalid. The underlying signal is that the receiving mail server accepts every address at that domain, which the tool detects by testing a random, almost certainly fake address at the same domain and seeing if it also gets accepted.
Do Apollo or ZoomInfo mark catch-all emails as verified?
Some prospecting tools soften the catch-all label at export, showing a general "verified" status that hides the underlying risk tier. Always check the raw verification status field in the export rather than trusting a summary column, especially before you load a list straight into a sending tool.
Should I remove catch-all emails from my list entirely?
Only for low-value, high-volume sends where a single bad batch is not worth the bounce risk. For accounts worth real effort, run the confidence checks first and send to the ones that clear your bar, rather than dropping every catch-all result on principle.
Does a catch-all result mean the company uses a security gateway?
Not necessarily. Some companies configure catch-all on purpose to stop exactly the kind of address-guessing a verification tool does. Others inherit it from a migration or a gateway they no longer actively manage. Either way the practical effect on your send is the same.
Sources: QuickEmailVerification, catch-all email statistics, 2026, Google, email sender guidelines, 2026