Catch-all domain checker

What this checker answers

One question: does this domain accept mail to any address? If yes, no verifier can confirm a specific mailbox there. If no, a mailbox-level check is meaningful.

You still type a name and domain (or an address, via the same public finder). We probe a local-part that cannot belong to a person. Accept → catch-all. Reject → not a catch-all, and we can then ask about the real candidate.

This uses a free daily lookup because it talks to a mail server. DNS-only tools on this site do not.

Why catch-alls exist

From IT's point of view, a catch-all is convenient. Misspelled addresses still arrive. Departed employees' mail can land in a shared box. There is no public directory to scrape. From a sender's point of view, a catch-all is a trap: every guess "succeeds," nothing bounces, and you learn nothing.

Mailbox providers still see the *downstream* effects — spam complaints, low engagement, users hitting delete — even when they do not see hard bounces. A catch-all list can wreck reputation without a bounce-rate alarm going off. That is the opposite of safety.

How we detect it

We look up MX, connect, and ask whether a reserved, implausible local-part exists. A server that says yes to that is not telling you about a person. It is telling you about its policy.

Some servers lie in other ways (greylist everything, tarpit probes, accept then bounce later). We label what we can observe. We do not invent a "99% confidence" number on top of a catch-all.

What to do when a domain is catch-all

• Do not send a guessed address from a warming domain. You will not get a bounce to teach you, and you may get a complaint.
• Look for another domain at the same company. MX lookup on brand.com vs corp.brand.com vs a country TLD sometimes shows one catch-all and one not.
• Use a second channel first. If they reply on LinkedIn, you can send with eyes open.
• Skip. This is allowed. A list of 200 verified people is a list. A list of 2,000 catch-alls is a wish.

We do not charge for catch-all results. There is no incentive here to hide the flag.

Catch-all vs "accept then drop"

A true catch-all accepts at SMTP. Some companies accept at SMTP and later discard unknown local-parts. From the outside those look identical at verify-time. You still cannot confirm the person. Treat both as unconfirmed.

How this page differs from the finder

The form is the same public finder. The reason this URL exists is intent: people searching "catch-all checker" do not want a lecture on patterns. They want a labelled answer for a domain they already distrust.

If the result is not catch-all, keep going — the mailbox verdict on this same lookup is the useful part. If it is catch-all, stop treating the address column as a fact.

A fictional walkthrough

Jane Doe appears to work at company.com. You run this checker.

• Probe to a nonsense local-part is rejected, and jane.doe@company.com is accepted → not a catch-all, mailbox verified. Sendable.
• Probe to a nonsense local-part is accepted → catch-all. The pattern jane.doe@ is still the most likely, and it is still unconfirmed. Do not put it in a warmup.
• Everything rejected → not a catch-all, not found. Try another domain at the company with MX lookup.

Jane Doe is not a real person at that domain.

What vendors sometimes do instead

Some products never mention catch-alls. They return a confidence score on every row. A high score on a catch-all domain is a guess with a progress bar.

Ask one question of any vendor: "If I verify zzzzz@that-domain.com, what status do I get?" If the answer is verified, they are checking the domain, not the mailbox. More on that.

Billing

Catch-all results are free here. Repeats are free. You pay when a *specific* mailbox is confirmed. That is the only status that should cost money, because it is the only status that should go into a sequencer.

Related reading

• Catch-all domain
• Free email verifier
• Why “verified” email finders often aren’t
• MX lookup when you suspect mail lives on a different domain