Article
How Much Does Catch-All Verification Cost? A Budget Guide with Worked Examples
By Unlimited Verifier Team ·

Summary
Catch-all verification usually costs your standard per-check rate, or nothing extra on flat plans. On Unlimited Verifier it's included in unlimited standard checks, so the direct cost is $0 on Free or $29 a month on Pro. The larger expense is the uncertainty a catch-all leaves behind, which can push a campaign past a safe bounce rate.Catch-all verification usually costs the same per-check rate as any other address, or nothing extra on flat plans. On Unlimited Verifier it's part of unlimited standard checks, so the direct cost is $0 on Free or $29 a month on Pro. The bigger expense is the uncertainty a catch-all leaves behind. Your email verification pricing model determines what you pay per check, and this guide covers the full budget, with worked examples at real list sizes. For the wider picture, see our email verification cost pillar.
Quick answer
- Direct cost on Unlimited Verifier: $0 per catch-all address. Pro is $29/month, or $25/month billed annually ($300 a year versus $348 monthly).
- Elsewhere: Vendors bill catch-alls differently. Some charge a full credit, some charge a lower rate, and some don't charge at all. Ask in writing and test a sample before you commit.
- The real cost: A catch-all can't be confirmed at the mailbox level, so mailing it blind can push a send past a 2% bounce ceiling.
- Budget formula: Catch-all count × your per-check rate (zero on flat plans). Then count the Valid contacts you can actually mail.
What is a catch-all address, and why can't a verifier resolve it?
A catch-all (or accept-all) domain accepts mail for any local part, real or not. That means a verifier can't confirm whether a specific person's mailbox exists on that domain.
During an SMTP check, the verifier asks the receiving server whether a recipient is valid using the RCPT TO command. RFC 5321 defines how servers answer that request. On a catch-all domain, the server accepts anything@domain along with real mailboxes, so the reply tells you the domain accepts mail but not whether the person exists.
That's why catch-all results land in the Risky bucket rather than Valid or Invalid. The verifier can confirm the domain and mail server, but not the mailbox. You're paying for a classification, not a certainty.
Bottom line: A catch-all result tells you the domain accepts mail, not that the person does. Price it as a risk classification.
How much does catch-all verification cost per address?
On a flat plan, catch-all verification costs nothing beyond the subscription. On a per-check plan, it usually bills at the standard rate, though some vendors discount it or skip the charge. The price you actually pay depends on which of five pricing models you're on.
| Pricing model | How catch-alls are billed | What it works out to | Watch for |
|---|---|---|---|
| Flat plan with unlimited standard checks (Unlimited Verifier Free or Pro) | Included in standard verification | $0 extra per address | Deep verifications are a separate monthly quota (750 on Free, 25,000 on Pro) |
| Pay-as-you-go credits | Usually one credit per check | Your credit rate; $0.004 is used as an illustration below | Whether retries consume credits again |
| Tiered per-email contract | Often priced at the standard rate | Falls as volume rises | Minimum commitments, and whether catch-alls are listed separately |
| Self-hosted open-source engine | No vendor fee | Server, IP and staff time | You still can't resolve a catch-all, because the limit is in SMTP itself |
| Negotiated enterprise contract | Set in the contract | Negotiated | Renewal terms and overage charges |
Sources don't agree on how far catch-all discounts go, and there's no standard. Our recommendation is to budget at the full per-check rate, even if the vendor offers a discount, and to confirm the billing on a test batch. A full-rate forecast won't surprise you on the invoice.
Bottom line: Catch-all verification is zero on a flat plan and the full per-check rate on a credit model. Budget at the full rate until a test invoice proves otherwise.
What does a catch-all actually cost once it's in your list?
The verification fee is usually the smallest cost. The number that matters is the true cost per usable contact:
True cost per usable contact = (verification fees + sending fees + bounce recovery) ÷ contacts you can actually email
Three costs usually sit outside the verification line:
- Sending fees. Many ESPs bill by active contact count. An unverifiable address keeps costing you send fees for as long as it stays on the list. Removing dead addresses before they accrue charges is one reason verifying emails can lower your ESP bill.
- Reputation exposure. Mailing a catch-all segment in one batch can push bounces up sharply. Google's email sender guidelines and Yahoo's sender requirements both emphasise list quality. We recommend a 2% total bounce ceiling for any single send, which leaves a margin below the thresholds platforms commonly act on.
- Lost opportunity. Dropping every catch-all also drops the real people among them. The goal is to mail the catch-alls with evidence of engagement, not to delete the whole segment.
For ecommerce and SaaS senders, where signups arrive constantly, these costs compound. Verification at the point of entry is part of email verification compliance and hygiene, and skipping it is what makes not verifying expensive over time.
Bottom line: A catch-all's true cost is its verification fee plus the risk of mailing it blind. Measure both before you choose a policy.
How do you estimate your catch-all budget before you verify?
Estimate the catch-all count from a random sample rather than guessing. This six-step method takes about an hour and prevents most budget surprises.
- Deduplicate the list. Remove repeated addresses, ignoring letter case and trailing spaces. Duplicates inflate your count and your usage.
- Remove malformed addresses. Fix or drop entries with obvious syntax errors before you spend quota on them.
- Draw a random sample of 500 addresses and verify it. Record the catch-all count.
- Calculate the share and its margin of error. If 90 of 500 are catch-all, the share is 18%. For a proportion near 18% at 95% confidence, a sample of 500 gives roughly ±3.4 percentage points, so plan for 15–21%.
- Multiply out the budget. Catch-all count × per-check rate (zero on flat plans), plus a 10% retry allowance on per-check plans.
- Choose a policy (see the policy table below) before the full run, so the team knows which segment is held back.
The margin of error assumes a genuinely random sample. If your list is segmented by source, sample each segment separately, because imported lists often carry far more catch-alls than customer lists.
Bottom line: A 500-address random sample predicts your catch-all share within a few points. Use it to size the budget before you pay for a full run.
How do you run catch-all verification on Unlimited Verifier?
Unlimited Verifier checks each address for syntax, domain, MX records and the SMTP mailbox. It detects catch-all domains, flags disposable and role-based addresses, and sorts results into Valid, Risky or Invalid. Catch-alls land in Risky.
- Export your contacts as a CSV or Excel file from your ESP or CRM. Include an engagement column, such as last open or last purchase date. That column decides which catch-alls are worth mailing.
- Create an account at sign up. The Free plan covers 25 lists a month of up to 150 emails each, plus 750 deep verifications.
- Upload the file on the upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. If your file is larger than 10MB, split it first.
- Run verification. Wait for the job to finish, then open the results.
- Filter the Risky bucket. Use the flags returned for each address to separate catch-all rows from disposable and role-based ones. Sort the catch-alls by engagement, most recent first.
- Export the results as CSV, Excel or JSON. Free results are kept for 24 hours and Pro results for 30 days, so export the same day and keep your own copy.
- Re-import only Valid contacts into your ESP as a new segment, then add Invalid addresses to your suppression list. There are no native ESP, CRM or Zapier integrations, so this export-and-re-import step is how the list moves.
To check one flagged contact, such as a VIP customer, use the free email checker. For a deeper look at how catch-all results are handled, see the catch-all email verification page.
Bottom line: Engagement data decides which catch-alls to mail. Export inside the retention window so you don't have to re-verify the same list.
What does catch-all verification cost at real list sizes?
These scenarios use Unlimited Verifier's published plan limits. The catch-all shares and the $0.004 credit rate are illustrative, not measured or quoted.
Scenario A: a 3,000-row list on Free ($0)
- Lists needed: 3,000 ÷ 150 = 20 lists, within the 25-list monthly limit.
- Catch-alls at an illustrative 15%: 3,000 × 0.15 = 450.
- If you also deep-verify all 450: 450 ÷ 750 = 60% of the monthly deep quota, leaving 300.
- Cost: $0. Export the same day, because Free results are kept for 24 hours.
Free has a hard ceiling. A 4,000-row list needs 4,000 ÷ 150 = 26.7, so 27 lists, which exceeds the 25-list limit. The most Free can process in a month is 25 × 150 = 3,750 emails.
Scenario B: a 40,000-row list on Pro ($29)
- Split for the 25,000-per-list limit: 25,000 + 15,000 = 2 lists.
- Illustrative result: 27,600 Valid (69%), 9,200 Risky (23%), 3,200 Invalid (8%). Check: 27,600 + 9,200 + 3,200 = 40,000.
- Catch-alls inside the Risky bucket at 18%: 40,000 × 0.18 = 7,200.
- Deep quota if you deep-verify all 7,200: 7,200 ÷ 25,000 = 28.8% of the monthly allowance.
- Subscription per 1,000 addresses: $29 ÷ 40 = $0.73. As a stress view, if you charged the entire subscription to catch-alls: $29 ÷ 7,200 = $0.004 each, or about $4.03 per 1,000 catch-alls.
- Billed annually at $25/month, the plan costs $300 a year, saving $48 against monthly billing. Our annual vs monthly billing guide covers when that trade-off makes sense.
If your list grows past this size, the cost to verify 500,000 emails follows the same arithmetic at larger volume.
Scenario C: the same 40,000 rows on a pay-as-you-go credit tool
- Illustrative rate: $0.004 per check. Full list: 40,000 × $0.004 = $160.
- If each catch-all is billed a second time on retry: 7,200 × $0.004 = $28.80 extra, for a total of $188.80.
- Break-even against Pro: $29 ÷ $0.004 = 7,250 checks a month. Above that volume, the flat plan costs less at this illustrative rate.
- A one-off 500-address test costs 500 × $0.004 = $2. Free handles the same 500 addresses at $0 across four lists of 150.
Scenario D: mailing all 7,200 catch-alls in one send
- Suppose 10% prove undeliverable (a hypothetical figure). That's 7,200 × 0.10 = 720 bounces.
- Send bounce rate: 720 ÷ 7,200 = 10%, five times the 2% ceiling of 144 bounces.
- Batching doesn't lower the rate. It limits exposure. If the most engaged 1,000 catch-alls bounce at 10%, that's 100 bounces, and you can stop before the other 6,200 go out.
Bottom line: On Free, catch-all verification costs nothing. On Pro, the subscription works out to about $0.73 per 1,000 addresses for this list. Pay-as-you-go wins only for small one-off checks.
Which catch-all policy gives the best cost and protection?
The policy you pick matters more than the verification price, because it decides how much risk each send carries.
| Policy | Extra verification cost | Bounce risk | Catch-alls reached | Best for |
|---|---|---|---|---|
| Mail all catch-alls at once | None beyond the initial check | High, because one batch carries the whole risk | 100% | Rarely the right call |
| Hold all catch-alls back | None | Lowest | None (the full 18% in Scenario B is excluded) | Lists under review, or sending-quality problems |
| Ramp catch-alls last, by engagement | None beyond the initial check | Low to moderate | Most engaged catch-alls, over several weeks | Most healthy lists with engagement data |
| Deep-verify catch-alls first | Uses deep quota (7,200 of 25,000 in Scenario B) | Lower for the contacts that pass | Only those that pass | Lists where the monthly quota can absorb it |
Our default recommendation is the third row. Verify the list, keep catch-alls out of the first sends, then ramp them by engagement. You get the reach of mailing them and a measured bounce rate on every send. The same ramp logic applies to any email list maintenance routine.
Bottom line: Ramp catch-alls by engagement rather than mailing them in one batch. The policy adds no verification cost and keeps each send under your ceiling.
Which verification option gives the best catch-all economics?
The right option depends on list size, whether you verify at signup, and how much engineering time you have. The table compares the main choices on how they bill catch-alls and how long results are kept. Our buyer's checklist for choosing a verifier covers the wider evaluation. For the wider field, see our roundup of best email verification tools.
| Option | How catch-alls are billed | Results kept | Predictable cost | Best fit | Watch for |
|---|---|---|---|---|---|
| Unlimited Verifier Free | Included in unlimited standard checks | 24 hours | Yes, $0 | Lists up to 150 rows, up to 3,750 emails a month | No API access; export the same day |
| Unlimited Verifier Pro | Included in unlimited standard checks | 30 days | Yes, $29/month or $25 billed annually | Lists up to 25,000 rows, with API access (100,000 emails a month) | Deep verifications capped at 25,000 a month |
| Pay-as-you-go credit tool | Usually one credit per check | Varies by vendor | No, scales with volume | Small one-off cleans | Retries, and whether unused credits expire (see unused credits) |
| Self-hosted open-source engine | No vendor fee; you run it | You decide | Predictable infrastructure cost | Teams with engineering capacity | You manage servers, sending IPs and rate limits; catch-alls stay unresolved |
| Negotiated enterprise contract | Set in the contract | Set in the contract | Yes, annually | Very large databases | Minimum commitments and overage terms |
Unlimited Verifier's verification engine is published as open source on GitHub. Self-hosting removes the vendor fee, but it doesn't remove the catch-all limit, and it adds the work of running your own sending infrastructure. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark.
Teams that verify at signup as well as in batches can use the email verification API. Pro includes API access, with single-email checks and bulk batches of up to 10,000 emails per request. Automating this is part of email verification API and automation, and real-time email validation explains how checks at the signup form differ from batch cleans. Our API vs bulk pricing comparison covers the cost side.
Bottom line: Free is the cheapest start for small lists. Pro's flat price beats per-check billing once you verify more than about 7,250 addresses a month at the illustrative rate.
What mistakes make catch-all verification cost more than it should?
Most overspend comes from process errors rather than the price itself.
- Wasting capacity on duplicates. Duplicate rows use up per-list capacity and, on per-check tools, money. Deduplicate before upload.
- Re-running an unchanged list. On Free, results are kept 24 hours; on Pro, 30 days. Export inside that window and keep your own copy. Re-running an unchanged list spends deep quota you may need for live catch-alls.
- Ignoring the Free ceiling. A 4,000-row list needs 27 lists, but Free allows 25 a month. Plan the month around the 3,750-email limit.
- Budgeting catch-alls as Valid. A catch-all is a classification, not a confirmed address. Base your send volume on the Valid count.
- Assuming all vendors bill catch-alls the same way. Some charge a full credit, and some don't. Test one batch and read the invoice before you commit.
- Mailing the whole Risky bucket at once. One batch carries all the risk. Ramp by engagement.
- Treating an accuracy figure as a guarantee. A stated accuracy number doesn't remove the catch-all limit. SMTP checks can't confirm an individual mailbox on a server that accepts every address.
- Skipping the engagement column. Without it, you can't rank catch-alls, so the segment is either mailed blind or dropped entirely.
- Assuming "unlimited" means no terms. Read the fair-use terms on any unlimited plan before you build a budget around it. Our guide to fair-use limits on unlimited verification plans explains what to check.
Bottom line: Most catch-all overspend comes from duplicates, expired results and mailing the segment in one batch, not from the verification fee.
How we compared (and limitations)
This article is based on public documentation and published pricing structures, including RFC 5321 and the sender guidelines from Google and Yahoo. We haven't tested other vendors' catch-all billing or run controlled benchmarks against any verifier.
- Unlimited Verifier plan figures come from its published plan details. The 99.5% deep-verification accuracy is the company's stated figure.
- The $0.004 per-check rate in Scenario C and the credit-tool comparison are illustrative, not quoted from any vendor.
- The 15% and 18% catch-all shares and the 10% undeliverable rate are hypothetical inputs for the arithmetic, not measured results.
- Vendor billing for catch-all results varies and changes over time. Confirm current terms with each provider before you commit.
Bottom line: Use the formulas and a 500-address sample to size your own budget. Your list will produce different numbers from the illustrations here.
Worked budget at 50,000 addresses
| Scenario | Catch-all share | Catch-alls | Cost at $0.004 per check | Cost on flat plan |
|---|---|---|---|---|
| Clean B2B list | 10% | 5,000 | $20 | $0 extra |
| Mixed consumer list | 25% | 12,500 | $50 | $0 extra |
| Corporate-heavy list | 40% | 20,000 | $80 | $0 extra |
Use the $0.004 rate only as an illustration; substitute your own vendor's rate.
Frequently asked questions
Do catch-all emails cost more to verify?
Usually not. Most vendors bill a catch-all at the same per-check rate as any other address. On flat plans with unlimited standard checks, such as Unlimited Verifier, there is no extra charge per catch-all address.
Is catch-all verification free?
It can be. On Unlimited Verifier's Free plan, catch-all checks are part of unlimited standard verification, so the direct cost is $0. Other vendors may charge a full or reduced credit, so confirm pricing in writing before you rely on it.
Why is a catch-all result called Risky?
Because the verifier can confirm the domain accepts mail but cannot confirm that a specific mailbox exists. The server accepts any local part, so the result is a classification of risk rather than a definite Valid or Invalid.
What is a safe bounce rate for catch-all addresses?
Many senders aim to keep bounces under 2 percent, since high bounce rates can hurt sender reputation. Mailing unverified catch-all addresses blind can push a send past that level, so sample and segment them before a full send.
Can I remove catch-all addresses from my list?
You can, but you may lose real customers. A practical approach is to mail catch-alls in small batches, monitor bounces and engagement, and suppress any that bounce or show no activity.
Do retries of catch-all checks cost extra credits?
It depends on the vendor. Some charge a new credit for each retry, while others include retries in the original check. Check your vendor's documentation for how retries and re-verifications are billed.
How do I budget for catch-all addresses?
Count your catch-all addresses, multiply by your per-check rate (zero on flat plans), then count how many Valid contacts you can actually mail. Include the cost of any deep verification or follow-up sends.
Can an open-source verifier resolve catch-all domains?
No. Self-hosted engines face the same limit because catch-all behavior is part of how SMTP servers respond. Hosting costs remove the vendor fee, but the uncertainty remains.
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.