Article

What Does Accept-All Mean in an Email Verifier?

By Unlimited Verifier Team ·

Diagram showing a verifier checking an accept-all email domain, where a random nonexistent address also receives a 250 OK reply.

Summary

In an email verifier, accept-all (also called catch-all) means the recipient's mail server replies 250 OK to every address checked, so the specific mailbox cannot be confirmed. Treat accept-all results as risky or unconfirmed rather than valid, and send to them last.

In an email verifier, accept-all (also called catch-all) means the recipient's mail server answers "250 OK" to every address the verifier asks about, so the specific mailbox can't be confirmed. Treat it as unconfirmed, not valid.

Most verification problems in large lists don't come from obviously fake addresses. They come from addresses that pass syntax and domain checks but sit on a domain that says yes to everything. Knowing how to read accept-all results is what separates a clean list from one that quietly damages your sender reputation.

Quick answer

What does accept-all mean in an email verifier?

Accept-all is a server behaviour, not a verdict about a person. The receiving server accepts recipients without checking whether each mailbox exists, often so that no legitimate message is lost to a typo. The verifier can't tell a real mailbox from an invented one on that domain, so every address there gets the same answer.

"Accept-all" and "catch-all" are two names for the same status. Vendors use both, and you'll see both in documentation and exports.

That makes accept-all a domain-level status. If jane@example.com is accept-all, so is ghost-12345@example.com, and so is every other address on that domain in your list. The status belongs to the domain. It tells you nothing about any individual on it.

Accept-all is one of several outcomes a verifier can return. For the full set of result categories, see what does deliverable mean in email verification.

Bottom line: Accept-all describes the domain's server, so one result applies to every address on that domain.

Why can't a verifier confirm an accept-all address?

A verifier can only confirm a mailbox if the server's reply depends on whether that mailbox exists. An accept-all server's reply doesn't depend on that, so the check returns no useful information.

Here is the sequence. The verifier connects to the domain's mail exchanger and issues RCPT TO with your address. A server that checks recipients replies 250 if the mailbox exists and 550 5.1.1 if it doesn't. The 5.1.1 code means "bad destination mailbox," as defined in RFC 3463. For a server that checks, that difference is a fair signal. For an accept-all server, the reply comes back 250 without any lookup.

RFC 5321 defines SMTP commands and reply codes. It leaves recipient validation to each server and doesn't require a server to confirm every mailbox at RCPT TO, which is why this behaviour exists. For the mechanics in more detail, see what does RCPT TO mean in email verification.

SMTP reply during the check What it tells the verifier Typical label
250 for your address, 550 5.1.1 for a random probe The server checks recipients Not accept-all; result depends on your address's reply
250 for your address and for a random probe The server accepts everything Accept-all
550 5.1.1 for your address Mailbox doesn't exist Invalid
4xx temporary failure Greylisting, rate limiting or a busy server Retry, or Unknown
No response or timeout Server unreachable or blocking checks Unknown or Risky

You can reproduce the check by hand with an SMTP session, but you'll get the same answer. The probe tests the domain, not the mailbox.

Bottom line: Accept-all returns the same 250 for every address, so a positive reply can't prove a specific mailbox exists.

How does a verifier detect an accept-all domain?

The common method is a probe: a second address that almost certainly doesn't exist, sent to the same domain. If the server accepts both the real address and the probe, the domain is accept-all. Check your vendor's documentation for its exact method, since implementations differ.

  1. Find the mail exchanger. The verifier looks up the domain's MX records to find the server that receives mail. For more on that step, see how do verifiers check if a domain accepts mail.
  2. Check your address. It opens an SMTP session and sends RCPT TO for your address.
  3. Send the probe. It sends RCPT TO for a random local part at the same domain, such as a long string of letters and numbers.
  4. Read both replies. If both get a 250, the domain is accept-all. If the probe gets a 550, the server checks recipients, and your address's 250 carries real information.
  5. Close without sending. The verifier normally ends the session before the DATA command, so no message body is delivered.
  6. Apply the verdict to the domain. Every address on that domain in the batch inherits the accept-all status.

Step 4 has a trap. A server that greylists unknown senders may return a temporary 4xx for the probe, which looks like a failure rather than a verdict. Good verifiers retry and treat an ambiguous result as unknown, not as proof. When you review results, check whether a domain was flagged on a clean probe or on a temporary error. For how verifiers reach these checks in practice, see how do verifiers detect catch-all domains and how does bounce-based catch-all verification work.

Bottom line: A reliable accept-all flag needs a clean probe reply, and one ambiguous response shouldn't decide a domain's status.

Is an accept-all address valid, risky or invalid?

An accept-all address is unconfirmed. It isn't valid, because nothing confirms the mailbox. It isn't invalid either, because the server didn't reject it. Risky is the honest label.

Teams handle accept-all results in four main ways. The right choice depends on your sending goals and how much risk your sender reputation can absorb.

Approach How it treats accept-all Advantage Drawback Best fit
Treat as Valid Send normally Maximum reach Inflates your Valid count and bounce exposure Rarely justified; avoid for cold or old lists
Hold as Risky Exclude from main sends; send last Protects reputation on the core list Gives up some reachable, real contacts Most senders, especially with mixed or old data
Send-test Send a small test and watch for bounces Gives real evidence over time Mail goes to an unconfirmed address; bounces can arrive later Engaged segments with consent records
Engagement overlay Judge by opens, clicks and purchases Uses behaviour, not just the domain Needs historical engagement data Customer lists with active tracking

We recommend holding accept-all addresses as Risky and releasing them in stages based on engagement. The verifier can't separate real mailboxes from fake ones on that domain, so the only reliable evidence is how people respond to your mail over time.

Bottom line: Treat accept-all as Risky, and let engagement, not the domain's 250, decide when a contact moves into your main sends.

Do accept-all addresses actually bounce?

Often not in the way you expect. An accept-all address has three possible outcomes, and only one of them shows up in your bounce report.

The third outcome is the one to watch. A segment full of silently dropped addresses can show a low bounce rate while opens fall to zero. Your bounce count looks healthy, but your engagement and complaint signals tell a different story.

Security gateways add a further wrinkle. Some corporate mail systems accept every message at SMTP and filter it afterwards. Real people's mail can therefore look accepted in the same way as mail to mailboxes that don't exist.

Complaints are the other risk. Google's sender guidelines recommend keeping spam rates below 0.1% and warn senders against reaching 0.3%. Sources differ on where the line sits, so we recommend the stricter 0.1% as your working target. Recipients on accept-all domains who don't remember opting in are a common source of complaints, and one bad cohort can push a campaign past that line.

Bottom line: A bounce report won't show silent drops, so watch opens and complaints for each cohort, not just bounces.

How common are accept-all addresses in a list?

There is no reliable public benchmark for the share of accept-all addresses in a typical list. It varies by industry, region and how the list was built. Lists built from corporate domains often contain more accept-all results than consumer lists, though this depends on each provider's SMTP behaviour, so measure your own list.

As a working threshold, not an industry standard, we suggest investigating your sources if accept-all addresses exceed roughly 10% of a list. A high share often points to a particular import, event list or scraped contact set.

The breakdown matters more than the headline figure. Split the share by domain and by sign-up source. Two lists with the same 12% accept-all share can carry very different risk, depending on whether that 12% came from a trusted customer form or a purchased file.

Bottom line: Your own accept-all share, broken down by source, is more useful than any industry average.

How should you send to accept-all addresses?

Send in a controlled, staged way: start with the most engaged addresses and stop if bounces or complaints rise.

  1. Segment them. Keep accept-all addresses in their own list or tag, so they never join your main sends by accident.
  2. Rank by recent engagement. Sort by opens or clicks in the last 90 days, then by purchase history. Recent engagement is the strongest signal you have.
  3. Run a small test. Send to a few hundred of the top-ranked addresses and measure bounces within 48 hours.
  4. Apply a stop rule. If bounces stay under 1% and you see no spam complaints, expand to the next group. If bounces go over 1%, stop the cohort.
  5. Hold the rest. Keep unengaged accept-all addresses out until you have evidence they respond.
  6. Re-verify and prune. Re-check the domain status monthly, because domain owners can change server settings, and remove addresses that stop engaging.

Each step addresses a specific failure. Segmentation prevents accidental mixing. Ranking puts your best evidence first. The stop rule limits the damage from a bad cohort before it reaches the whole list. Note that a 300-address test gives you a rough signal, not a precise rate, so widen the sample before drawing firm conclusions. For a wider view of keeping lists healthy, see email list maintenance best practices.

Bottom line: Staged sending with a hard stop rule lets you learn from accept-all addresses without betting your reputation on them.

How do you find and segment accept-all addresses step by step?

Here is how to isolate accept-all results in Unlimited Verifier. The steps assume you have a CSV exported from your email service provider.

  1. Export your contacts. Include the email column and at least one engagement field, such as last open date. Keep the export as your untouched backup.
  2. Sign up for a free account. The Free plan allows 25 lists a month of up to 150 emails each, enough to test a sample first. You can also use the free email checker to spot-check individual addresses.
  3. Upload and verify a list. Upload a CSV or Excel file up to 10MB. The email column is detected automatically. On Pro, each list can hold up to 25,000 addresses, so split larger files first.
  4. Run verification. It checks syntax, domain, MX records and the SMTP mailbox, and detects catch-all domains. It also flags disposable and role-based addresses, which you should review separately. Standard verification is unlimited on all plans.
  5. Filter for the catch-all result. Use the catch-all flag in your export to pull out accept-all addresses. Confirm they sit in your Risky group, not Valid. If the export doesn't place them there, move them yourself.
  6. Decide on deep verification. Deep verifications come from a separate allowance: 750 a month on Free and 25,000 on Pro. Spend them on a segment you have chosen, such as your highest-value accept-all contacts. The catch-all email verification page describes how these results are handled. For the difference between the two modes, see deep email verification vs standard verification.
  7. Export and save immediately. Export as CSV, Excel or JSON. Results are kept for 24 hours on Free and 30 days on Pro, so save a copy the same day.
  8. Re-import as separate segments. There are no native integrations with email service providers, CRMs or Zapier. Re-import Valid contacts and the accept-all segment as separate lists or tags, and label each one clearly. If you prefer automation, the email verification API lets you call checks from your own scripts, and the email verification API and automation approach covers the setup.

Bottom line: Export, verify, filter the catch-all results, save the output and re-import each segment separately.

What does an accept-all cleanup look like on a 40,000-row list?

This example is hypothetical, but the arithmetic and plan limits are real.

Setup: A B2B software company has 40,000 contacts, mostly from trade-show scans and a partner import. Its Pro plan allows 25,000 addresses per list, so it splits the file into two lists: 25,000 and 15,000.

Hypothetical results:

Verdict Count Share of 40,000
Valid 32,400 81%
Accept-all (Risky) 4,800 12%
Other Risky 800 2%
Invalid 2,000 5%
Total 40,000 100%

Check: 32,400 + 4,800 + 800 + 2,000 = 40,000.

Deep verification: Running deep verification on all 4,800 accept-all addresses would use 4,800 of the 25,000 monthly deep verifications, leaving 20,200. That is within the cap, though whether it adds value for each address depends on the test you run on a sample first.

Cost: One month of Pro at $29 covers 40,000 addresses, which works out to $29 ÷ 40 = $0.73 per 1,000 addresses checked. On annual billing at $25 a month, the same month comes to $25 ÷ 40 = $0.63 per 1,000. For a broader view of how verification is priced, see email verification pricing.

Staged send to the accept-all segment:

Stage Addresses sent Bounces Bounce rate Decision
Test 300 (most engaged, opened in 90 days) 2 0.67% Under 1%: continue
Wave 2 850 (next most engaged) 6 0.71% Under 1%: continue
Cumulative 1,150 8 0.70% Hold the remaining 3,650

Check: 2 ÷ 300 = 0.67%; 6 ÷ 850 = 0.71%; 8 ÷ 1,150 = 0.70%.

The remaining 3,650 stay in quarantine until a 60-day engagement review shows they respond. If the whole 4,800 cohort had bounced at 4%, that would add 192 bounces to the 40,000-row list, or 0.48% of the total. That's a small share, but it still counts toward your sending ceiling.

Bottom line: Splitting the file keeps you within the per-list cap, and a staged send turns an unknown cohort into measured data.

What mistakes do teams make with accept-all results?

Bottom line: Most accept-all mistakes come from reading the server's 250 as proof of a mailbox.

How we compared (and limitations)

This article is based on public documentation: RFC 5321 and RFC 3463 for SMTP behaviour and status codes, and Google's sender guidelines for the spam-rate thresholds. We have not run controlled tests against mail servers across providers, and server configurations change without notice.

Unlimited Verifier's plan limits and features come from the company's own published details. The company states 99.5% accuracy for deep verification; that is its own figure, not an independent benchmark. Every percentage and count in the worked example is hypothetical and included only to show the arithmetic.

For background before you interpret accept-all results, start with how email verification works. If you're comparing products, the guides to best email verification tools and how to choose an email verifier explain what to check, and real-time email validation covers how to apply the same logic at signup.

Bottom line: Treat the figures here as public-documentation context and a worked example, and confirm plan limits against your own list before you commit.

Accept-all handling steps

  1. Run syntax and domain checks first.
  2. Run an SMTP check and note the RCPT TO reply.
  3. If the target gets 250, send a random nonexistent address on the same domain.
  4. If that also gets 250, label the domain accept-all.
  5. Classify the result as Risky, not Valid.
  6. Send to confirmed valid addresses first.
  7. Mail accept-all addresses last and track opens and complaints by cohort.

Frequently asked questions

Is an accept-all email address valid?

Not necessarily. Accept-all means the domain accepts any address, so a verifier cannot confirm that the specific mailbox exists. Most verifiers label these results as risky or unconfirmed rather than valid, and teams typically send to them last in a campaign.

What is the difference between accept-all and catch-all?

There is no practical difference. Accept-all and catch-all are two names for the same server behaviour, where the domain accepts mail for any recipient. Vendors use both terms, so you may see either in documentation and exported results.

How does an email verifier detect accept-all?

The verifier sends a random, almost certainly nonexistent address on the same domain through the SMTP RCPT TO step. If that address also receives a 250 response, the domain is marked accept-all. This is a domain-level check, not a per-person check.

Will emails to accept-all addresses bounce?

Sometimes not. Some accept-all servers accept mail and then silently drop it or filter it, so no bounce is generated. This is why bounce rate alone can understate problems, and tracking opens and spam complaints by cohort gives a clearer picture.

Should I remove accept-all emails from my list?

It depends on your goals and risk tolerance. Many senders hold accept-all addresses back and mail them last, after confirmed valid addresses, and monitor engagement closely. Removing them entirely is a conservative option if list quality is the priority.

Why do some domains accept all email addresses?

Mail administrators often enable catch-all so that messages to misspelled addresses still reach someone rather than bouncing. The setting is a choice made by the domain owner, and it does not indicate whether any particular mailbox is active.

Can an email verifier ever confirm an accept-all address?

Generally no, not through SMTP alone. Because the server replies 250 regardless of whether the mailbox exists, the response carries no information about that mailbox. Some tools use additional signals, but these are probabilistic rather than confirmation.

Does RFC 5321 require servers to validate every recipient?

No. RFC 5321 defines SMTP commands and reply codes but leaves recipient validation to each server's policy. That is why accept-all behaviour exists and why verifiers cannot rely on RCPT TO for every domain.

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.