Article

How Does Bounce-Based Catch-All Verification Work? A Step-by-Step Guide

By Unlimited Verifier Team ·

Flow diagram of bounce-based catch-all verification, showing a probe email sent to a catch-all domain and a 5.1.1 bounce marking the address invalid.

Summary

Bounce-based catch-all verification sends a real message to an address on a catch-all domain and treats a permanent bounce within a set window as proof the mailbox is invalid. Only permanent failures such as enhanced status code 5.1.1 count as a verdict, since silence proves nothing. The guide's default setup uses a 72-hour verdict window, a 7-day sweep, and a separate probe subdomain.

Bounce-based catch-all verification tests whether an address at a catch-all domain exists by sending it a real message and treating a permanent bounce that arrives within a set window as evidence the mailbox is invalid. This guide recommends a 72-hour verdict window, though no published standard sets one. For the broader picture, see how email verification works.

Quick answer

Why can't a standard verifier tell whether a catch-all address exists?

A standard verifier opens an SMTP session with the recipient's mail server, issues RCPT TO for the address, and reads the reply: 250 (accepted) or 550 (no such user). It is fast and cheap, and it is the core of how an email verifier checks whether an address exists. What RCPT TO means covers the mechanics.

A catch-all (accept-all) domain is configured to accept every recipient at the SMTP layer and decide what to do with each message later. So RCPT TO:<jane.doe@example.com> and RCPT TO:<xq7-random@example.com> can both return 250. The reply describes the server's configuration, not the person's mailbox. How verifiers detect catch-all domains explains the usual trick of probing a nonsense address first.

Catch-all configurations are common on large corporate domains, so they can make up a meaningful share of the Risky bucket on B2B lists. The practical consequence is that a "catch-all" result describes the domain, not the person. Bounce-based testing asks the one question SMTP cannot answer on its own: does this mailbox actually accept mail?

Bottom line: SMTP acceptance on a catch-all domain describes the server, so you need a second signal from the mailbox itself.

How does a bounce-based check work, step by step?

It works because acceptance at SMTP is not the final decision. A receiving server can accept a message and then fail it later, and when it does, it reports the failure back to the sender.

  1. Send from a return-path you control. Every message has an envelope sender (the MAIL FROM address, also called the return-path). Failure reports go there.
  2. Make each bounce traceable. Some senders encode the recipient into the return-path, a pattern called VERP (variable envelope return path). That lets you match a bounce to its address without parsing message text. Some ESPs apply this automatically, so check yours.
  3. Wait out the window. Receiving servers often defer a message before failing it, so failures can arrive days later.
  4. Collect the delivery status notifications (DSNs). A DSN is a machine-readable bounce. Its format is defined in RFC 3464. Senders request DSNs under the extension in RFC 3461.
  5. Read the enhanced status code. Codes such as 5.1.1 come from RFC 3463 and say what kind of failure occurred.
  6. Classify the result. Permanent mailbox failures become suppressions. Policy refusals and full mailboxes get held. Silence becomes "survived probe," a weaker label than "valid."

The reason this works is that the SMTP probe is one checkpoint, and often a generic one. The real delivery decision happens later, inside the receiving system, and that is the only place a catch-all mailbox's status is actually known.

Bottom line: A bounce-based check reads the decision the mailbox makes after accepting the message, a signal SMTP probing cannot reach.

Which bounce codes count as proof?

Not every bounce means the mailbox is gone. Treating every failure as "invalid" is the most common way this method damages a list. The table maps the RFC 3463 codes you are most likely to see to an action.

Enhanced code RFC 3463 meaning What it tells you Recommended action
5.1.1 Bad destination mailbox address Strongest evidence the mailbox does not exist Suppress permanently
5.1.3 Bad destination mailbox address syntax The address is malformed Suppress, and fix the source
5.2.2 Mailbox full The mailbox exists but cannot take mail right now Hold and retry; never delete on one bounce
5.4.4 Unable to route Often a DNS or routing fault, sometimes domain-wide Investigate the domain before judging individual addresses
5.7.1 Delivery not authorized, message refused A policy or reputation block, which says little about the mailbox Treat as Risky, not Invalid
4.x.x Transient failure No verdict yet; the server is still deferring Retry until it turns permanent or the window closes

The 5.7.1 row is where practitioners get hurt. A policy refusal means the message was rejected for content or reputation, not that the recipient doesn't exist. Counting it as Invalid deletes real customers. Receivers also apply codes inconsistently, so track patterns per domain rather than trusting any single bounce.

Bottom line: Only the permanent mailbox codes (5.1.1 and 5.1.3) should trigger automatic suppression. Everything else needs a hold or an investigation.

How long should you wait before a silent address counts as valid?

No industry standard exists, and practitioners disagree widely, from an hour to a week. This guide recommends a 72-hour verdict window and a 7-day sweep for late bounces.

The reasoning comes from how mail is retried. RFC 5321 expects sending servers to keep retrying deferred mail over a period measured in days before giving up. A message deferred for four days and bounced on day five never appears in a 72-hour read. The 72-hour window catches immediate and short-deferral failures, and the 7-day sweep catches most of the rest.

Longer windows cost time. Every extra day delays the list's next use, and a longer window narrows the gap without closing it.

Bottom line: Read at 72 hours, sweep at 7 days, and record both windows so your results can be reproduced.

What does "no bounce" actually prove?

Less than most teams assume. Silence means no permanent failure was reported inside your window. It does not prove:

Label survivors honestly in your data. Use "survived probe" rather than "valid," so no one later mistakes a weak signal for a strong one.

Bottom line: A survived probe is a reduced-risk address, not a verified one. Keep it in its own segment and send to it last.

How does bounce-based testing compare with other catch-all options?

Each option resolves a different question, so compare them on what they answer.

Option What it resolves Sends mail? Main risk Best use
Treat all catch-alls as valid Nothing No Bounce rate creeps up unnoticed Rarely justified
Suppress all catch-alls Removes the uncertainty No Loses real contacts on corporate domains Low-value lists, or compliance-first programmes
Engagement-only sending Recent interest, not existence Yes, to engaged contacts only Opens are an unreliable signal Ongoing sends after a probe
Bounce-based probe Mailbox existence, within the window Yes, one probe per address Deliberate bounces hurt reputation; needs a lawful basis Large catch-all segments with a lawful basis
Double opt-in or confirmation Existence and consent Yes, a confirmation message Lower sign-up completion New sign-ups, where proof matters most
Verifier detection alone That a domain is catch-all, not the mailbox No Cannot settle individual mailboxes First-pass triage

Read vendor accuracy claims against this table. An accuracy figure applies to what a check can resolve, and an SMTP-only check cannot reliably settle an individual catch-all mailbox. That is why the "verifier detection alone" row exists.

If you are comparing the best email verification tools for catch-all handling, ask each vendor which rows its product covers. Some will answer "detection" and stay silent on "resolution."

Bottom line: Detection tells you a domain is catch-all. Only a bounce-based probe or a confirmation message tells you about the individual mailbox.

What should you decide before sending a single probe?

Make five decisions before you send. Each protects either your compliance position or your sending reputation.

  1. Confirm the lawful basis for each contact. If you cannot show consent or legitimate interest, suppress the address instead of probing it. A probe is a marketing-style send.
  2. Choose a dedicated sending subdomain. Deliberate bounces count against the reputation of whatever domain you send from. Keep probes off your main brand domain.
  3. Set the windows in writing. Use a 72-hour verdict and a 7-day sweep.
  4. Map codes to actions in advance. Only 5.1.1 and 5.1.3 suppress automatically. 5.2.2, 5.4.4 and 5.7.1 are held or investigated.
  5. Analyse per domain, not just per address. If one corporate domain bounces most of its probes, its configuration is probably the cause. If a large domain shows almost no bounces across hundreds of probes, it may be accepting mail silently, which makes its survivors weaker than they look.

Run a pilot first. A few hundred addresses per major domain show how each domain behaves before you commit the full segment. Pair the probe with deep email verification vs standard verification so you know which addresses reached the probe stage and why.

Bottom line: The decisions you make before sending determine whether the test produces clean evidence or a reputation problem.

How do you run a bounce-based check with Unlimited Verifier?

Unlimited Verifier checks syntax, domain, MX records and the SMTP mailbox, detects catch-all domains, and sorts every address into Valid, Risky or Invalid. The probe send and bounce collection happen in your sending platform. Unlimited Verifier has no native ESP, CRM or Zapier integrations, so the workflow is export, verify, send, collect bounces, and re-import, or calling the API from your own scripts.

  1. Sign up for a pilot. Create a free account. The Free plan ($0) covers 25 lists a month of up to 150 emails each, plus 750 deep verifications a month, but has no API access. Pro is $29 a month, or $25 a month billed annually. When you compare email verification pricing, include the cost of the sends you will run, not the verifier fee alone.
  2. Upload your list. Use the upload and verify a list page. CSV and Excel files up to 10MB are accepted, and the email column is detected automatically. On Pro, each list holds up to 25,000 emails, so split larger files first.
  3. Read the three buckets. Valid, Risky and Invalid. Filter the Risky rows to isolate the catch-all domains.
  4. Export immediately. Export as CSV, Excel or JSON. Free-plan results are kept for 24 hours. Pro keeps them for 30 days, which covers a 7-day sweep.
  5. Remove contacts without a lawful basis. Build the probe list only from addresses you can justify contacting.
  6. Configure the send. Use your dedicated subdomain. Confirm that bounces return to a monitored address or webhook, and that your platform records enhanced status codes.
  7. Send a genuine, identified message. Probes should be a real message you are entitled to send, with a clear sender identity and a working unsubscribe. A blank test send to strangers is a complaint magnet.
  8. Wait 72 hours, then export bounces. Keep the raw file for the sweep.
  9. Classify and sort. Suppress 5.1.1 and 5.1.3. Hold 5.2.2, 5.4.4 and 5.7.1. Label silent addresses "survived probe."
  10. Sweep at day 7. Pull late bounces, then re-import survivors as a new segment.
  11. Check single cases and automate at scale. For one contact that matters, use the free email checker. For automated checks, the email verification API handles single checks and batches of up to 10,000 emails per request, with Pro including 100,000 API emails a month. This sits inside a broader email verification API and automation workflow.

Bottom line: Verify first, probe only the catch-all segment, then re-import survivors. The verifier sorts; your sending platform produces the bounce evidence.

What does a bounce-based check look like with real numbers?

This example uses a hypothetical B2B SaaS list, a common profile for email verification for ecommerce and SaaS teams. The plan limits and arithmetic are real. The percentages and send price are illustrative.

Step 1: Verify and split. A 52,000-row file goes onto Pro. The 25,000-per-list cap splits it into 25,000 + 25,000 + 2,000 = 52,000 rows.

Bucket after verification Count Share
Valid 38,400 73.8%
Invalid 6,240 12.0%
Risky 7,360 14.2%

The Risky bucket breaks down as 4,900 catch-all, 1,460 role-based (for example info@), and 1,000 other. Check: 4,900 + 1,460 + 1,000 = 7,360.

Step 2: Probe the catch-all segment. The 4,900 catch-all addresses go out from a subdomain. At a hypothetical sending rate of $1.00 per 1,000 messages, the probe costs 4,900 ÷ 1,000 × $1.00 = $4.90.

Step 3: Read at 72 hours. Assume 1,470 bounces arrive, a 30.0% rate. That leaves 4,900 − 1,470 = 3,430 silent addresses. Assume 30% of those engaged in the last 180 days: 3,430 × 0.30 = 1,029. That leaves 3,430 − 1,029 = 2,401 silent and unengaged.

Step 4: Sort the final buckets.

Check: 39,429 + 7,710 + 4,861 = 52,000.

Step 5: Re-enter carefully. Send to the Valid segment first, then the 1,029 engaged survivors. For that second batch, set a bounce ceiling of 1%, which is 1,029 × 0.01 ≈ 10 bounces. If you also deep-verify the 7,360 Risky rows, that uses 7,360 of Pro's 25,000 monthly deep verifications, leaving 25,000 − 7,360 = 17,640 for re-checks.

Cost: $29 for Pro plus the $4.90 probe, roughly $33.90 in this hypothetical.

The send cost is trivial. The real cost is the 1,470 deliberate bounces, which is why the probe runs on a subdomain. A 30% rate is illustrative. Real rates vary widely by domain, and the pilot exists to find your actual number.

Bottom line: The verifier reduced 52,000 rows to clean segments, and the probe turned 4,900 unknowns into 1,029 usable contacts and 1,470 confirmed removals.

Is it legal and safe to probe catch-all addresses?

There are two separate risks, compliance and reputation, and both need handling before you send. A sound email verification compliance and hygiene process covers both.

Compliance. In the US, the FTC's CAN-SPAM compliance guide sets the rules for commercial email. It requires accurate sender identification, a working unsubscribe, and honoured opt-outs. In the UK and EU, marketing email to individuals generally requires consent under PECR and a lawful basis under UK GDPR or the GDPR. The ICO publishes guidance on both. Apply these rules to probes, because a probe is a marketing-style send. If you lack a lawful basis for a contact, suppress the contact rather than probing it. This is general guidance, not legal advice, so check with counsel for your jurisdiction.

Reputation. Google's Postmaster Tools documentation describes spam-rate thresholds for bulk senders. Google's guidance is to stay below 0.10% user-reported spam and to avoid reaching 0.30%. Bounces are not spam complaints, but deliberate probe bounces still shape how providers see your list. Keep probes on a subdomain so your main domain's reputation stays separate.

Bottom line: Probe only contacts you have a lawful basis to message, and keep probes off your primary domain.

What are the most common mistakes?

Bottom line: Most failures come from reading a weak signal as a strong one. Decide your labels and windows before the first send.

How we compared (and limitations)

This article is based on public documentation: RFC 3463 for enhanced status codes, RFC 3464 for DSN format, RFC 3461 for DSN requests, RFC 5321 for SMTP retry behaviour, FTC and ICO guidance on email marketing, and Google's Postmaster Tools documentation. We have not run controlled tests against any mail server or ESP. Bounce timing and codes vary by receiving provider, so treat the windows and code mappings as starting points to validate in your pilot.

The worked example is illustrative. The 30% bounce rate, the 30% engagement share and the $1.00 per 1,000 send rate are hypothetical, not benchmarks or quoted prices.

Unlimited Verifier details come from its published plan facts. Its stated accuracy of 99.5% for deep verification is the company's own figure, not an independent benchmark. The verification engine is published on GitHub at github.com/unlimitedverifier/free-email-verifier, so its code can be inspected directly. Unlimited Verifier identifies catch-all domains and sorts results; this article does not describe it sending probe messages or reading bounces. Those steps happen in your own sending platform.

If you are choosing a verifier for a catch-all-heavy list, how to choose an email verifier lists the questions to ask. The catch-all email verification page explains how Unlimited Verifier handles catch-all domains. For the probe family in more depth, read send-based catch-all verification. Also review real-time email validation so new catch-all sign-ups are handled at entry, not after they bounce.

Bottom line: Run a pilot on a few hundred addresses per major domain, record your windows and code mappings, and let your own bounce data set the final rules.

Bounce verdict framework

Signal in window Verdict Action
Permanent 5.1.1 bounce Invalid Suppress
Temporary 4.x.x bounce only Unknown Retry later
No bounce after 72h and 7-day sweep Unknown, not valid Engagement check before sending
Recent opens or clicks Engaged Prioritize for send

Frequently asked questions

What is a catch-all domain?

A catch-all domain is a mail domain configured to accept messages for any local part, so every RCPT TO returns an accept reply at the SMTP layer. That means the server's acceptance does not confirm that a specific mailbox exists. Checking catch-all addresses requires a second signal, such as a bounce.

What is enhanced status code 5.1.1?

Enhanced status code 5.1.1 is a permanent failure meaning the recipient address does not exist or is unknown to the server. It is the strongest bounce signal for marking an address invalid. Temporary codes in the 4.x.x range should not be treated as proof of invalidity.

Why use a 72-hour verdict window?

The 72-hour window is this guide's recommended default, not an industry standard, because no published standard sets one. Receiving servers often defer messages before failing them, so failures can arrive days later. A 7-day sweep then catches late bounces.

Does silence mean an address is valid?

No. Silence only shows that no permanent failure arrived inside the observation window. Some mailboxes accept mail and never bounce, and some bounces arrive late, so an address with no bounce should be treated as unknown rather than confirmed valid.

What is VERP and why does it matter here?

VERP, or variable envelope return path, encodes the recipient address into the return-path so each bounce can be matched to its address without parsing message text. Some sending platforms apply it automatically, so check your platform's settings before relying on it.

Should I probe from my main sending domain?

A separate probe subdomain is safer. Test sends can generate bounces and complaints, which can affect the reputation of your primary domain. Isolating probes keeps your production sending reputation protected while you classify addresses.

Are bounce-based checks billed per email?

Verification itself can be billed differently from sending. Probe sends are typically billed by your sending platform, so the verifier's cost and your ESP's cost are separate line items. Check both pricing pages before estimating the total.

Should I send to catch-all survivors before others?

No. Send to survivors last, after an engagement check, because a catch-all address that passes a bounce test can still be low-engagement or a role mailbox. Prioritize contacts with recent opens or clicks over those with only a clean bounce result.

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.