Catch-All Email Checker

✓ Email verification

Find out whether a domain accepts mail for every address — where SMTP acceptance no longer proves a mailbox is real.

No sign-up required Runs on our own infrastructure Also available via API

Runs on our diagnostic API. We don’t attach your input to an account for these free tools; short-lived rate-limit/security logs may exist, and requests are rate-limited per IP.

Email verification usually works by asking a domain’s mail server, politely and without ever sending a message, “would you accept mail for this address?” On most domains a clear no means the mailbox doesn’t exist and a yes means it does. Catch-all domains break that logic. They’re configured to say yes to everything, which means the usual SMTP probe can’t tell a real mailbox from a made-up one — and that’s why addresses at these domains come back as risky or unknown rather than a confident valid.

What “catch-all” means

A catch-all (also called accept-all, or sometimes a “verify-all” from the checker’s point of view) domain routes any address at the domain — anything@example.com, whether or not it was ever provisioned — to a single mailbox or destination instead of rejecting the unknown ones. Admins set this up for legitimate reasons: to avoid losing mail sent to a slightly-misspelled address, to capture role-style aliases without creating each one, or just because the default configuration on some hosted platforms is accept-all. The behaviour is invisible to senders until you actually test it.

Why it defeats normal SMTP verification

Ordinary email verification leans on the SMTP conversation: after connecting to the domain’s MX server, the verifier issues RCPT TO for the address and reads the response code. A 550 (or similar) means “no such user” — a confident invalid. A 250 normally means the mailbox exists. On a catch-all domain, every RCPT TO returns 250, including for an address you just invented. So the accept tells you nothing specific.

To detect this, the checker does exactly what a careful human would: it probes the domain with a random address that almost certainly doesn’t exist. If that obviously-fake address is also accepted, the domain is behaving as catch-all, and any “accepted” result for a real address is downgraded accordingly. No message is ever delivered — the conversation is closed before DATA.

RCPT TO:<definitely-not-real-9f3a@example.com>   250 OK   ← accepts a fake address => domain is accept-all; SMTP acceptance no longer proves a mailbox exists

How to handle catch-all results

A catch-all verdict is a “proceed with caution,” not a delete signal. Some of the most valuable business domains are catch-all. What you shouldn’t do is treat the address as fully verified. Sensible approaches:

  • Don’t auto-discard. Plenty of catch-all addresses are perfectly real, deliverable inboxes.
  • Don’t treat as confirmed either. Segment catch-all/risky addresses separately from your confidently-valid ones.
  • Lean on real engagement. An open, a click, or a completed double opt-in is far stronger evidence than any SMTP probe can give you on these domains.
  • Warm cautiously. If you must mail a batch of catch-all addresses, send to them gradually and watch bounce and complaint rates before committing your whole list.

Where this fits

Catch-all detection is one component of a full verdict, not a standalone judgement. The Email Verifier runs it as part of a larger pipeline — syntax, MX, SMTP, disposable and role checks — so a catch-all domain gets flagged in context rather than in isolation. If you want to see the raw SMTP exchange for a domain yourself, the SMTP Test shows the live conversation, and MX Lookup confirms which servers you’d be talking to in the first place.

Frequently asked questions

What is a catch-all (accept-all) email domain?
A domain set up to accept mail for any address at the domain — even ones that don’t exist — instead of rejecting the unknown ones. Because it accepts everything, an SMTP “accepted” no longer proves a specific mailbox is real.
Why does a catch-all address show as risky or unknown?
Because verification relies on the server rejecting non-existent addresses. A catch-all accepts them all, so a specific mailbox can’t be confirmed — hence risky/unknown instead of a confident valid.
Does the checker send an email to detect catch-all?
No. It opens an SMTP session, issues RCPT TO for a random fake address, and closes before DATA. If the fake address is accepted, the domain is catch-all — and no message is ever delivered.
Should I remove catch-all addresses from my list?
Not automatically — many are real inboxes, including important business domains. Segment them apart from confidently-valid addresses and lean on engagement (opens, clicks, double opt-in) as the stronger signal.