A domain registered at GoDaddy but pointed at Namecheap’s servers needs its catch-all configured in Namecheap, not GoDaddy. That single rule prevents most of the confusion people hit when they split registration and hosting across providers. The catch-all lives in the panel that owns the MX records, because that panel is where inbound mail is actually routed. Get that straight and the rest of the setup is mechanical.
Find the panel that owns inbound mail
Mail delivery follows MX records and nothing else. When someone sends a message to anything@yourdomain.com, the sending server does an MX record lookup and hands the message to whatever host the DNS says is responsible. The registrar where you bought the domain is irrelevant at that point. What matters is which company’s mail servers the MX records point to, because that company’s email hosting panel is the only place a catch-all setting will take effect.
Run a quick lookup before you touch a single toggle. From a terminal, dig MX yourdomain.com or nslookup -type=MX yourdomain.com returns the mail exchangers. If the answer is mail.yourdomain.com or a cPanel-style hostname, you are probably on shared hosting. If it is mx1.privateemail.com, you are on Namecheap Private Email. If it is aspmx.l.google.com, you are on Google Workspace. Match the answer to the panel, then configure there.
The common mismatch looks like this: a domain registered at GoDaddy, DNS delegated to Namecheap’s nameservers, and hosting on a Namecheap shared plan. GoDaddy’s dashboard still shows the domain and may even offer email settings, but those settings do nothing because GoDaddy’s servers are not in the MX chain. The catch-all has to be set where the MX records point, which in this example is Namecheap’s cPanel.
Check the MX chain before changing anything
Write down the full MX list with priorities, and note whether a third-party service such as an email security gateway sits in front of the real mailbox host. If a filtering service holds the lowest-priority MX, mail passes through it first and the catch-all belongs either at the filter or at the final destination, depending on how the filter is configured. Getting this wrong produces the maddening result where the catch-all “works” for some senders and silently drops mail from others.
Also confirm which nameservers are authoritative. A domain can have MX records sitting in a registrar’s DNS zone that nobody queries because the nameservers were changed to a hosting provider’s. The panel you edit must be the one behind the authoritative nameservers, or your changes will never be seen.
Configure the catch-all in each major panel
Once you know the mail host, the procedure differs by panel but the concept is identical: designate a mailbox that receives everything addressed to your domain that does not match a real account. In cPanel, which is used by Namecheap shared hosting and GoDaddy cPanel hosting, the feature is called Default Address, and cPanel calls the catch-all a Default Address because it is the fallback for unrouted mail. You set it under Email > Default Address, choose “Forward to email address,” and enter the destination. That destination can be a mailbox on the same server or an external address.
On Namecheap, the picture depends on the product. Private Email has its own catch-all toggle inside the admin panel under domain settings. Namecheap shared hosting exposes cPanel’s Default Address instead. Namecheap also offers catch-all via free email forwarding on domains that use its BasicDNS, which is a lighter option if you just want everything funneled to a Gmail account. catch-all email in cPanel provides further background on the subject. GoDaddy provides a catch-all toggle in its Workspace Email and Professional Email admin consoles, but only when GoDaddy hosts the mail. Google Workspace requires its own catch-all rule, configured in the admin console under Apps > Google Workspace > Gmail > Routing, using a recipient address map for the domain.
Two behaviors trip people up. First, domain-level forwarders override the Default Address, so a specific forwarder for sales@yourdomain.com wins over the catch-all and the catch-all never sees that address. Second, a catch-all set to forward to an external mailbox still passes through the origin server’s spam filter, so a filter set to discard email will drop messages before the forward fires. Check the discard threshold before blaming the catch-all.
- cPanel (Namecheap shared, GoDaddy cPanel hosting): Email > Default Address, forward to a real mailbox.
- Namecheap Private Email: domain settings, enable catch-all, pick the destination mailbox.
- Namecheap free email forwarding: set a wildcard forwarder when BasicDNS is authoritative.
- GoDaddy Professional Email or Workspace Email: catch-all toggle in the email admin console.
- Google Workspace: recipient address map in the Gmail routing settings.
One more option exists in cPanel and is best avoided unless you know exactly why you need it: piping unrouted mail to a program or a system account. A pipe to a program hands raw messages to a script, which is useful for ticketing systems and a liability for everything else. Forward to a mailbox, sort it there, and keep the server config boring.
Weigh the spam trade-off and test the result
A catch-all collects every typo, every scraped address, and every dictionary attack aimed at your domain. Spammers may cause large amounts of spam at the default address within weeks of enabling it, and the destination mailbox inherits all of it. That is the spam trade-off: you gain coverage for misspelled or unlisted addresses and you lose the implicit filtering that comes from rejecting unknown recipients. For a small business that wants to catch info@, contact@, and misspelled variants, the trade is usually worth it. For a domain with no public presence, it is mostly noise.
Testing takes two minutes. Send a message from an outside account to a random address at your domain, such as zz-test-8471@yourdomain.com, then check the destination mailbox. If it arrives, the catch-all is live. If it bounces with an SMTP rejection like “550 No Such User Here,” the setting is not applied where the MX records point, or a domain-level forwarder is intercepting it. Repeat the test after any DNS change, because propagation delays can make a correct configuration look broken.
| Panel | Where the catch-all lives | Applies when MX points to | Main trade-off |
|---|---|---|---|
| cPanel Default Address | Email > Default Address | Shared hosting servers (Namecheap, GoDaddy cPanel) | Full control, but spam volume hits the destination mailbox |
| Namecheap Private Email | Domain settings in the admin panel | mx1.privateemail.com and related hosts | Clean interface, tied to a paid mail plan |
| Namecheap free forwarding | Wildcard forwarder with BasicDNS | Namecheap forwarding servers | No mailbox storage, forwarding only |
| GoDaddy email consoles | Catch-all toggle in email admin | GoDaddy mail servers | Simple toggle, only valid if GoDaddy hosts mail |
| Google Workspace | Recipient address map in Gmail routing | aspmx.l.google.com | Powerful rules, more steps to configure |
Keep the domain-level forwarders minimal and documented. Every specific forwarder you add takes precedence over the catch-all, so a list of twenty addresses turns the catch-all into a fallback for typos only. That is often exactly what you want, but write it down so the next person who touches the account understands the routing order.
Start by running the MX lookup, then open the panel that matches the answer and set the catch-all there. If the domain is registered at GoDaddy but hosted at Namecheap, the GoDaddy dashboard is a red herring and the setting goes in Namecheap’s panel. Forward unrouted mail to a real mailbox you check daily, watch the spam volume for the first month, and turn the catch-all off if the noise outweighs the coverage. Recheck the MX records whenever you migrate hosting, because a catch-all left behind on an old panel does nothing once the records move.