Article
Do You Need Catch-All Verification or Just Standard Checks?
By Unlimited Verifier Team ·

Summary
Standard email checks confirm syntax, domain, MX and mailbox existence, but they cannot verify mailboxes on catch-all domains that accept any address. Use standard checks for recent opt-in lists, and add catch-all verification once catch-alls pass about 5% of a list or when the list is cold, purchased or dormant.Standard checks are enough for recent opt-in lists, but once catch-all domains pass about 5% of your contacts, or your list is cold, purchased or dormant, you also need catch-all verification. A catch-all (accept-all) domain says yes to any address, so an SMTP check generally cannot confirm that a specific mailbox exists there. Keep total bounces under 2% on every send, and manage catch-all addresses as a risk segment rather than treating them as proof of a working inbox. The 5% figure is our working threshold, not a number published by any ESP or mailbox provider.
Quick answer
- Standard checks (syntax, domain, MX and the SMTP mailbox) tell you whether an address is probably deliverable. They cannot tell you whether a catch-all domain's mailbox exists.
- Catch-all verification is a decision layer. You identify catch-all addresses, then decide whether to send, hold or remove them based on how you collected them and how recently they engaged.
- Standard checks are usually enough for recent opt-in lists where catch-alls are a small share. Add catch-all handling once they pass about 5% of a list, and for any cold, purchased or dormant list.
- Hold catch-alls back from your first sends after a cleanup or an account review. Send them last, and only to your most engaged segment.
What do standard checks actually confirm, and where do they stop?
Standard verification runs a sequence of tests, from cheap checks to one that talks to the recipient's mail server. It tells you an address is well formed and plausibly reachable. It does not tell you that a person reads it.
| Check | What it tests | What it tells you | Where it stops |
|---|---|---|---|
| Syntax | Format of the local part, the @ sign and the domain | Typos such as gmial.com or missing @ signs |
Says nothing about whether the mailbox exists |
| Domain | Whether the domain resolves and is active | Dead or parked domains | A live domain can still host dead mailboxes |
| MX records | Whether the domain publishes mail servers | Domains that cannot receive mail at all | Mail servers existing does not mean the mailbox does |
| SMTP mailbox | Whether the receiving server accepts the recipient, without sending a message | Nonexistent mailboxes on ordinary domains | Catch-all servers accept everything, so the answer is uninformative |
| Catch-all detection | Whether the domain accepts made-up addresses | Flags domains where a "valid" result is unreliable | Cannot identify which real mailbox sits behind it |
| Disposable and role flags | Known temporary-mail providers, and role addresses such as info@ or sales@ | Addresses unlikely to belong to one buyer | These are signals, not proof of a bad address |
The SMTP check is the core test. It follows the dialogue defined in RFC 5321: the verifier issues an RCPT TO command, and the receiving server answers. A positive reply means the server will accept mail for that recipient. A 5xx reply means it will not. The answer is only as informative as the server's configuration, and a catch-all server answers "yes" to everything.
Bottom line: Standard checks reliably catch mistyped addresses and dead domains, and they catch many nonexistent mailboxes. They are weakest exactly where catch-all configuration hides the mailbox.
Why does a catch-all address pass verification and still bounce?
A catch-all domain accepts mail for any local part, real or invented. When a verifier asks whether xq7-random@acme.com exists, the server says yes. It gives the same answer for jane.doe@acme.com, whether or not Jane still works there. The verifier cannot separate the two cases from the SMTP reply alone.
The failure happens after acceptance, and it takes three forms:
- The server rejects the message after the data stage, which shows up as a bounce against that send.
- The server accepts the message and sends a non-delivery report later, sometimes hours or days after the campaign.
- The server accepts the message and discards it without a bounce. This is the most dangerous case, because your bounce count looks clean while the message never reaches anyone.
Here is an illustrative calculation. Suppose a 48,000-contact send includes 6,900 catch-all addresses, and (hypothetically) 20% of those fail. That is 1,380 failures, and 1,380 ÷ 48,000 = 2.9% of the send. The catch-all segment alone breaches a 2% ceiling. The 20% is an illustration, not a measured rate, because real failure rates depend on the domain and on how the list was built.
Bottom line: For a catch-all domain, "valid" describes the domain's configuration, not the person. Treat it as a risk category, not a verdict.
When do you need catch-all verification, and when are standard checks enough?
The answer depends on three things: how the address was collected, how recently it engaged, and what share of your list is catch-all.
| Your situation | Standard checks enough? | Catch-all handling | Why |
|---|---|---|---|
| Opt-in newsletter, engaged in the last 90 days, catch-alls under about 5% | Yes | Monitor bounces by domain | Consent and recent engagement make a dead mailbox less likely to get mail |
| Transactional or account emails to customers | Usually yes | Send, track bounces by domain | Recipients expect the message and you have a direct relationship |
| Cold B2B outreach | No | Hold catch-alls; send last in small tests | No consent, and catch-alls are where mailboxes are least confirmed. See email verification for sales prospecting |
| Imported, purchased or event-scanned lists | No | Verify, then hold catch-alls | No engagement history, so more dead or misdirected addresses |
| Dormant list you are reviving | No | Hold catch-alls; send to Valid contacts only | Engagement is unknown, and a bounce spike feeds suspension risk |
| Re-entry after an account review | No | Hold all catch-alls until volume is stable | Reviewers watch your first sends closely |
Our recommended rule is that once catch-alls exceed about 5% of a list, they need their own plan, even for opt-in sends.
Where catch-alls come from matters as much as how many there are. Most teams find that catch-all status clusters in business domains, because consumer mailbox providers typically reject unknown local parts at SMTP time. A B2B SaaS list can therefore carry a far higher catch-all share than a consumer ecommerce list. That is why email verification for ecommerce and SaaS should be planned by segment, not as one average.
Bottom line: Standard checks are the floor. Add catch-all handling whenever the consent or engagement behind an address is weaker than a domain's "yes" suggests.
How do you find out what share of your list is catch-all?
Run standard verification on the whole list first. The results file tells you the catch-all result for each address, so the count comes straight from the export. Divide the catch-all count by the total row count. For example, 6,900 catch-all addresses in a 48,000-row list is 6,900 ÷ 48,000 = 14.4%.
Measure the share by segment, not just overall. An average of 6% can hide a segment at 30%, and that segment is where bounces will concentrate. Split your catch-all count by source (webinar leads versus CRM customers, for example) and by domain type.
You could probe a domain yourself by sending an SMTP test with a random local part. It is the same test a verifier runs, and some servers rate-limit or refuse repeated probes, so a verifier is the practical route. For spot checks on individual addresses, such as a key account that came back Risky, use the free single-email checker. It shows how one address was classified before you decide what to do with it.
Bottom line: The overall catch-all rate is a starting point. The segment-level rate drives the decision.
Which catch-all strategy should you pick?
Five strategies cover most situations. They trade reach against bounce exposure, so choose based on your list's history rather than a general rule.
| Strategy | Bounce exposure | Reach | Best fit | Watch-out |
|---|---|---|---|---|
| Remove all catch-alls | Lowest | Lowest; you also drop real people | Tiny lists, compliance-sensitive senders, reinstatement appeals | You discard contacts that may be valid, which can be a large share of a B2B list |
| Hold, then send engaged catch-alls last | Low and controlled | Medium | Most lists with some engagement history | Needs engagement dates in your ESP to be useful |
| Small test sends to catch-alls | Limited by test size | Medium | Catch-alls with a recent reply, purchase or known contact | Tests still create bounces, so keep them very small |
| Send everything and monitor | Unbounded | Highest | Proven opt-in audiences on domains with a strong record | One bad batch can push your total bounce rate past 2% |
| Deep-verify the catch-all subset, then decide | Depends on results | Depends on results | Large catch-all shares where you have deep-check quota to spare | A deep result is a signal to weigh, not proof that a mailbox exists |
Our default is the second row: hold catch-alls, then send to the engaged subset last. It keeps reach where engagement justifies it and caps exposure everywhere else. Use "remove all" only when losing contacts costs less than the risk, or when you are in a reinstatement review.
For a broader view of how verifiers handle these categories, see which email verifier features actually matter and questions to ask before buying an email verifier.
Bottom line: Hold the catch-alls, send to the engaged subset last, and remove them outright only when a bounce spike would cost more than the contacts you lose.
How do you run standard and catch-all verification on a list?
This tutorial uses Unlimited Verifier. Standard verification is unlimited on every plan, so the metered items are the monthly deep-verification quota and, on Pro, API volume.
- Check your row count against the plan limits. The Free plan handles 25 lists a month of up to 150 emails each. The Pro plan ($29/month, or $25/month billed annually) handles lists of up to 25,000 emails each. A 48,000-row file needs two uploads on Pro. Files can be CSV or Excel up to 10MB.
- Export your contacts as CSV. Include the email column and at least one engagement field, such as last opened, last clicked or last purchase date. Remove blank rows and obvious duplicates first.
- Sign up for an account. Use the Free plan to test a sample of 150 addresses before you commit to a full list.
- Upload and verify a list. The email column is detected automatically, so confirm it is the one you expect.
- Run standard verification. Each address is checked for syntax, domain, MX records and the SMTP mailbox. Catch-all domains are detected, and disposable and role-based addresses are flagged.
- Read the three buckets. Valid, Risky and Invalid come back as separate groups. Use the flags on each Risky address to split it into catch-all, disposable and role-based groups.
- Export the results as CSV, Excel or JSON. On the Free plan, results are kept for 24 hours, so download them the same day. On Pro, results are kept for 30 days.
- Build your send segments. Valid addresses go into your main send. Catch-alls with recent engagement go into a last-wave segment. Other catch-alls, and disposable or role addresses, go into a hold segment. Invalid addresses are suppressed.
- Re-import each segment into your ESP or CRM. There are no native ESP, CRM or Zapier integrations, so this is a manual export-and-import step, or you can call the API from your own scripts.
- Save the summary counts for each file. You will need them for reporting, and for any appeal if a bounce spike happens later.
For verification at signup or inside your own tools, the email verification API is available on Pro, with 100,000 emails a month and bulk batches of up to 10,000 emails per request. For that workflow, see real-time email validation.
Bottom line: Standard checks run on the full list, the catch-all flag sorts your risk, and only the segments you chose go back into your ESP.
What does catch-all handling look like on a 48,000-contact list?
This example is illustrative. The counts and bounce rates are hypothetical, but the arithmetic and plan limits are real.
The setup: A B2B company has 48,000 contacts, a mix of CRM customers and older webinar leads. Because the list exceeds 25,000 rows, it goes into two Pro uploads: 25,000 + 23,000 = 48,000.
Standard results:
| Bucket | Count | Share of 48,000 |
|---|---|---|
| Valid | 36,500 | 76.0% |
| Invalid | 3,100 | 6.5% |
| Risky: catch-all | 6,900 | 14.4% |
| Risky: role or disposable | 1,500 | 3.1% |
Check: 36,500 + 3,100 + 6,900 + 1,500 = 48,000.
The cost: One Pro month is $29. Across 48,000 contacts, that is $29 ÷ 48 = $0.60 per 1,000 contacts. On annual billing at $25 a month, it is $25 ÷ 48 = $0.52 per 1,000. Standard verification adds no per-email charge. For how verification costs compare across vendors, see email verification pricing. The monthly deep-verification quota is 25,000, so deep-checking the 6,900 catch-alls leaves 18,100 for re-checks.
Segmenting the catch-alls: Of the 6,900, 1,150 engaged in the last 90 days, and 5,750 did not.
The send plan:
- Wave 1: Valid contacts who engaged in the last 30 days.
- Wave 2: All remaining Valid contacts.
- Wave 3: The 1,150 engaged catch-alls, in a small test before the full wave.
- Hold: The 5,750 unengaged catch-alls and the 1,500 role or disposable addresses.
- Suppress: The 3,100 Invalid addresses.
The bounce projection: Assume (hypothetically) a 0.5% bounce rate on Valid contacts and a 20% rate on catch-alls. Bounce rate is measured against what you actually send, so the denominators below are the send counts, not the full list.
- Sending everything: Valid plus all 6,900 catch-alls, 43,400 sends. Bounces are 183 + 1,380 = 1,563, so 1,563 ÷ 43,400 = 3.6%.
- Sending the plan: Valid plus the 1,150 engaged catch-alls, 37,650 sends. Bounces are 183 + 230 = 413, so 413 ÷ 37,650 = 1.1%.
The hold-back moves the projected bounce rate from well above the 2% ceiling to about 1%, for one $29 month. The held contacts are not deleted. You can re-check them later, or re-engage them once you have a clean sending history.
Bottom line: In this example, the catch-all decision matters far more than the verification fee. Holding the least-engaged catch-alls keeps the send inside the ceiling.
What do mailbox providers and regulators expect from your list?
Mailbox providers judge your results, not your intentions. Two numbers matter most:
- Complaints: Google's email sender guidelines set the broad expectation that bulk senders keep user-reported spam low. Google's Postmaster Tools documentation points senders toward a spam rate below 0.1% and warns against reaching 0.3%. Some older sources cite 0.3% as the ceiling. Where they differ, we recommend 0.1% as your target. Yahoo's sender requirements set similar expectations.
- Bounces: Amazon SES's documentation describes a 5% bounce rate as a level that triggers review, and 10% as one that can lead to a pause. Our 2% ceiling leaves a buffer below both.
The legal picture differs by country. Under the US CAN-SPAM Act, commercial email does not require prior opt-in. It does require accurate sender information, a working unsubscribe and honoured opt-outs. In the US, catch-all verification is therefore mainly a deliverability and reputation decision, not a statutory one.
In the UK, the ICO applies the Privacy and Electronic Communications Regulations to marketing email. Its guidance treats named addresses at a business, such as jane.doe@acme.com, as individual subscriber addresses, which generally require consent. The corporate-subscriber exception covers generic addresses such as info@. A catch-all result does not change that analysis, so a UK B2B list can need consent review even when every address verifies. Confirm the position for your own list with counsel. For how verification fits into your wider obligations, see email verification compliance and hygiene.
Bottom line: Keep complaints near 0.1% and bounces under 2%. Verification helps with the second, but consent protects you on the first, and verification cannot supply it.
What are the most common catch-all mistakes?
- Reading a catch-all "Valid" as a confirmed inbox. It means the domain said yes. Use engagement history to decide whether to trust it.
- Spending deep-verification quota on the whole list. Standard checks already sort the majority. Spend the deep quota on the catch-all subset that matters for the next send.
- Sending a catch-all test to the full list. A test is only useful when its bounces are survivable.
- Deleting catch-alls who recently bought or replied. Use purchase and reply data to rescue real customers before you suppress anything.
- Letting Free-plan results expire. Results are kept for 24 hours, so an export left until tomorrow may be gone.
- Treating role addresses and catch-alls as the same problem. Role addresses such as info@ raise questions about who reads the mail. Catch-alls raise questions about whether the mailbox exists. They need different handling.
- Merging Risky back into the main segment on re-import. This quietly undoes the hold you built.
- Sending re-engagement mail to catch-alls during a suspension review. Every bounce is visible to the reviewer.
- Treating a result as permanent. Domains change their configuration, and people leave their jobs.
Bottom line: Most catch-all errors come from treating a classification as a verdict, or from merging segments you meant to keep apart.
How often should you re-check catch-all addresses?
Re-verify the catch-all segment every quarter, and always before a campaign that matters. Domain configuration changes, and so do job titles. For a one-off cleanup versus a recurring schedule, see email verifier for one-time cleanup vs ongoing hygiene, and for the wider routine, see email list maintenance best practices.
At signup, catch-all status should shape the experience rather than block the person. A common approach is to accept the address, send a confirmation email, and add the contact to a full-send segment only after they confirm. Teams using email verification API and automation can flag catch-all domains at entry and route them to that confirmation step automatically.
If you are considering two verifiers on the same list, a second opinion rarely changes a catch-all decision, because both tools face the same SMTP limitation. See should I double verify my email list with two tools.
Bottom line: Re-check catch-alls quarterly and at signup, and let the confirmation step, not the verifier alone, decide who joins the full send.
How we compared (and limitations)
This article is based on public documentation: RFC 5321 and RFC 3463 for SMTP behaviour, Google's and Yahoo's published sender guidance, Amazon SES's documentation, the FTC's CAN-SPAM guide and the ICO's guidance. We have not run controlled tests of catch-all acceptance behaviour across providers, and mailbox providers change their policies without notice.
The worked example uses hypothetical counts and bounce rates. Its arithmetic and plan limits are real. Unlimited Verifier's 99.5% accuracy figure is the company's own stated figure for deep verification, not an independent benchmark, and no SMTP-based check can confirm that a specific mailbox on a catch-all domain exists. Check current plan details on the sign-up page before you plan a large run, since limits and retention periods can change.
For a broader view of selecting a verifier, start with how to choose an email verifier and compare options in best email verification tools. When a vendor claims certainty on catch-all addresses, treat the claim with caution, as explained in red flags when choosing an email verification service. For catch-all handling specifically, see Unlimited Verifier's catch-all email verification page.
Bottom line: Use standard checks as the floor, handle catch-alls as a segment with its own rules, and tie every decision to your consent and engagement data.
Catch-all decision steps
- Run standard checks on the full list: syntax, domain, MX, SMTP.
- Flag catch-all domains using a catch-all detection test.
- Count catch-alls as a share of the list. Below about 5% on a recent opt-in list, a light process is usually enough.
- Split catch-alls by source and last engagement date.
- Send recent opt-in catch-alls last, only to the most engaged segment.
- Hold or remove cold, purchased or dormant catch-alls.
- Monitor bounces after each send and keep total bounces under 2 percent.
Frequently asked questions
What is a catch-all email domain?
A catch-all domain is a mail domain whose server accepts mail for any local part, even addresses that do not exist. Because of this, a positive SMTP response does not prove a specific mailbox exists there. Treat these addresses as a risk segment and decide how to send to them based on engagement history.
Can an SMTP check verify a catch-all address?
Generally no. An SMTP check asks the receiving server whether it accepts a recipient, and a catch-all server says yes to everything. The result is uninformative for that address, so it cannot confirm a working inbox.
What percentage of catch-all addresses is too many?
The 5% figure in this guide is a working threshold, not a published standard from any ESP or mailbox provider. Once catch-all addresses pass roughly 5% of a list, add separate handling for them.
Should I remove all catch-all addresses from my list?
Not necessarily. Recent opt-in catch-alls with recent engagement can often be sent to, ideally last and to the most engaged segment. Cold, purchased or dormant catch-alls carry more risk and are better held back or removed.
What bounce rate should I keep under?
This guide recommends keeping total bounces under 2 percent on every send. This is an internal guideline, so check your ESP's own policies and monitor your bounce data over time.
Do catch-all checks slow down list cleaning?
They can add time and cost, since many verifiers mark catch-alls as a separate result. Most teams find it worthwhile to verify the riskiest segments first rather than running every check on the full list.
Why do catch-all addresses still bounce after passing verification?
Catch-all servers accept mail at the SMTP stage, then may reject or bounce it later, for example after content filtering or when the mailbox was closed. The early acceptance is therefore not a guarantee of delivery.
Are role addresses like info@ a catch-all problem?
They are a separate signal. Role addresses such as info@ or sales@ may be monitored by several people or have low engagement, so they are not proof of a bad address but can warrant a different sending approach.
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.