A catch-all domain is set up to accept email sent to any address at that domain, whether the mailbox exists or not. jane.doe@company.com, jdoe@company.com and nobody-here@company.com all look accepted.
Why companies use catch-all
Companies turn it on so they never miss a message: mail sent to a misspelled name, a former employee or an old alias still arrives somewhere. Some mail setups and security filters also accept everything at first and sort it out later.
It's common. A large share of business domains, especially at mid-size and enterprise companies, behave this way.
Why it's a problem for verification
A normal verification asks the receiving mail server whether a mailbox exists. A catch-all server says yes to every address, so the answer tells you nothing about the one you care about.
That has two consequences:
- Hidden bounces. The server accepts the address during the check, then the message bounces or is quietly dropped when you actually send. These bounces still count against your sender reputation.
- Lost leads. Many tools mark every catch-all address as "unknown" or "accept all", and teams throw those rows away, including the real, reachable people in them.
How filtrat handles catch-all
- Detection is free. When a domain accepts any address, the result is Catch-all and you pay nothing for it.
- You choose what to resolve. Catch-all resolution runs a deeper check on one specific mailbox and returns a definite answer: deliverable or invalid. It costs 5, only when it gets that answer.
- Unresolved stays free. If even the deeper check can't decide, the address stays Catch-all and you aren't charged. See When an address can't be resolved.
How to tell a domain is catch-all
- A verification returns the status Catch-all, and the SMTP mailbox check reads Catch-all server.
- The Catch-all domain field reads Yes in the domain intelligence panel, in Domain intel and in the email finder's results.
- In a downloaded bulk file, the
catch_allcolumn isTrue.
What to do with catch-all addresses
| Situation | Suggested approach |
|---|---|
| High-value contacts, small numbers | Resolve each one before sending. |
| A large list with many catch-all rows | Look up the domain's email pattern first, then resolve the addresses that match it. See Look up a domain's email pattern. |
| Addresses that can't be resolved | Send carefully, in small batches, or leave them out of high-volume sends. |
When you find emails rather than verify them, turn on Resolve catch-all domains in the finder. You then get confirmed addresses on catch-all domains instead of best guesses. See Found, catch-all unverified, not found.