What is a catch-all email
A catch-all email domain is configured to accept mail for every local part. jane@company.com and this-person-does-not-exist@company.com both get a yes from the server. The second address was never created. The server takes it anyway, then drops it, files it in a shared inbox, or bounces it later.
That is why the phrase shows up in two different searches. “What is a catch-all email” is the definition. “Catch-all email verification” is the next question: can you still tell which of those addresses are real.
A syntax check cannot answer it. Any string with an @ and a domain passes. Consumer Gmail is the opposite case: @gmail.com usually rejects a mailbox that does not exist. That single-address check is the free Gmail checker.
Why verifiers say risky or unknown
A normal SMTP check asks the server if the recipient exists, then hangs up. No message is sent. On a catch-all domain the server accepts the recipient either way, so the check has nothing to report. Tools label that unknown, risky, or catch-all and leave the decision to you.
Deleting the whole bucket protects the bounce rate and throws away real people. Mailing the whole bucket protects the lead count and trains Gmail and Yahoo that you do not know who is on the list. The refusal rate, and the 2% line, are on Email bounce rate.
The useful split is not “catch-all or not.” It is which of those domains can still be resolved to a mailbox, and which ones stay unresolved no matter how many times you ask.
Which catch-all addresses can still be checked
Some providers that other verifiers mark catch-all still have a way to ask whether that account exists. Wontbounce uses those checks for Yahoo, Zoho, and Outlook, and for Google Workspace domains that accept every address. The result can be valid or invalid, not a blanket risky.
Yahoo, Zoho, and Outlook
These are the domains that show up as risky on a generic SMTP pass and as a real mailbox or a dead one when the provider can be asked directly. AOL is checked the same way on the public test list.
Google Workspace catch-all
A company domain on Google that accepts every recipient is not consumer Gmail. The mailbox can still be checked. @gmail.com itself is not this case.
The public 16-address list, and how a skipped provider changes the coverage score, is on How we test. A file that does not fit in the free credits is the bulk trial on Free email verification.
What stays unknown
A company server that accepts every address, and is not one of the providers above, does not reveal the mailbox. Acceptance is not a person. The first campaign report can look clean, then the message is dropped or bounced. Verification can still remove addresses that are clearly dead. It cannot turn that domain into a list of confirmed people.
Treat those rows as unresolved. Do not mail a guessed local part just because the domain said yes. Role addresses such as info@ and sales@ need the same caution: the inbox may be real and still be a shared mailbox nobody owns.
Authentication, complaints, and the rest of the send are in email deliverability best practices. The catch-all limit is called out there, next to permission and volume.