What is a catch-all email address? Pros and cons

A catch-all is a setting that accepts mail sent to any address on your domain, whether you created it or not. With a catch-all on example.com, a message to [email protected] lands in a mailbox you choose. Without it, the same message bounces with 550 5.1.1 user unknown.
Why people use one
- Typos.
[email protected]or[email protected]still reaches you. - Old addresses. Someone who left or a former team address keeps receiving, and you can see who still writes to it.
- Throwaway addresses. You can give each website its own address, such as
[email protected], without creating anything. If spam arrives at one, you know who leaked it. - Letting nothing slip by when customer mail is the heart of the business.
The costs
Spam. Spammers guess common names at known domains, a practice called a dictionary attack. A normal domain refuses them all. A catch-all accepts all of them and turns the noise into your problem.
Reputation. If your catch-all mailbox forwards to Gmail or Outlook, the spam goes with it, and that can damage the reputation of your forwarding server. See how forwarding interacts with filters.
Less reliable address validation. Email verification tools cannot tell whether a given address exists on a catch-all domain, so they label it "accept-all" or "risky". Some senders then skip you or treat you with caution.
Lost signal. Senders stop learning that an address is wrong. Someone who misspells a colleague's name gets no error, and thinks the message was delivered.
A safer way to use one
- Give it a dedicated destination. Use a separate mailbox or folder, never someone's main inbox.
- Keep spam filtering on. Filter before anything is forwarded.
- Look at it weekly. Turn repeated typos into proper aliases, then remove the noise.
- Consider an allowlist. Most of the benefits come from a few specific aliases, which attract none of the spam:
support@,sales@,billing@,contact@. - Turn it off if spam takes over. There is no harm in going back.
Frequently asked questions
Does a catch-all affect my sending?
Not directly, since it only concerns incoming mail. The indirect effect comes through forwarding, or through the time your team wastes on noise.
How do I know if a domain has a catch-all?
Send to a random address on it. If there is no bounce, it probably has one, though some servers accept during delivery and drop it later, so the test is not certain.
Is a catch-all dangerous for security?
It can receive password reset messages meant for a former colleague's address, so whoever reads the catch-all gets those too. Restrict access to it, as you would for any shared mailbox.
Can I have a catch-all on a subdomain only?
With many providers, yes. Using a subdomain for throwaway addresses ([email protected]) keeps the noise away from your main domain, since subdomains have their own MX records.
Smailor offers a catch-all on the Pro and Business plans, so mail to any address on your domain lands somewhere instead of bouncing, and routing rules can send it to the right group.