Article
How Accurate Are Email Verifiers on Catch-All Domains?
By Unlimited Verifier Team ·

Summary
Email verifiers can usually flag a catch-all domain, but they cannot confirm whether a specific mailbox exists there, because the server accepts any recipient during the SMTP check. Treat catch-all results as Risky and release them in small, engagement-ranked waves based on your own sending data.Most email verifiers can flag a catch-all domain, but they cannot confirm whether a specific mailbox exists there, because a catch-all server replies 250 (accepted) to any recipient during the SMTP check. Treat every catch-all result as Risky until your own sending data says otherwise. For the wider picture, see our email verifier accuracy pillar.
"Accuracy" hides two different questions. One is whether a tool correctly identifies an accept-all server. The other is whether its label on a single address matches what happens when you mail it. The first can be highly consistent. The second cannot be measured from the SMTP probe, and it is where most vendor accuracy claims stop applying. This guide separates the two, shows you how to measure what matters on your own list, and gives a decision rule for the addresses in the middle.
Quick answer
- Detection: Most verifiers flag a catch-all domain by probing a made-up address on it. Greylisting, rate limits and inconsistent servers are where detection goes wrong.
- Mailbox confirmation: The SMTP probe cannot confirm a specific mailbox on an accept-all server. A Valid label there is an inference.
- Routing rule: Keep catch-all addresses out of your first sends, then release them in small, engagement-ranked waves.
- Sample size: 9 bounces in 500 sends (1.8%) has a 95% range of roughly 0.9% to 3.4%, so small tests can mislead in both directions.
- Cost: Pro's 25,000 deep checks a month at $29 works out to $1.16 per 1,000 at full use ($1.00 on annual billing).
What is a catch-all domain, and why can't SMTP settle it?
A catch-all (accept-all) domain is one whose mail server accepts messages for any local part, so anything@company.com gets a successful reply even if no such mailbox exists. A verifier checks an address by opening an SMTP session and issuing RCPT TO for it. RFC 5321 defines the exchange: a server that knows the mailbox replies 250, and one that doesn't replies with a 5xx code such as 550.
On a standard domain, a 550 with enhanced status code 5.1.1 from RFC 3463 means "bad destination mailbox." On a catch-all, the server has already said yes, so the verifier never learns what happens next. Whether the message reaches a person, is silently discarded, or bounces later is decided after the probe ends.
That last possibility matters for your metrics. Some accept-all servers take a message and discard it without sending any bounce. A clean bounce report therefore doesn't prove delivery, which is why engagement has to judge catch-all addresses alongside bounce counts.
Catch-all configurations are common for practical reasons. Businesses use them so misspelled addresses aren't lost, to route mail through forwarding rules, or because some hosted mail platforms enable them by default. Large consumer providers generally reject unknown recipients during the SMTP conversation, so catch-all results cluster in business domains.
Bottom line: A catch-all server answers before the mailbox question is asked, so the probe cannot separate a live inbox from a dead one.
How accurate is catch-all detection compared with mailbox classification?
Detection can be reliable. Classifying an individual mailbox on an accept-all domain cannot be measured with the probe. Keep these separate whenever you read an accuracy claim.
Most verifiers test an accept-all server by probing a random local part on the same domain, one that almost certainly doesn't exist. If the server accepts it, the domain is flagged catch-all. This test is sound when the server answers consistently. It fails in three predictable ways:
- Greylisting and temporary errors (4xx): A server that defers the first attempt returns an inconclusive response. Some tools label that unknown rather than catch-all, so the domain's status depends on the tool's retry logic. RFC 5321 defines these 4xx replies.
- Rate limiting: Rapid probing of one domain can trigger throttling, so later addresses get different answers from the same server.
- Inconsistent servers: Some domains accept random addresses but reject certain patterns, or change configuration over time. A result can be right today and wrong next month.
Mailbox classification is different. On an accept-all domain, a real inbox and a non-existent one produce the same SMTP answer. A Valid label there can only be inferred from other signals, or tested by sending. If your tool labels such an address Valid and it later bounces, that is a false positive in practice, even though the probe did what it was built to do.
So "accuracy on catch-all domains" is an incomplete phrase. The useful version asks two questions: how reliably does the tool identify catch-all domains, and how sensibly does it route the addresses it finds?
What do the result categories mean?
| Result | What the verifier is saying | Reliability on catch-all domains | What to do |
|---|---|---|---|
| Valid (mailbox accepted, domain not catch-all) | The server accepted this mailbox and didn't accept random ones | High for detection, if the server answers consistently | Send, with normal monitoring |
| Invalid (mailbox rejected) | The server rejected this mailbox | High on standard domains; confirm the tool never labels catch-alls Invalid | Suppress |
| Risky / catch-all | The domain accepts any address, so the mailbox can't be confirmed | Detection is strong; mailbox status is unknown | Hold back, test, gate by engagement |
| Unknown / inconclusive (labels vary by tool) | No clear answer, often timeouts or temporary errors | Not a verdict | Retry later, or treat as Risky |
Unlimited Verifier sorts results into Valid, Risky and Invalid, and it detects catch-all domains. Our recommended handling is to treat flagged catch-all addresses as Risky. Before you build a send list, check your export to see which bucket each flagged row lands in. For why tools disagree on these edge cases, see why different email verifiers give different results and why does my verifier return so many unknowns.
Bottom line: Catch-all detection can be reliable. Confirming a specific mailbox on a catch-all domain cannot be done from the probe, so any Valid label on those addresses is a hypothesis to test.
What accuracy figures should you trust for catch-all domains?
Vendors usually publish one headline accuracy figure, and it rarely breaks out catch-all performance. Unlimited Verifier states 99.5% accuracy for its deep verification. That is the company's own figure, not an independent benchmark, and it doesn't say how the tool performs on accept-all domains.
Ask two questions of any accuracy claim. How was it measured? And does the test set include catch-all addresses at a realistic share of the list? Catch-all share varies widely by industry and data source, so the only reliable number is the one you measure on your own list. For the mechanics behind these figures, read how accurate is email verification really, whether verifiers really have 99% accuracy and our independent accuracy benchmark for 2026. The principles for judging vendor claims are in are vendor accuracy claims for email verifiers trustworthy.
Bottom line: A headline accuracy figure says little about catch-alls unless the vendor reports those results separately.
Can any verifier confirm a mailbox on a catch-all domain?
Not from the SMTP handshake alone. The protocol gives the same answer for real and fake addresses, so no amount of probing changes that. Some vendors describe additional signals beyond the probe. Before relying on one, ask what those signals are, whether they were validated on accept-all domains, and how they affect the final label.
You can't easily reproduce the probe yourself. Many home and cloud networks block outbound port 25, and repeated probes from a single IP can get that IP listed or throttled. For spot checks on individual addresses, use a single-address checker rather than building your own.
Bottom line: No verifier can confirm a specific mailbox on a catch-all domain from the handshake, so ask vendors what extra evidence they use and whether it was tested on catch-alls.
Why do catch-all addresses matter more for B2B and SaaS lists?
Catch-all addresses concentrate in business lists, which makes them the hardest part of cleaning SaaS and B2B databases. Consumer lists rarely have the problem, and the cost of getting it wrong runs in both directions.
Delete every catch-all and you may discard real buyers. Keep every catch-all as Valid and you concentrate bounce risk in one segment. In the worst cases, some accept-all domains are run to catch senders with poor list hygiene, so mail to them can damage your reputation. The workable answer is segmentation: decide per address using engagement and recency, not the domain alone.
Keep bounce and complaint metrics separate. Google's bulk sender guidelines recommend keeping user-reported spam below 0.10% and advise avoiding a rate of 0.30% or higher. Some guides quote 0.3% as the ceiling, which is the warning level rather than a target, so use 0.10% as your internal goal. Yahoo's sender hub sets similar complaint expectations. A bounce spike and a complaint spike need different fixes, so track them as separate numbers.
Bottom line: For B2B lists, the catch-all question is a routing problem, not a deletion problem.
How do you test a verifier's catch-all results yourself?
Run this test on your own list before you commit to a catch-all policy. It takes a few days and produces evidence no vendor page can supply.
- Isolate the catch-all addresses. Verify the full list, then filter the flagged catch-all rows and group them by domain.
- Rank them by engagement. Add last-open or last-purchase dates to the export, and start with contacts who engaged recently.
- Draw a sample of about 500. Smaller samples are too noisy to separate a real problem from chance. How many emails to use when testing a verifier covers sizing in more depth.
- Send and wait several days. Catch-all bounces can arrive late, or never arrive, so don't judge from a few hours of logs.
- Calculate the rate with an honest interval. Nine bounces in 500 sends is 1.8%. The common normal approximation, 1.96 × √[p(1−p)/n], gives ±1.2 points. That understates the uncertainty at small counts. The Wilson score interval, which handles small counts better, puts the 95% range at roughly 0.9% to 3.4%.
- Set the release rule before you look. Release the next wave if the sample rate is under 2%. Pause and investigate between 2% and 3%. Hold anything above 3%.
The interval changes the decision. A 1.8% result passes the 2% rule, but its upper bound sits above 3%. That is why the next step is a staged release, not a full one.
| Approach | Upside | Downside | Best for |
|---|---|---|---|
| Treat all catch-alls as Valid | Maximum reach; no lost contacts | Bounce risk concentrates in one segment; hard to recover reputation | Rarely a sound default |
| Delete all catch-alls | Simplest; lowest bounce risk | Loses real B2B contacts; no evidence gathered about them | Lists with a small catch-all share or poor data quality |
| Hold, then gate by engagement | Keeps engaged contacts; limits exposure | Needs engagement data and discipline | Most B2B and SaaS lists |
| Test a sample, then release in waves | Produces your own bounce evidence | Takes days; needs monitoring | Large lists with a big catch-all share |
| Act on the Valid/Risky label alone | Fast; no sends needed | No way to check accuracy on your own data | A first filter only |
Bottom line: Test small, release in waves, and let your own bounce data set the policy.
Hands-on tutorial: segmenting catch-all addresses with Unlimited Verifier
- Export your contacts as a CSV. Include the email column and any engagement fields, such as last open or last purchase. Unlimited Verifier detects the email column automatically in CSV and Excel files up to 10MB.
- Create an account. Sign up for free to run the workflow. The Free plan covers lists of up to 150 emails, 25 lists a month (3,750 addresses in total), and 750 deep verifications a month. It has no API access.
- Upload the file. Use the upload and verify a list page. On Pro, each list is capped at 25,000 emails, so split larger files first.
- Find the catch-all rows. Filter for the catch-all flag and confirm which bucket those rows land in. Treat them as Risky, alongside any disposable and role-based addresses you want to hold back.
- Export within the retention window. Free results are kept for 24 hours and Pro results for 30 days. Export as CSV, Excel or JSON the same day you verify.
- Build segments in a spreadsheet. Sort the Risky rows by last-open date, then create three groups: engaged in the last 90 days, older engagement, and no engagement data.
- Spot-check high-value contacts with the free email checker before deciding on them.
- Re-import in waves. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so re-import the Valid segment and each released Risky wave manually. If you prefer to automate, Pro includes API access for up to 100,000 emails a month, with bulk requests of up to 10,000 emails each. See the API keys page for setup, and the email verification API and automation pattern for workflow ideas.
- Log every count. Record how many addresses fell into each bucket and segment, and keep the test results. You'll need them for your own review and for any compliance question.
Bottom line: Segmenting turns the catch-all bucket from a dead end into a plan.
Worked example: a 40,000-row B2B list on Pro
The percentages below are illustrative. The plan limits are real.
A SaaS company holds 40,000 contacts, and an illustrative 12% of them sit on catch-all domains.
- Splitting the list. Pro caps each list at 25,000 emails, so the 40,000 rows become two uploads of 25,000 and 15,000.
- Sizing the catch-all segment. 40,000 × 12% = 4,800 catch-all addresses.
- Engagement split. Suppose 1,400 of those opened an email in the last 90 days, and 3,400 have not engaged recently. 1,400 + 3,400 = 4,800.
- The test. Send to 500 of the 1,400 engaged catch-alls. Suppose 9 bounce: 9 ÷ 500 = 1.8%, under the 2% release threshold. The 95% range is roughly 0.9% to 3.4%, so the release is cautious.
- Staged release. The remaining 900 engaged catch-alls go out as two waves of 450. Suppose each wave bounces 8 times: 8 ÷ 450 = 1.8%, within the rule. Total bounces across the 1,400: 9 + 8 + 8 = 25, and 25 ÷ 1,400 = 1.8%.
- Hold. The 3,400 disengaged catch-alls stay out of promotional sends. They can enter a re-engagement sequence once the main list is stable.
- Cost. Email verification pricing varies widely, so compare per-check cost, not headline price. Pro is $29 a month, or $25 billed annually. At full use of the 25,000 deep allowance, that's $29 ÷ 25 = $1.16 per 1,000 deep checks on monthly billing, or $25 ÷ 25 = $1.00 on annual billing. Standard verification is unlimited on every plan. The Free plan's 3,750-address monthly capacity can't cover this 40,000-row list in a single month.
Bottom line: A 40,000-row list is a two-upload job on Pro, and the catch-all policy becomes a few days of staged sending rather than one blanket decision.
How should you decide what to do with each catch-all address?
Use engagement as the deciding signal, since it's the one thing the SMTP probe cannot see. Apply these rules in order:
- Engaged in the last 90 days: Include in the test sample, then release in waves.
- Engaged 91 to 365 days ago: Hold. Use only in a re-engagement sequence once the main list is stable.
- No engagement in 12+ months: Exclude from promotional sends.
- Flagged disposable: Suppress. Role-based (e.g.,
info@): Hold back, since these rarely belong to a named buyer. - Existing customer or signed contract: Confirm the address with the account owner. No tool can settle that question for you.
Verification is not consent. Recency and documented opt-in matter as much as the verifier's output, which is why email verification compliance and hygiene belongs in the same process. Keep catch-all addresses in your recurring cleaning cycle using the steps in email list maintenance best practices. For new sign-ups, real-time email validation can flag catch-all domains before they enter the list, and a catch-all email verification check can show how a given domain behaves.
Bottom line: Engagement and documented consent decide what happens to a catch-all address. The verifier's label only starts the conversation.
What are the common mistakes with catch-all verification?
- Treating catch-all as a synonym for Valid or Invalid. It means neither. It means the mailbox is unconfirmed.
- Judging a tool by its catch-all share alone. A high share of Risky results isn't an error by itself. What matters is how those addresses behave once you send.
- Calling a 50-address test proof. At that size, one bounce moves the rate by two percentage points, and the uncertainty is wide.
- Reading results too early. Late bounces can arrive days after a send, and some never arrive.
- Releasing the whole Risky bucket at once. That concentrates your bounce risk into a single day.
- Deleting every catch-all without testing. You may remove real buyers and gather no evidence either way.
- Treating inconclusive results as Valid. Retry them later, or treat them as Risky.
- Re-verifying the same list hoping the flag changes. Repeated probing doesn't create new evidence and can trigger throttling. New information comes from engagement and bounce outcomes.
- Letting Free-plan results expire. Free results are kept for 24 hours, so export the same day.
- Assuming a headline 99.5% applies to catch-alls. Ask for results broken out by domain type.
- Ignoring silent drops. A zero-bounce result from a catch-all doesn't prove the mail was read.
Bottom line: Most catch-all mistakes come from treating a probe result as a verdict, when it is a starting point for a test.
How we compared (and limitations)
This article is based on public documentation: RFC 5321 and RFC 3463 for SMTP behaviour and status codes, Google's and Yahoo's published sender guidance, Amazon SES's published bounce guidance (see its documentation), and Unlimited Verifier's published plan details. We have not run controlled tests against any verifier's catch-all behaviour, and we have not measured catch-all accuracy directly.
- The worked-example figures (12% catch-all share, 1,400 engaged addresses, 9 and 8 bounces) are illustrative, not measured results.
- Unlimited Verifier's 99.5% is the company's stated figure for deep verification. It has not been independently verified here, and it does not break out catch-all performance.
- Other vendors' catch-all methods and labels differ. For a side-by-side view, see best email verification tools and how to choose an email verifier.
- Mail server configurations change without notice, so a domain that is catch-all today may not be next quarter. Retest on a schedule rather than trusting one snapshot.
Bottom line: Use the framework here as a method, then replace the illustrative numbers with the results from your own list.
Catch-all routing rule
- Run verification and separate Valid, Invalid, and Catch-all/Risky results.
- Send Valid addresses first and suppress Invalid addresses.
- Rank catch-all addresses by past engagement (opens, clicks, replies).
- Release catch-all addresses in small waves, such as 50 to 100 per wave.
- After each wave, check bounce and complaint rates against your threshold.
- Stop releasing waves if bounces rise, and suppress addresses with no engagement after several sends.
Frequently asked questions
What is a catch-all email domain?
A catch-all domain is one whose mail server accepts messages for any local part, so anything@company.com receives a success reply even if that mailbox does not exist. This happens because the server is configured to accept all recipients and forward or discard them internally.
Can email verifiers detect catch-all domains?
Most verifiers can detect catch-all domains by probing a made-up address on the domain and seeing whether the server accepts it. Detection can still fail when servers greylist, rate-limit, or respond inconsistently, so results should be checked against your own data.
Is a Valid result on a catch-all domain reliable?
Not in the strict sense. A Valid label on a catch-all address is an inference, because the SMTP probe received a 250 reply that applies to any recipient. The mailbox may be live, dead, or silently discarded.
Why do catch-all servers accept every address?
Businesses configure catch-all servers so misspelled addresses are not lost, to route mail through forwarding rules, or because some hosted mail platforms enable the setting by default. Large consumer providers usually reject unknown recipients instead.
Do catch-all addresses bounce?
Sometimes. Some catch-all servers bounce mail to nonexistent mailboxes later, while others accept and discard it silently with no bounce. A clean bounce report therefore does not prove the message was delivered.
Should I send to catch-all addresses?
You can, but route them carefully. Keep catch-all addresses out of the first sends, then release them in small waves ranked by past engagement, and watch bounce and complaint rates before expanding.
How many emails do I need to test catch-all accuracy?
Small samples mislead in both directions. For example, 9 bounces in 500 sends (1.8%) gives a 95% range of roughly 0.9% to 3.4%, so you need larger samples before drawing firm conclusions about a tool's accuracy.
What should I do with Risky email addresses?
Treat Risky addresses as a separate segment. Mail the highest-engagement addresses first in small batches, suppress addresses that bounce or never engage, and avoid using catch-all results as proof that a specific person can receive mail.
Cut Bounces and Protect Your Sender Reputation With Unlimited Email Verification
Every invalid address you send to hurts your sender reputation and your inbox placement. Verifying your list before each send means fewer bounces, healthier deliverability, and a predictable cost. With Unlimited Verifier, standard verification is unlimited on every plan, with no per-email fees.
Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox. It also detects catch-all domains and flags disposable and role-based addresses. Export a CSV from your email platform or CRM, upload and verify the list, then re-import the clean results. You can also automate checks with the email verification API.
| Free | Pro | |
|---|---|---|
| Price | $0 | $29/month ($25/month billed annually) |
| Lists | 25 a month, up to 150 emails each | Unlimited, up to 25,000 emails each |
| Deep verifications | 750 a month | 25,000 a month |
| API access | No | Yes (100,000 emails a month) |
| Result retention | 24 hours | 30 days |
Why teams choose Unlimited Verifier
- Unlimited standard verification on all plans, including Free, with no per-email fees.
- Catch-all detection so you know which domains accept every address.
- Clear Valid / Risky / Invalid results, exportable as CSV, Excel or JSON.
- An open-source verification engine you can inspect on GitHub.
Unlimited Verifier states 99.5% accuracy for deep verification.
Create a free account and verify your next list before you hit send.
Want to test a single address first? Try the free email checker.