Home/Catch-All Email
The verification edge case explained

Catch-All Email Addresses:
What They Are and What to Do With Them

Some domains accept email sent to any address — real or invented. These are called catch-all domains, and they present a unique challenge for email verification. Here is what you need to know.

Normal domain

A standard mail server accepts email only for mailboxes that actually exist. Send to a non-existent address and the server responds with a 550 error— “No such user here.”

→ john@company.com — ACCEPTED (mailbox exists)
→ xyz999@company.com — REJECTED (no mailbox)

Catch-all domain

A catch-all mail server accepts everything. There is no way to distinguish a real mailbox from a made-up one at the SMTP level.

→ john@catchall.com — ACCEPTED (mailbox exists)
→ xyz999@catchall.com — ACCEPTED (no mailbox!)

Why StopBouncing marks these as "Unknown"

Any tool that marks catch-all addresses as “valid” is misleading you — it cannot know whether the specific mailbox exists. StopBouncing honestly classifies catch-all addresses as Unknown. This gives you accurate information so you can make an informed decision, rather than false confidence that leads to bounces.

Should You Send to Catch-All Addresses?

Use these signals to guide your decision.

Address came from a form the user typed themselves

Generally safe to send — the user chose their own email.

Address has previous engagement (opens, clicks)

Safe to send — engagement proves deliverability.

Address came from a purchased or scraped list

Do not send — risk of bounce outweighs potential engagement.

Address has no engagement history

Send a low-risk re-engagement first. Monitor bounce rate carefully.

Domain is a free provider (gmail.com, outlook.com)

Free providers don't use catch-all — this should not happen. Flag for review.

Catch-All Email FAQ

What is a catch-all email domain?

A catch-all domain (also called an accept-all domain) is configured to accept email sent to any address at that domain, regardless of whether the specific mailbox exists. For example, if example.com is a catch-all, sending to xyz123@example.com and john@example.com will both appear to succeed at the SMTP level — even if the mailbox xyz123 doesn't exist.

Why can't catch-all emails be verified?

Email verification works by simulating a message delivery and checking whether the mail server accepts or rejects the address. On a catch-all domain, the server always responds positively — it cannot distinguish between real and fake mailboxes. This makes it impossible to determine with certainty whether any specific address at a catch-all domain actually has a mailbox.

How does StopBouncing classify catch-all addresses?

StopBouncing marks catch-all addresses as 'Unknown' — never as valid or invalid. This honest classification prevents you from accidentally treating unverifiable addresses as confirmed deliverable, which could lead to bounces and reputation damage.

Should I send to catch-all addresses?

It depends on the source and context. Catch-all addresses from forms you control (where the user typed their address) are safer to send to than purchased lists. If you have engagement data (opens, clicks) for an address on a catch-all domain, that's a stronger signal of deliverability than verification alone. Consider sending a re-engagement campaign first.

How common are catch-all domains?

Catch-all configuration is especially common in corporate environments where system administrators set up catch-all to avoid missing emails sent to slightly wrong addresses. Estimates suggest between 5% and 20% of business email domains are configured as catch-all.

Get Honest Verification Results

StopBouncing never lies about catch-all addresses. Unknown means unknown. 100 free credits to start.