Turn catch-all and risky emails into real answers
A catch-all domain says yes to every address, so ordinary verifiers give up and call it "unknown". MailVet keeps going and tells you whether a real person is behind the address, usually in seconds.
What is a catch-all email?
A catch-all email address (also called accept-all) belongs to a domain whose mail server accepts messages for any address, even ones that don't exist. Send to dana@ or dnaa@ and the server answers "yes" to both.
That breaks the standard verification check. A verifier asks the server whether a mailbox exists; on a catch-all domain the answer is always yes, so it can't tell a real inbox from a typo or a person who left two years ago. Most tools label those addresses catch-all, accept-all, risky or unknown and leave the decision to you.
On B2B lists that's a large share of the file. Companies enable catch-all so they never lose mail, and lead databases are full of them, which is why so many "verified" cold email lists still bounce.
Same address. A different answer.
What you get back for an address on a catch-all domain.
- ×Sees the server accept every address
- ×Returns "catch-all", "accept-all" or "unknown"
- ×Leaves you to send and hope, or delete good leads
- ×Still charges a credit, and some charge several
- ✓Checks whether this specific mailbox is real
- ✓Returns deliverable or undeliverable with a reason code
- ✓Usually in seconds; the hard ones by webhook within minutes
- ✓One normal credit, and unknown stays free
How MailVet verifies a catch-all address
No test email is ever sent to the address, and nothing reaches the person's inbox.
- 01
Detect the catch-all
We check how the domain answers for an address that can't exist. If it accepts that too, the domain is catch-all.
- 02
Look past the handshake
We check the specific mailbox using independent signals beyond the basic SMTP reply, so the server's blanket "yes" doesn't decide the result.
- 03
Return a verdict
catch_all_verifiedwhen a real mailbox is behind the address,catch_all_no_mailboxwhen there isn't. - 04
Or say we don't know
If the signals don't agree, you get
catch_all_unresolved. It's marked unknown and costs nothing.
How catch-all checks compare
The catch-all problem is old. The answers differ on time, cost and whether you get a verdict at all.
| Tool | What happens to catch-all addresses | Time to verdict | Extra cost |
|---|---|---|---|
| MailVet | Verified to deliverable or undeliverable in the same call | Seconds; hard ones 1–6 min by webhook | None |
| ZeroBounce | Second "Verify+" pass after the main check | Up to 12 hours | AI scoring +1 credit |
| Scrubby | Sends real test emails and waits for bounces | 24–72 hours | 3 credits per address |
| DeBounce | Optional deep catch-all check | Varies | 10 credits per address |
| NeverBounce | Returned as "catchall", no further check | n/a | n/a |
| Kickbox / Emailable | Marked "risky" with a quality score | n/a | n/a |
From each vendor's public docs and pricing pages, checked November 2026.
Where catch-alls cost the most
Lead database exports
Exports from Apollo, ZoomInfo or Sales Navigator scrapers are heavy on catch-all domains. Verify before the list touches your sending domains.
CRM contacts
Contacts go stale as people change jobs, and a catch-all domain keeps accepting mail for them. Re-verify before every campaign.
Client lists
One bad client list can burn shared infrastructure. Verify every list on intake and keep the report as proof.
Candidate outreach
Company domains are often catch-all. Know which work addresses are real before you send a sequence.
Should you send to catch-all emails?
If MailVet returns deliverable with catch_all_verified, yes: treat it like any other deliverable address. If it returns undeliverable with catch_all_no_mailbox, remove it.
For the small set that stays unknown, the safe options are to re-run them later, send at low volume from a separate warmed domain, or skip them. What you shouldn't do is send a large unverified catch-all segment from your main domain: bounces add up quickly, and inbox providers judge senders on them.
Catch-all email questions
What is a catch-all email address?
An address on a domain configured to accept mail for any address at that domain, whether or not a mailbox exists. Because the server accepts everything, a basic verification check can't tell real addresses from fake ones.
How do you verify a catch-all email?
MailVet first confirms the domain is catch-all, then checks the specific mailbox with independent signals beyond the server's blanket SMTP 'yes'. The result is deliverable (catch_all_verified), undeliverable (catch_all_no_mailbox) or, when the signals don't agree, unknown and free.
Are catch-all emails valid?
Some are and some aren't. That's the point: the domain accepts everything, so 'valid' depends on whether a real person has that mailbox. That's exactly what the catch-all check answers.
Is catch-all the same as accept-all, risky or unknown?
Usually. 'Catch-all' and 'accept-all' describe the domain's setup. Many tools export those addresses as 'risky' or 'unknown'. If you have a file of them from another verifier, upload it here to get definite verdicts.
Do you send emails to verify catch-alls?
No. Nothing is sent to the address and nothing reaches an inbox. Tools that send real test emails take days and can hurt your sending reputation.
How accurate is catch-all verification?
No verifier is perfect on catch-alls, and we won't claim 100%. When the evidence isn't strong enough we return unknown, for free, rather than guess. We're publishing our own benchmark with its method so you can judge for yourself.
How much does it cost?
The same single credit as any other verification: $10 for 10,000 emails on Starter, less on Growth. There's no catch-all surcharge, and unresolved addresses cost nothing.
Got a file full of "unknown" from another verifier?
Upload it here. You'll see how many become deliverable, how many are dead, and you only pay for definite answers.
Related
Last updated November 13, 2026