Article

What Is Send-Based Catch-All Verification? A Practical Guide

By Unlimited Verifier Team ·

Diagram of send-based catch-all verification showing a neutral probe sent to a catch-all address and the resulting invalid or unverified outcome.

Summary

Send-based catch-all verification checks an address on a catch-all domain by sending a short, neutral message and reading the outcome. A 5.1.1 hard bounce proves the address is invalid, while silence is only a weak positive and never confirms a mailbox exists.

What is send-based catch-all verification?

Send-based catch-all verification checks an address on a catch-all domain by sending it a real message and reading the outcome: a hard bounce (SMTP code 5.1.1) proves the address is invalid, but silence is only a weak positive and never proves the mailbox exists.

Quick answer

For the wider picture, start with how email verification works.

What is a catch-all domain, and why does it break normal verification?

A catch-all domain (also called an accept-all domain) is configured to accept mail for any local part, so anything@company.com gets a positive SMTP response whether or not that mailbox exists. Organisations do this so no legitimate message is lost to a typo, then sort the mail internally.

Standard verification asks the receiving server whether it would accept a recipient at the RCPT TO step of an SMTP conversation. What RCPT TO means in email verification covers that step, and how an email verifier checks if an address exists shows the full sequence. On a catch-all domain the answer is "yes" for every address, so the check cannot separate a real person from an invented one. How verifiers detect catch-all domains explains how the flag is set.

The result looks deliverable but is actually unknown. That is why catch-all addresses need a different method. Treat a catch-all email verification result as a classification, not a guarantee. Check how large the flagged share is in your own list before you plan the work, because it varies widely by source.

Bottom line: A catch-all "accepted" result means the domain says yes to everyone, so it cannot confirm the individual mailbox.

How is send-based verification different from the other methods?

The methods differ in who does the work and how much a positive result can be trusted. Send-based probing is the only option here that tests the mailbox directly, but it carries the most operational risk.

Method Who does the work What a positive result proves Main risk Best use
SMTP-only check Verifier, no message sent Domain accepts mail; on catch-alls, proves nothing about the mailbox None to recipients First-pass filtering of obvious invalid addresses
Send-based probe You, through your own sending setup Only a 5.1.1 bounce is conclusive; silence is weak Complaints and reputation damage to your sending domain Small, high-value catch-all segments
Bounce-based review You, from normal campaigns Built only from addresses you have already mailed Repeat bounces before you spot the pattern Ongoing hygiene; see bounce-based catch-all verification
Double opt-in The recipient clicks a link Address works and the person agreed to mail Smaller list and slower growth Lists you intend to keep long term
Engagement sunset Your engagement data Recent interest, not a valid mailbox Apple Mail Privacy Protection (iOS 15, 2021) pre-loads images, inflating opens Policy for dormant contacts, using clicks and replies

Bounce-based review and send-based probing are easy to confuse. Bounce-based review reads outcomes from campaigns you were already sending. A probe is a deliberate, isolated test on addresses you have never mailed, usually with a short, neutral message.

Bottom line: Only a probe or a double opt-in produces a direct signal about the mailbox, and each one carries a different cost.

How does send-based catch-all verification work, step by step?

The process is simple to describe and easy to get wrong. Each step protects either your results or your sender reputation.

  1. Isolate the catch-all addresses. Run the full list through a verifier first. Syntax and domain problems should be gone by now; what syntax validation checks and how verifiers check if a domain accepts mail explain those earlier filters. Pull the catch-all rows into their own file. Probing the whole list wastes sends on addresses that are already known.
  2. Choose a neutral probe. Use a short, plain-text confirmation with a clear sender name and a reason for the message. No promotional content. Keeping it neutral reduces complaints and keeps the message closer to transactional than marketing.
  3. Send from a separate subdomain. Probes should never leave your primary sending domain. If complaints spike, the damage stays on a subdomain you can quarantine.
  4. Send in waves. Split the file into waves of roughly 500 to 1,000 addresses over several days. Immediate rejections surface within minutes, so you can pause a wave if early bounces climb.
  5. Monitor a return path you can read. Delivery status notifications follow the format in RFC 3464. Route them to a mailbox or webhook you check, not only to your ESP's dashboard.
  6. Wait the full window. Wait at least 72 hours, ideally 5 days from the last send. RFC 5321 describes senders retrying deliveries over several days, and some gateways accept a message and bounce it later after an internal lookup. A 24-hour check misses those late bounces.
  7. Classify every address and reconcile. Match each DSN to its address, sort the results using the table below, suppress the hard bounces and re-import the rest into segments.

Some vendor guides suggest 24 to 48 hours. That is too short given the retry behaviour above. We recommend 72 hours as the minimum, with 5 days as the target.

Bottom line: The probe is only as good as its wait window and its bounce monitoring, so set both up before the first wave goes out.

What do the bounce results actually mean?

Each outcome points to a different action. The most common mistake is treating a policy rejection as proof the mailbox is missing. A deliverable label from a verifier is not the same as a confirmed mailbox, and the table below keeps those two apart.

Outcome Typical signal Classification Action
Hard bounce, 5.1.1 (mailbox unknown) Permanent DSN Invalid Suppress permanently
Other permanent 5.1.x address errors Permanent DSN Invalid Suppress permanently
Late hard bounce after the window DSN arriving days later Invalid Suppress; this is why the window matters
5.7.1 (delivery not authorised, message refused) Policy or reputation rejection Undetermined Hold; do not call invalid
4.x.x temporary failure Deferral Undetermined Retry once, then hold
No DSN by the end of the window Silence Unverified positive Use only for low-risk, engagement-led sends
Click or reply from the recipient Human response Confirmed Move to your active list

The 5.7.x row matters most. A policy rejection means a filter refused your message, not that the mailbox does not exist. Removing those addresses over-prunes real contacts and makes your list look worse than it is.

The silence row is the hardest to accept. A catch-all server can accept a message and then quarantine or discard it without a bounce, so silence means "no evidence of a problem", not "verified". Keep silent addresses in their own tier.

Bottom line: Only a hard bounce or a human reply changes an address's status with confidence; everything else stays in a holding tier.

Should you probe a catch-all address at all?

Probing is a tool for a specific segment, not a default step. Your existing relationship with the contact decides the right move more than the verifier's flag does.

Segment Recommended action Why
Catch-all, clicked or replied in the last 90 days Send normal campaigns, watch bounces Recent clicks are strong evidence; a probe adds little
Catch-all, opted in through your own form, no recent engagement Probe in small waves You hold consent history, so the probe is a relationship check
Catch-all, bought or scraped Do not probe; suppress Probing cannot fix a consent problem, and the risk stays with you
Catch-all, B2B, high value, no engagement Double opt-in invitation first, then probe a sample Lower complaint risk than cold mail; the results shape the rest of the plan
Any large catch-all segment Probe 500 addresses first The sample's hard-bounce rate tells you whether to continue or suppress the whole segment

Use clicks and replies as your engagement signal, not opens. Apple Mail Privacy Protection pre-loads images, so opens overstate interest.

Bottom line: Probe only where consent and recent relationship justify it, and start with a sample so the first results decide the rest.

How much does a catch-all probe cost?

The verification cost is small and predictable. The probe itself has a cost that is easy to miss.

If you used all 25,000 deep checks on Pro, $29 ÷ 25 gives $1.16 per 1,000 deep checks on monthly billing, and $25 ÷ 25 gives $1.00 per 1,000 on annual billing. Most teams use only part of the allowance, so the effective cost is lower. For a broader view of email verification pricing and when deep checks are worth the spend, see deep email verification vs standard verification.

The hidden cost is the probe send. Each probe counts as a send on your ESP, so check your ESP's per-send pricing before you run a large wave. Staff time for reconciling bounce logs is also a real cost.

Bottom line: Verification is cheap at Pro rates; the sends and the reconciliation work are where the budget actually goes.

Worked example: cleaning a 40,000-row B2B list with 6,000 catch-alls

This example is illustrative. The plan limits and arithmetic are real; the verification split and probe outcomes are hypothetical.

Setup: A B2B SaaS team holds 40,000 contacts from trade-show imports and a legacy CRM, a common case covered in email verification for ecommerce and SaaS. In this scenario, the verification run flags 6,000 addresses (15%) as catch-all, and those fall into the Risky file.

Plan: The team uses the Pro plan at $29 a month. Pro allows lists of up to 25,000 emails, so the file splits into two uploads: 25,000 + 15,000 = 40,000. Standard verification is unlimited, so the full run carries no per-email fee. If the catch-all rows are also run through deep verification, they use 6,000 of the 25,000 monthly deep allowance, leaving 19,000.

Probe: The team sends the 6,000 catch-all addresses in waves of about 1,000 over four days, then waits five days from the last send.

Outcome Count Share of 6,000
Hard bounce (5.1.1) 912 15.2%
Policy or temporary (5.7.x / 4.x.x) 600 10.0%
Silent (no DSN in window) 4,488 74.8%
Check: 912 + 600 + 4,488 6,000 100%

Decisions:

Cost: One Pro month at $29, plus the probe sends on the ESP's pricing.

Free-plan check: The Free plan allows 25 lists a month of up to 150 emails each, which caps a month at 3,750 addresses and 750 deep verifications. That suits a trial, not a 40,000-row list.

Bottom line: The probe confirmed 912 invalid addresses and left 4,488 unproven, which is the honest result most catch-all segments produce.

How do you protect your sender reputation during a probe?

Sender reputation is the real cost of this method, so treat each probe as a risk to manage. Three rules keep it contained.

Keep volume small and content neutral. Mailbox providers judge senders on complaint and bounce rates. Cap the probe to a small share of your sending volume and keep the message to a plain confirmation.

Use one complaint line. Google's sender guidance warns against spam rates reaching 0.3%, and its Postmaster Tools documentation recommends keeping them below 0.1%. Yahoo's sender requirements set a similar complaint ceiling. We recommend 0.1% as your stop line for probes, which leaves a wide margin before the 0.3% level.

Get the legal basis right. In the US, the FTC's CAN-SPAM compliance guide applies to commercial messages, so a probe that promotes anything falls under it. In the UK and EU, unsolicited electronic mail raises questions under PECR and GDPR, and the ICO publishes guidance on both. If you are unsure, use a double opt-in invitation instead. Verification supports email verification compliance and hygiene, but it does not replace consent.

Bottom line: A probe is defensible only when it is small, neutral, monitored and lawful for the recipients you contact.

How do you run a catch-all probe with Unlimited Verifier?

This walkthrough assumes you have a CSV export and an ESP that can send to a segment.

  1. Create an account. Sign up for free to test with a small list, or choose Pro for larger files.
  2. Upload your list. Go to upload and verify a list. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, split any file above 25,000 rows first.
  3. Export the results immediately. Free results are kept for 24 hours and Pro results for 30 days. Download the Valid, Risky and Invalid files as CSV, Excel or JSON as soon as the run finishes.
  4. Build the probe file. From the Risky file, keep only the catch-all addresses, using the catch-all result in your export. Leave disposable addresses, which verifiers flag separately, and role addresses such as info@ out of the probe. They need their own handling.
  5. Set up a probe sender. Create a subdomain for the send, add a plain-text template with a clear sender name, and point bounce handling at a mailbox you check.
  6. Send in waves. Start with about 500 addresses, check the first hour for hard bounces and complaints, then continue in waves of 500 to 1,000 spread over several days.
  7. Wait 72 hours to 5 days, then pull the bounce log and match every DSN to its address.
  8. Reconcile and re-import. Suppress hard bounces in your ESP, move silent addresses into a double opt-in segment, and hold undetermined ones. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so this is an export and re-import. You can automate it with the email verification API and automation workflow via the Email verification API. API access is included on Pro (100,000 emails a month), and each bulk request takes up to 10,000 emails.

For a one-off spot-check of an individual address before you decide whether it belongs in a probe, the free email checker gives a quick read.

Bottom line: Export results before the retention window closes, then let the wait and the bounce log make the decisions.

What mistakes wreck catch-all probes?

Bottom line: Most failed probes come from reading silence as success or sending from the wrong domain.

How we compared (and limitations)

This article is based on public documentation: the SMTP and bounce-format RFCs (RFC 5321 and RFC 3464), Google and Yahoo sender guidance, the FTC's CAN-SPAM guidance and ICO guidance. We have not run controlled probes against any mailbox provider, and provider behaviour changes without notice.

The wait window and wave sizes are practitioner recommendations, not published standards. The worked-example outcomes are hypothetical. Unlimited Verifier states 99.5% accuracy for deep verification. That is the company's own figure, not an independent benchmark, and it does not confirm any individual catch-all address. For a broader comparison of options, see our guide to the best email verification tools and our buyer's checklist for choosing an email verifier.

For catch-all lists, the honest output of any verifier, including Unlimited Verifier, is a sorted list with a Risky tier that needs a method beyond SMTP. Pair verification with real-time email validation at signup and a regular schedule from our list maintenance best practices, so the catch-all problem stays small.

Bottom line: Verification tells you which addresses need a probe; the probe and its wait window tell you the rest.

Result classification framework

Outcome Signal Classification Action
5.1.1 hard bounce Mailbox does not exist Invalid Remove from list
No bounce after 72h to 5 days Silence only Unverified Keep in risky segment
4xx temporary response Server delay or full mailbox Undetermined Retry later
5.7.x policy response Blocked by policy Undetermined Do not treat as valid

Frequently asked questions

Is a catch-all email address valid?

Not necessarily. A catch-all domain accepts mail for any address, so a positive SMTP response does not confirm the individual mailbox exists. Catch-all addresses are usually classified as risky or unknown until a stronger signal, such as an engagement history or a send-based probe, is available.

What does a 5.1.1 bounce mean?

A 5.1.1 code is an SMTP status meaning the recipient mailbox does not exist. When a send-based probe returns this hard bounce, the address can be treated as invalid and removed from your list.

How long should I wait for a bounce before deciding?

Most teams wait roughly 72 hours to 5 days before classifying a silent address as unverified. Silence is not proof of validity, so the address should stay in a risky category rather than being marked as deliverable.

Can send-based verification hurt my sender reputation?

Yes, it can. Probes generate bounces and possibly complaints, which affect domain reputation if sent from your main domain. Running probes from a separate subdomain, in small waves, with neutral content limits this risk.

What is the difference between a hard and soft bounce?

A hard bounce is a permanent failure, typically a 5.x.x code, indicating the address cannot receive mail. A soft bounce is temporary, usually a 4xx code, such as a full mailbox or server delay, and the address should not be treated as invalid from one soft bounce alone.

Why do catch-all domains exist?

Organisations configure catch-all domains so that mail sent to misspelled or unknown local parts is not lost. Staff then route the messages internally. This design is why standard SMTP checks cannot confirm individual mailboxes.

Should I send probes to every catch-all address?

Usually no. Send-based probing is best reserved for small, high-value catch-all segments where the cost of a wrong decision is high. Running it on an entire large list increases complaint and reputation risk.

Are there alternatives to send-based verification for catch-all domains?

Yes. Options include engagement history, double opt-in confirmation, and checking how recently an address interacted with your emails. Each has trade-offs, but none require sending unsolicited probe messages to the recipient.

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 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.