Catch-All Email Verifier: How to Check Catch-All Addresses
By Aria Pramesi, founder of InboxPolicy · Updated November 12, 2026
Looking for a catchall email verifier or a quick catch all email checker? Catch-all domains, also called accept-all domains, accept mail sent to any address, so no verifier can confirm a specific mailbox by SMTP response alone. An accept-all domain is functionally the same problem under a different name. A large share of B2B email addresses sit on catch-all domains. Use the free check below to validate catch-all emails at the format and MX level, then get an honest send / review / avoid decision, InboxPolicy never guesses a catch-all address is safe.
Check an email address
Free format + MX check, runs in your browser. No signup.
Why can't SMTP verify a catch-all address?
A catch-all domain is configured to accept mail sent to any address at that domain, whether or not a specific mailbox exists behind it. When a verification engine opens an SMTP session to check a mailbox on a catch-all domain, the mail server accepts the recipient regardless of whether the exact address is real, made up, or mistyped.
That means the one signal most verification tools rely on, an SMTP accept or reject response, doesn't distinguish a real mailbox from a nonexistent one on these domains. InboxPolicy's engine still runs the full sequence, syntax, MX, and live SMTP, but on a catch-all domain the SMTP step returns evidence that can't confirm the specific mailbox either way.
Why catch-alls bounce even though the server "accepted" your mail
A catch-all domain accepts RCPT TO for any address at that domain, real mailbox or not: an SMTP accept means "this domain doesn't reject at the edge," not "this person exists."
What happens next depends on internal routing you cannot see from outside. Some servers route unmatched addresses to a real inbox someone monitors. Others silently drop the message with no trace. Others queue a delayed non-delivery report (NDR) that fires hours or days later, after your sending platform already logged the message as delivered. That is the mechanism behind catch-all bounces despite the server saying yes: the rejection is downstream rather than at SMTP time, and it can land after you have already sent follow-ups two and three to the same address.
The real trade-off: skip them all vs. send to all
Catch-all domains account for a large share of B2B addresses. On many outbound or cold-email lists, a substantial portion of contacts come back with an unresolved mailbox status. Treat "catch-all" as automatically unsafe and skip every one, and you delete a large share of your addressable pipeline before sending a single email, with no address-level data behind that cut.
Go the other direction and send to every catch-all address as if it were verified valid, and you gamble sender reputation on domains where you have zero mailbox-level confirmation. Push your bounce rate past what your ESP or mailbox provider tolerates, and the damage drags deliverability down for your entire sending domain, including the addresses you verified cleanly. Neither "skip them all" nor "send to all" is a strategy — both apply a category-wide rule to an address-level problem.
A routing framework for catch-all addresses (and what InboxPolicy returns)
InboxPolicy tags normalized signals with catch_all: true (reason_code: "catch_all", billed as a resolved domain check) and never guesses the mailbox is safe. Under InboxPolicy's policy rules, with no higher-priority condition (invalid/syntax_error → avoid, temporary_unavailable → retry_later, or disposable → avoid), a catch-all result maps to review by default (and under strict strictness), or to send_with_caution under aggressive strictness — never a silent send. Both decide_send (MCP) / POST /v1/decide and verify_email / POST /v1/verify include confidence and normalized signals for catch-all, disposable, free, and role-account status.
Once catch-all stops being a single risk tier, split results into three operational buckets using the corroborating context your workflow holds:
- send_with_caution — positive signals back the address up: an established sending domain, no freshly registered domain risk, or real engagement history (prior replies, opens, or form submissions) tied to that contact or domain.
- review — no corroborating evidence either way. This is the honest default for an uncorroborated catch-all hit until a human or enrichment step adds context.
- avoid — negative signals stack up: a newly registered domain, zero engagement history, or untrusted list provenance.
Every fresh check is $0.01 standard quote via keyless x402 (or $3.16–$5.00/1k on prepaid packs), with eligible 72-hour cache hits free. See the send-decision benchmark for worked scenarios, or the API docs to wire routing into a workflow.
How do other verification tools handle catch-all addresses?
Most verification tools return a status field rather than a send decision, so catch-all handling comes down to how aggressively they try to resolve the unknown versus how clearly they flag it. See the comparison below for what's publicly documented about each.
- MillionVerifier resolves unknowns aggressively and runs $3.90/1k at entry down to $0.45/1k at 1M volume; InboxPolicy Growth is $79 for 25,000 ($3.16/1k), while MillionVerifier's entry is $39 for 10,000 ($3.90/1k), a lower total purchase; MillionVerifier also wins on unit price at 1M ($0.45/1k) for one-shot bulk list cleaning.
- ZeroBounce and Kickbox report catch-all and other results through status fields (Kickbox adds a Sendex quality score), aimed at a dashboard workflow rather than a real-time send decision.
- Emailable is a dashboard-first verification suite built around bulk uploads and integrations.
| Tool | Entry price | Catch-all handling | Free tier |
|---|---|---|---|
| InboxPolicy | $0.01 per fresh verification (pay-per-call, x402), or credit packs from $5.00/1k down to $3.16/1k at Growth volume | Tags catch_all evidence, returns review by default or send_with_caution under an aggressive policy, never guessed safe | None; 72h cache re-verification, malformed rejection & unresolved checks cost 0 credits |
| ZeroBounce | ~$9.90/1k sub | Reports via status field; also maintains a spam-trap/abuse address database | 100 emails/month |
| Kickbox | ~$10.00 per 1,000 | Reports via status field plus a Sendex quality score | One-time free credits |
| MillionVerifier | $3.90–0.45/1k | Resolves unknowns aggressively; positioned for one-shot bulk list cleaning | Yes, free tier available |
| Emailable | ~$6.46/1k sub | Dashboard-first suite with bulk uploads and integrations; catch-all handling not detailed publicly | 250 signup credits (live pricing reviewed 2026-07-20) |
Catch-all guides
Dig into specific tools and scenarios: Apollo's catch-all domain flag explains what it means and what to do next; catch-all flags in Instantly, Smartlead, and Clay covers how the major cold-email platforms surface catch-all results; NeverBounce unknown and unverifiable codes and ZeroBounce catch-all and do_not_mail statuses map vendor codes to routing rules; and catch-all vs accept-all settles the terminology and risky-address taxonomy.
Frequently asked questions
What is a catch-all email domain?
A catch-all domain is configured to accept mail sent to any address at that domain, whether or not a real mailbox exists. Because the mail server won't reject invalid addresses at the SMTP level, verification tools can't confirm a specific mailbox by SMTP response alone. This makes catch-all domains a blind spot for any tool that only reports mailbox status.
How common are catch-all domains on B2B lists?
A large share of B2B email addresses sit on catch-all domains, though prevalence varies widely by company size, industry, and mail security stack rather than following one universal percentage. Because catch-all domains are common on business contact lists, how a tool treats catch-all results has a direct impact on list quality and sender reputation.
Are catch-all emails safe to send to?
Not as a blanket rule. The domain accepts mail for any address, so a catch-all result confirms nothing about whether the specific mailbox exists. Some catch-all addresses are perfectly safe to send to when other evidence backs them up; others should be avoided. Treating the whole category as safe, or unsafe, throws away the evidence you actually have.
Why do catch-all emails bounce after the server accepts them?
Because SMTP acceptance and mailbox delivery are two different steps. The server says yes to RCPT TO because the domain is configured to accept everything, then routes the message internally, to a real inbox, to a black hole, or to a delayed non-delivery report that fires after your sending platform already marked it delivered. The bounce happens after acceptance because that's where the actual mailbox check occurs, not at the SMTP handshake.
Do catch-all emails always bounce?
No. Most catch-all addresses correspond to real, receiving mailboxes, catch-all is a domain configuration, not a signal that the address is fake. Some catch-all addresses do bounce, but that's because catch-all can't confirm the mailbox either way, not because catch-all mail is inherently doomed.
What bounce rate do catch-all emails have?
It varies by domain, and there's no single honest number to quote here. A catch-all domain with real engagement history behaves nothing like a freshly registered catch-all domain scraped off a list. That variance is exactly why a category-wide bounce-rate figure is the wrong tool: per-address routing based on real evidence beats a guessed average every time.
Should I remove catch-all emails from my list?
Not automatically. Removing every catch-all address discards a large share of a typical B2B list for no reason beyond the label. Route them instead: keep the ones with supporting evidence such as engagement or established domain history, flag the ones with no evidence for review, and drop only the ones with real negative signals stacked against them.
Does InboxPolicy ever mark a catch-all address as safe to send?
No. InboxPolicy tags catch-all evidence with catch_all and returns the action review by default, never guessing the mailbox is valid. Under a more aggressive policy configuration it can return send_with_caution instead, but it will not silently return send for an address it cannot confirm exists.
Is a catch-all result the same as an invalid email?
No. Catch-all means the verification engine could not confirm or deny the mailbox exists because the domain accepts all mail. It is not a bounce prediction. InboxPolicy separates this from malformed or clearly invalid addresses, which are rejected before any SMTP check runs and never billed.
Which tool should I use for a catch-all-heavy list I just want to clean once?
For one-shot cleaning of a large scraped list at the lowest cost, MillionVerifier runs $3.90/1k at entry down to $0.45/1k at 1M volume; InboxPolicy Growth is $79 for 25,000 ($3.16/1k), while MillionVerifier's entry is $39 for 10,000 ($3.90/1k), a lower total purchase; MillionVerifier also wins on unit price at 1M ($0.45/1k). InboxPolicy is built for per-send decisions in live agent workflows, not one-time bulk list cleaning, so pricing and workflow fit differ.
How does InboxPolicy price catch-all verifications?
Catch-all answers are billed like any confirmed check: $0.01 standard quote per fresh check via pay-per-call x402 (discounted 20% after 1,000 settled units in 30 days and 40% after 10,000), or 1 credit from a prepaid pack such as Starter ($5 for 1,000 credits) or Growth ($79 for 25,000 credits). An eligible cache hit within 72 hours returns from_cache and costs 0 credits, even for a previously seen catch-all result; unresolved checks with no catch-all or disposable signal also cost 0 credits.
What is the best catch-all email verifier?
The best catch-all email verifier for your case depends on the job. For one-shot bulk list cleaning, a resolver like MillionVerifier is priced for that workflow. For live, per-send decisions inside an agent or outbound tool, InboxPolicy is built for that: it runs syntax, MX, and SMTP checks, tags catch-all evidence honestly, and returns a send / send_with_caution / review / retry_later / avoid decision for $0.01 per check instead of a bare status label.
How do you verify a catch-all email without sending?
You can't fully verify a specific mailbox on a catch-all domain without sending, because the SMTP server accepts RCPT TO for any address. What you can do without sending is confirm the address is well-formed and that the domain has valid MX records, then treat the mailbox itself as unresolved. InboxPolicy runs this full check and returns review by default, or send_with_caution under aggressive strictness, with the catch_all evidence tag rather than guessing the mailbox is safe.
Can you check if a catch-all domain will bounce?
You can check whether the domain itself is reachable, has valid MX records, and accepts mail, which rules out hard bounces from a dead or misconfigured domain. What you can't determine from SMTP alone is whether a specific mailbox on a catch-all domain exists, since the server accepts everything. InboxPolicy reports both: domain-level deliverability evidence and an honest review flag for the unresolved mailbox.
What does it mean when Apollo flags a domain as catch-all?
When Apollo flags a domain as catch-all, it means Apollo's own verification couldn't confirm the specific mailbox exists because the domain accepts mail for any address at that domain. It does not mean the address is invalid. See our guide on Apollo's catch-all domain flag for how to handle those contacts before sending.