A catch-all email address is a mailbox that receives every message sent to your domain, including messages sent to addresses you never created. If someone writes to sales@yourdomain.com and you only have info@yourdomain.com, the catch-all picks up the message instead of letting it bounce. You set it up in your email host's control panel, point it at one mailbox, and then keep that mailbox under control with a few simple habits. This guide covers all of it.
TL;DR
- A catch-all routes mail for any unrecognized address on your domain to one mailbox, so typos and old addresses don't lose messages.
- In cPanel it lives under Email > Default Address. In Google Workspace it is a routing rule in the Gmail admin console.
- Send catch-all mail to a dedicated mailbox, not your main inbox, because it will also collect spam.
- Use it for migrations, staff changes and small teams, then review it on a schedule and filter it.
- Set up SPF, DKIM and DMARC properly so forwarded and routed mail keeps passing authentication.
Table of Contents
- What a catch-all email address actually does
- When a catch-all is worth using
- How to set up a catch-all email address
- Keep the catch-all mailbox under control
- Authentication when mail is forwarded or rerouted
- Alternatives to a full catch-all
- Our perspective
- Run your domain email with inSave Hosting
- FAQ
- Sources
What a catch-all email address actually does
Every email address has two parts: the local part before the @ and the domain after it. Your mail server normally checks the local part against the mailboxes and aliases you created. If it finds a match, the message is delivered. If it doesn't, the server rejects the message and the sender gets a bounce notice.
A catch-all changes that last step. Instead of rejecting, the server accepts the message and delivers it to the address you chose. Mail for typo@, oldname@ or anything-at-all@ all lands in the same place.
The feature is usually described the same way across providers: mail sent to a domain that doesn't match an existing address is delivered to the catch-all address you specify. The naming varies. Some control panels call it a default address, some call it a wildcard, and some write it as *@yourdomain.com.
The catch-all only works if your domain's mail is routed correctly in the first place. The MX record tells the rest of the internet which server accepts mail for your domain. Lower priority numbers are preferred, and the destination must be a hostname rather than an IP address. If MX records point somewhere else, a catch-all rule on your hosting account will never see the mail. Our guide to DNS management for website owners explains where those records live and how to read them.

When a catch-all is worth using
A catch-all is a tool for specific situations. These are the ones where it earns its place.
Migrating or rebranding
When you move from old addresses to a new domain or naming scheme, people keep writing to the old ones for months. A catch-all makes sure none of that mail disappears while contacts update their address books. One guide recommends setting it up during the migration, watching it for three to six months, and turning it off once traffic to old addresses fades. That is a sensible window to plan around.
Staff changes
When someone leaves, their address often keeps receiving vendor emails, invoices and customer replies. Deliverability specialist Al Iverson notes that a catch-all is an easy way to redirect mail when people leave, so follow-up such as incoming invoices isn't missed. For a small business without a formal offboarding process, that is a real safety net.
Small teams that can't predict every address
If you are a small team and customers guess at addresses such as support@, billing@, hello@ or orders@, a catch-all means they all reach you. You don't have to create a dozen aliases up front. Industry write-ups also list compliance and audit trails, and unique per-service addresses for leak detection, as reasons organizations enable one.
Tracking who shares your address
Because any address works, you can sign up for each service with a different one, such as shop-brandname@yourdomain.com. If spam arrives at that exact address, you know who passed it on. You can then create a filter or a real alias for that address if you want to block it.
How to set up a catch-all email address
The steps differ by platform, but the logic is always the same: confirm your MX records point at the mail service, turn on the catch-all rule, and choose the destination mailbox. A 2026 setup guide describes the same three moves for any provider: point MX records at the mail service, enable the catch-all rule, and pick the mailbox that receives mail for nonexistent addresses.
Before you start
- Create the mailbox that will receive the catch-all mail. A name like
catchall@yourdomain.comworks well. - Check that your domain's MX records point at the service that hosts that mailbox.
- Confirm you can log in to that mailbox and see it in webmail or your mail app.
If you are still putting email on your domain for the first time, our step-by-step email setup guide and our overview of web host email for small business cover those basics.
In cPanel
On hosting that uses cPanel, cPanel's own documentation says to configure the catch-all under Email > Default Address. In practice:
- Log in to cPanel and open the Email section.
- Open Default Address and select your domain if you have more than one.
- Enter the address that should receive unrouted mail, or choose to forward to it.
- Save, then send a test message to a made-up address on your domain and confirm it arrives.
Note that the other option in that screen is to discard unrouted mail with an error. That is the standard rejecting behavior, and it is the one most hosts use by default.
In Google Workspace
Google Workspace has no single catch-all toggle. An administrator builds a routing rule. According to Google's admin help, you go to Apps > Google Workspace > Gmail > Routing, choose Modify message, check Change envelope recipient, choose Replace recipient and enter the catch-all address. The same page says to check the box for all inactive and unrecognized accounts so the rule applies only to addresses that don't exist.

Only an administrator can do this, and the rule applies to the whole domain, so test it with a throwaway address before relying on it.
Other platforms
Some email services offer no catch-all at all, while others use a wildcard address written as *. A comparison of providers in a 2026 setup guide shows how different the options are. If your current mail service doesn't support it, the cleanest fix is to host the mailboxes where the feature exists, or to create specific aliases for the addresses you expect.
Keep the catch-all mailbox under control
The tradeoff of accepting everything is that you receive everything. Spammers send mail to guessed addresses such as admin@, billing@ and random strings in what are called dictionary attacks. A catch-all accepts every guessed or misspelled address and with it every message sent to random addresses, so spam volume rises. It also removes the rejection that lets legitimate senders discover their own typos.
That is manageable, and the habits below keep a catch-all useful.
Use a dedicated mailbox
Don't send catch-all mail to your main inbox. Create a dedicated address in your domain, such as catchall@ or contact@, to receive it. Check it on a schedule instead of letting it interrupt your day. A separate mailbox also means your regular inbox filtering and your sending reputation stay clean.
Review on a schedule
Pick a rhythm that fits the reason you turned it on. During a migration, scan the mailbox weekly and create real aliases for any address that keeps getting legitimate mail. For a small team, a monthly look is often enough. Each time you find a legitimate address, create it as a proper mailbox or alias so it no longer depends on the catch-all.
Filter aggressively
Use server-side or client-side rules to sort the catch-all mailbox. Common approaches:
- Auto-delete mail to addresses you know are only spam targets.
- Move anything with obvious spam markers to a junk folder.
- Flag mail from known customers or vendors so it stands out.
- Keep spam filtering turned on for the catch-all mailbox, the same as any other.
Know the sender's view
Because nothing bounces, a sender who mistypes your address won't be told. They may believe they reached you when the message went to the wrong place. That is the reason to review the mailbox regularly: it's where those misdirected messages land. Another consequence: services that try to verify addresses by asking your server will get a yes for everything. As Iverson points out, SMTP verification will struggle because your server never gives a negative response.
Plan to turn it off
If the catch-all was for a transition, give it an end date. If it is permanent, decide which addresses matter and convert them to real aliases over time. Security researchers warn that spam lists never prune addresses, so volume can stay high even after you disable a catch-all. That is one more reason to enable it with intent and keep its mailbox separate from the start.
Authentication when mail is forwarded or rerouted
A catch-all often works by forwarding, and forwarding can break email authentication. SPF checks that the sending server is allowed to send for the domain. When a server forwards a message, the forwarder's IP is not on the original sender's SPF list, so SPF can fail.
Microsoft's documentation describes the Sender Rewriting Scheme, which rewrites the MAIL FROM address on applicable messages sent to external recipients to solve the incompatibility between autoforwarding and SPF. The same page is clear about the limit: SRS does not fix forwarded messages failing DMARC. The reliable way to pass is a DKIM signature that uses the From address's domain and stays intact in transit.
For you, that means two practical things:
- Keep the catch-all mailbox on the same service as the domain's mail where you can, so messages are delivered, not forwarded to an outside provider.
- Make sure your own outgoing mail is signed with DKIM and covered by SPF. Our guide to SPF and DKIM for small sites walks through it, including how to avoid the SPF 10-lookup limit. If you use WordPress, our WordPress SMTP setup guide covers sending site mail through authenticated SMTP.
For a broader look at the account-protection side of the Microsoft ecosystem, these Microsoft 365 security practices pair well with sound forwarding settings. And for sender reputation in general, this overview of email deliverability basics is a useful next step.
Alternatives to a full catch-all
You don't always need to accept everything. Depending on your goal, one of these may fit better:
| Your goal | Option |
|---|---|
| A few role addresses (sales@, support@, billing@) | Create specific aliases that forward to one inbox |
| Handling an ex-employee's mail | Alias the old address to a current person |
| Tracking who leaks your address | Create a unique alias per service and delete it when abused |
| Moving to a new domain | Temporary catch-all for 3 to 6 months, then convert to aliases |
| Reducing spam but not missing typos | A catch-all in a dedicated mailbox with filters |
Aliases give you most of the benefit with a fixed list of addresses. A catch-all is the right call when you can't predict the addresses, which is exactly the case in migrations and small teams.
Our perspective
We run hosting for small businesses, bloggers and agencies, and the pattern we see is simple: people want email on their own domain to just work, and they don't want to lose a customer message to a typo.
A catch-all is a good answer to that, as long as it is treated as a mailbox you manage, not a switch you flip and forget. Point it at a dedicated address, filter it, and review it. When the same legitimate address shows up twice, turn it into a real alias.
The other half is the foundation. Mail only reaches a catch-all when your DNS and MX records are right, and it only lands in inboxes when SPF and DKIM are set up correctly. Our engineers in the EU and US handle migrations for free, so moving your mail along with your site doesn't mean a weekend of DNS edits. We also design our plans around daily backups and automated security, so the site and the email around it stay in good shape.
If you're setting up email for a new domain, start with the aliases you know you need, add a catch-all for the ones you can't predict, and check back in a month.
Ihor
Run your domain email with inSave Hosting
If you want your domain, site and email in one place, our shared hosting plans are built for small business sites, and our WordPress hosting adds WordPress-specific tools such as staging. We include free migration, daily backups and a 30-day money-back guarantee.

Need a domain first? You can register a domain with DNS management or transfer an existing one, then set up your catch-all with the steps above. Prefer to understand DNS before you commit? Read our guides on nameservers versus A records and DNS hosting.
FAQ
How do I set up a catch-all email?
Create a mailbox to receive the mail, confirm your MX records point at your mail service, then turn on the catch-all or default address setting. In cPanel that is Email > Default Address. In Google Workspace it is a Gmail routing rule set by an administrator. Send a test to a made-up address to confirm it works.
Will a catch-all email increase my spam?
Yes, it usually does, because it accepts mail sent to random and guessed addresses that would otherwise be rejected. You can keep it manageable by sending it to a dedicated mailbox, filtering that mailbox and reviewing it on a schedule. Create real aliases for addresses that receive legitimate mail.
Can senders tell if they typed my address wrong?
Not with a catch-all in place. The server accepts the message instead of bouncing it, so the sender gets no error. That is why the catch-all mailbox is worth checking regularly: misdirected messages land there, and you can reply or create the missing address.
How long should I keep a catch-all active?
It depends on the reason. For a migration or rebrand, many guides suggest three to six months, then turn it off once old-address traffic drops. For a small team that can't predict addresses, it can stay on permanently if you keep filtering and reviewing the mailbox.
Does forwarding catch-all mail hurt deliverability?
It can, because forwarded mail may fail SPF or DMARC checks. Keeping the catch-all mailbox on the same service as your domain's mail avoids forwarding. Signing your own mail with DKIM and publishing correct SPF and DMARC records also helps.
Sources
- Proton: What is a catch-all email address?
- cPanel: How to configure the catchall email address
- Google Workspace admin help: Get misaddressed email in a catch-all mailbox
- CatchNone: How to Set Up a Catch-All Email
- Prodou: DNS, the MX record
- Prospeo: Catch-All Emails
- SpamResource: DELIVTERMS Catch-all
- HostBible: What Is a Catch-All Email Address
- Stalwart: Addresses, aliases and catch-all
- SpamNinja: Catch All Email Address, the Risks and the Alternatives
- Microsoft Learn: Sender Rewriting Scheme in Microsoft 365
