Catch-All Email: When to Use It (and When to Avoid It)

Catch-all email is one of Forward's most popular features. But it's also one of the most misunderstood.

Used correctly, catch-all routing is a superpower — you never miss emails, and you can create addresses on the fly. Used incorrectly, it's a spam magnet that drowns your inbox.

In this guide, we'll explain what catch-all email is, when it's useful, and when you should avoid it.

What is Catch-All Email?

A catch-all address (also called a wildcard address) accepts any email sent to your domain, even if the specific address doesn't exist.

Example:

• You own yourdomain.com
• You enable catch-all routing to you@gmail.com
• Now, anything@yourdomain.com works — hello@, support@, random123@, typos@, whatever

No need to create aliases manually. Every address automatically forwards to your inbox.

Why Catch-All Exists

Catch-all was originally designed for businesses that needed to accept email to any department or employee without pre-configuring every address.

For example:

• A client emails sales@yourstartup.com before you've set up that alias
• A typo: suport@yourdomain.com (missing a 'p') still reaches you
• You give out unique addresses for tracking: facebook-ads@, twitter-dm@, etc.

Catch-all ensures nothing gets lost.

When to Use Catch-All

1. You're a Solopreneur or Small Team

If you're the only person checking email, catch-all is a huge time-saver. You don't need to create new aliases every time someone emails a different address.

2. You Use Unique Addresses for Tracking

Catch-all is perfect for giving out unique email addresses to different services, so you can track who's sharing/selling your email.

• amazon@yourdomain.com — for Amazon account
• newsletter-techcrunch@yourdomain.com — for TechCrunch newsletter
• signup-2026-02-05@yourdomain.com — for one-off signups

If you start getting spam at amazon@yourdomain.com, you know Amazon leaked your email. Block that specific address and move on.

3. You Want Flexibility

Need to create a new email address on the spot? Just give it out. With catch-all, you don't need to log into your dashboard and create an alias first.

4. You Accept Typos Gracefully

People make typos. info@ becomes infor@. support@ becomes suport@. Catch-all means you still get the email.

When to Avoid Catch-All

1. Your Domain is Public or Well-Known

If your domain is listed anywhere online (website footer, social media, business directories), spammers will scrape it and try random addresses:

• admin@yourdomain.com
• info@yourdomain.com
• sales@yourdomain.com
• contact@yourdomain.com

With catch-all, all of these work, even if you never created them. That's a lot of spam.

2. You Care About Email Security

Catch-all increases your attack surface. If a hacker tries to phish or brute-force your domain, they can send emails to thousands of random addresses and know they'll all reach someone.

It also makes it easier for bad actors to enumerate your employees. They can send emails to common names and see which ones bounce (if catch-all is off) or succeed (if it's on).

3. You Have a Team

Catch-all doesn't make sense for teams with separate inboxes. If anything@yourdomain.com goes to one person, but sales@ should go to the sales team and support@ should go to support, catch-all will break your routing.

4. You Can't Keep Up with Spam

If your inbox is already drowning in spam, catch-all will make it worse. You'll need aggressive spam filtering, which can lead to false positives (legitimate emails marked as spam).

Pros and Cons at a Glance

Best Practices for Catch-All Email

1. Use Filters Aggressively

If you enable catch-all, set up Gmail/Outlook filters to auto-label or delete obvious spam patterns:

• Emails to admin@, postmaster@, webmaster@ → auto-delete (these are spam magnets)
• Emails to support@ → label "Support"
• Emails to your known aliases → label accordingly

2. Combine Catch-All with Specific Aliases

Use catch-all as a safety net, not the primary routing method. Create specific aliases for important addresses (hello@, support@, invoices@), and let catch-all handle everything else.

3. Monitor and Prune

Check which addresses are actually receiving email (Forward's dashboard shows this). If randomaddress@yourdomain.com is getting hammered with spam, block it specifically or disable catch-all.

4. Use a Separate Domain for Public-Facing Email

Advanced strategy: Buy two domains:

• yourstartup.com — public-facing (website, social media). No catch-all.
• yourstartup.io — private (for signups, tracking). Catch-all enabled.

This way, your private domain stays clean, and your public domain doesn't leak spam via catch-all.

5. Disable Catch-All If You're Getting Hammered

If spam gets out of control, turn off catch-all. It's not a permanent solution — it's a feature you can enable/disable based on your needs.

Catch-All Alternatives

If catch-all feels too risky, here are alternatives:

1. Wildcard Aliases (Subdomain Catch-All)

Instead of accepting anything@yourdomain.com, accept anything@tracker.yourdomain.com.

This gives you catch-all flexibility for tracking purposes without exposing your main domain to spam.

2. Plus Addressing (Gmail Trick)

If you forward to Gmail, use Gmail's + trick:

• yourname+amazon@gmail.com
• yourname+newsletter@gmail.com

All of these land in yourname@gmail.com, but you can filter by the +tag. No catch-all needed.

3. Pre-Define Common Aliases

Just create the 10-15 most common aliases manually:

• hello@, hi@, contact@, info@
• support@, help@
• sales@, inquiries@
• invoices@, billing@

This covers 95% of use cases without the spam risk of catch-all.

Real-World Example: Freelancer vs. Startup

Freelancer (Catch-All Recommended)

• Domain: janedoe.com (not public, only on business cards)
• Volume: 20-50 emails/week
• Setup: Catch-all enabled → routes to personal Gmail
• Result: Never misses emails, minimal spam

Startup (Catch-All Not Recommended)

• Domain: startupname.com (public website, listed in directories)
• Volume: 500+ emails/week
• Setup: Specific aliases (hello@, support@, sales@, team@), no catch-all
• Result: Clean inbox, minimal spam, team members get their own routes

How to Enable/Disable Catch-All in Forward

1. Log into Forward Dashboard
2. Go to Domains
3. Select your domain
4. Toggle Catch-All Routing
5. Choose the destination inbox
6. Save changes

You can enable/disable catch-all at any time. It's not permanent.

FAQ

Does catch-all affect SPF/DKIM/DMARC?

No. Email authentication is independent of catch-all. As long as your DNS records are configured correctly, catch-all won't affect deliverability.

Can I use catch-all with Gmail's "Send As" feature?

Yes! Catch-all only affects incoming email. You can still send from specific addresses using Gmail's "Send As."

Will catch-all increase my spam score?

Not directly. But if your inbox is flooded with spam (because catch-all accepts everything), your email provider might flag future emails more aggressively.

Can I block specific addresses even with catch-all enabled?

Yes! In Forward's dashboard, you can create block rules for specific addresses (e.g., block admin@yourdomain.com) even with catch-all enabled.

The Bottom Line

Catch-all email is a powerful tool, but it's not for everyone.

Use it if:

• You're a solopreneur or small team
• Your domain isn't widely published
• You want maximum flexibility

Avoid it if:

• Your domain is public-facing
• You care deeply about email security
• You have a team with role-based routing

And remember: you can always turn it on, test it, and turn it off if spam gets out of hand.