GoDaddy Catch-All Forwarding Belongs at the Domain Layer

Rate this post

If you own a domain at GoDaddy and want every misspelled, guessed, or long-retired address at that domain to land somewhere useful, the fix is not a setting buried in a mailbox. It is a catch-all rule sitting at the domain layer, paired with a forwarder that sends everything to Gmail. Getting GoDaddy email forwarding right means understanding that the wildcard and the destination are two separate pieces of configuration, and that neither one lives inside a mailbox you log into.

The mechanics are simpler than the control panels suggest. A catch-all is a wildcard routing rule that matches any local part at your domain, whether or not a mailbox exists for it. That rule can only be evaluated by whatever system receives your domain’s mail first, which is determined by the MX records on the domain itself. A per-mailbox setting cannot see a message addressed to someone@yourdomain.com if no mailbox named someone was ever created, because the message never reaches a mailbox to have settings applied to it. This is why the domain-level forwarding panel is the only correct control point, and why email forwarding GoDaddy style is independent of the other GoDaddy email products you may or may not have bought.

The setup path in this guide runs in that order: confirm where your MX records point, add a forwarding destination you can verify, then layer the catch-all wildcard on top and test it with a deliberately random local part. From there the guide covers the part most walkthroughs skip, which is what happens when a catch-all plus a Gmail forwarder starts collecting dictionary spam addressed to addresses that never existed, and how to filter or redirect it before your inbox becomes unusable. It also covers the pricing question people ask most often, is GoDaddy email forwarding still free, with the caveats that matter for 2026, including forwarding credits, per-forwarder caps, and the fact that GoDaddy no longer bundles free email forwarding with domains the way it once did. If you are planning to forward GoDaddy email to Gmail for business mail rather than a side project, check the current limits before you commit, because GoDaddy email forwarding 2026 looks different from the setup described in older forum posts. The closing section diagnoses the failures that produce silence rather than error messages: unverified destinations, MX conflicts, forwarding loops, and strict DMARC policies that drop forwarded mail without telling anyone.

What Catch-All Email Forwarding Actually Does at the Domain Level

A catch-all address is a wildcard rule at the domain level: it matches every local part that has no explicit mailbox or forwarder of its own. If sales@example.com and info@example.com have their own routes, a message to q7x2@example.com still arrives because the catch-all says “anything not otherwise claimed goes here.” That “here” is usually a single inbox, often a Gmail account, so nothing sent to your domain bounces just because you never created that address.

The rule is not stored inside any one mailbox. It sits in the mail routing configuration for the domain: the MX records in DNS tell the internet which servers accept mail for example.com, and the forwarding layer on those servers decides where each local part goes. A mailbox only sees mail that was already delivered to it. It cannot see a message addressed to a local part that does not exist, so it cannot rescue that message either.

That distinction explains the entity relationship worth remembering: email forwarding is independent of other GoDaddy email products. You can run a catch-all forwarder on a domain with no Workspace Email and no Professional Email mailbox at all. GoDaddy no longer bundles free email forwarding with domains the way it once did, and Workspace Email has been retired, but forwarding remains its own product with its own control panel. Users can forward mail without owning a GoDaddy mailbox, which is exactly what makes the domain layer the right place for the wildcard.

Concretely, here is the routing path a catch-all message takes:

  1. A sender’s server looks up the MX record for your domain and connects to the server listed there, typically GoDaddy’s forwarding infrastructure.
  2. That server reads the recipient’s local part and checks for an exact match: a mailbox, an alias, a distribution group, or a named forwarder.
  3. If no exact match exists and a catch-all is enabled, the wildcard applies and the message is relayed to the configured forwarding destination.
  4. If no exact match and no catch-all exist, the server rejects the message with a 550-class error and the sender sees a bounce.

Two practical consequences follow. First, the catch-all captures a very wide net: every typo, every scraped address, every dictionary guess at your domain lands in the same destination. That is useful for recovering misdirected mail and brutal for inbox hygiene, which is why the destination and its filters matter as much as the rule. Second, a catch-all is only as reliable as the MX records pointing at it. If your domain’s MX records point somewhere else, such as a Microsoft 365 tenant, GoDaddy’s forwarding panel never sees the mail and the catch-all appears enabled while routing nothing. Microsoft 365 restricts automatic external forwarding by default, so a wildcard configured there behaves differently from one configured in GoDaddy’s Email & Office Dashboard.

Treat the catch-all as a domain-wide safety net, not a mailbox feature. It is configured once, at the layer that receives all mail for the domain, and it applies to every local part you have not explicitly assigned.

Why the Domain Layer Is the Only Place a Catch-All Can Be Configured

A message to anything@yourdomain.com gets delivered by one rule: whoever the MX record points at has to accept it. That is the entire basis for catch-all forwarding, and it explains why no mailbox setting can do the job.

Trace one message through the path. The sending server looks up the MX record for yourdomain.com and connects to the host listed there. That host decides whether the local part exists. If you run Workspace Email, Professional Email, or Microsoft 365 on the domain, the MX points to that platform’s inbound servers, and the platform checks the recipient against its list of real mailboxes and aliases. A message to sales@ when only info@ exists is rejected at that step with a 550 unknown user error, before any forwarding rule or inbox filter ever runs. Your per-mailbox settings only see mail that already passed the existence check.

GoDaddy email forwarding works differently because it changes the MX target. When forwarding is active, GoDaddy’s forwarding servers receive the mail for the domain, look up the address in the forwarder table, and relay it to the destination inbox. A catch-all entry is a wildcard row in that same table: it matches any local part with no specific forwarder of its own. Because the decision happens at the server that received the message, it can see addresses that do not exist as mailboxes, which is exactly the mail a catch-all needs to capture.

What This Means for Your Configuration

Two practical consequences follow, and both trip people up.

  • One MX target wins. A domain can point its MX records at GoDaddy’s forwarders or at a mailbox platform, but not productively at both. If you want a catch-all and also keep live mailboxes on the same domain, the mailboxes need to sit behind the same inbound system, or the catch-all has to live on a subdomain.
  • Forwarding is independent of other GoDaddy email products. You can forward mail for a domain without buying Workspace Email, Professional Email, or Microsoft 365 for it. The catch-all is a property of the domain’s routing, not of a mailbox you own.

The control point is therefore GoDaddy’s Email & Office Dashboard, under the domain’s email forwarding panel, where the forwarder table and the MX records live together. That panel is the only place where a rule can match on “any local part” rather than on a specific address. Look for the wildcard or catch-all option when adding a forwarder, and check that the MX records still list GoDaddy’s forwarding hosts after you save. If the MX records were changed for a mailbox migration and never pointed back, the catch-all row can look active in the panel while every message is being rejected upstream. Verify the routing path first, then trust the rule.

Setting Up GoDaddy Email Forwarding for a Domain

Everything in this section happens in the GoDaddy Email & Office Dashboard, not inside a mailbox. Sign in to your GoDaddy account, open the account menu, and choose Email & Office. The dashboard lists every domain in the account; pick the one you want to route. If the domain has no paid mail plan attached, the dashboard still shows an Email Forwarding card, because forwarding is independent of other GoDaddy email products. Click Manage next to it.

If the card is missing, first confirm the domain is registered in this account and that its nameservers still point to GoDaddy. A domain moved to third-party DNS will not expose the forwarding panel until the DNS records are handled on the other side.

The forwarder form asks for two things: a source local part and a destination address. Start with one specific forwarder before you add anything wildcard-shaped, for example hello@yourdomain.com pointing to yourname@gmail.com. Type the destination carefully. This address is where every message will land, and a typo is the most common reason a forwarder looks broken when it is actually routing into the void.

Save the forwarder, then verify the destination. GoDaddy sends a confirmation email to the destination inbox with an approval link, and the forwarder stays inactive until someone clicks it. If the link does not arrive, check the spam folder, then re-send the verification from the dashboard. Gmail sometimes files these under Promotions, so search for “GoDaddy” rather than scrolling.

Next, confirm the mail actually reaches GoDaddy’s forwarding servers. Open the domain’s DNS settings and look at the MX records. For GoDaddy forwarding, the expected record is mx1.secureserver.net with priority 0, and in some configurations a second record at mx2.secureserver.net. If the domain also has an MX record pointing to Microsoft 365, Google Workspace, or a Titan-powered Professional Email plan, mail will be delivered there instead and the forwarder will never see it. Catch-all forwarding and a live mailbox on the same domain require a deliberate choice about which system owns the MX.

Allow up to an hour for DNS propagation, though GoDaddy’s own records usually resolve faster. Then send a test message from an outside account, not from the same domain, to the forwarder address. Delivery to the Gmail destination confirms three things at once: the MX record is right, the destination is verified, and the forwarder is live. Keep that test message; it is useful evidence if you later need to open a support ticket.

Setting Where to find it What “correct” looks like
Forwarder Email & Office Dashboard, Email Forwarding Source local part plus a verified destination
Destination status Dashboard forwarder list Marked verified, not pending
MX record Domain DNS settings mx1.secureserver.net, priority 0
Nameservers Domain settings GoDaddy nameservers, unless DNS is managed elsewhere

One practical note: the dashboard changes labels and layout regularly, and GoDaddy updates its help pages frequently. If a menu item named in a tutorial from last year is gone, look for the same function under a different heading rather than assuming the feature was removed.

Adding the Catch-All Rule and Forwarding GoDaddy Email to Gmail

Pair a named forwarder with the wildcard

The cleanest setup is two forwarders on the same domain: one for your main address, one for everything else. Start with the named forwarder, for example you@yourdomain.com to yourname@gmail.com. That entry gives you a predictable path for real mail and a known-good destination you can test first. Once it works, add the wildcard.

In GoDaddy’s email forwarding panel, the catch-all is a separate entry whose local part is the asterisk (*) or a blank username, depending on which interface version your account lands on. Point it at the same Gmail address, or at a second Gmail address you keep for low-trust mail. Some accounts only allow one catch-all per domain, so decide the destination before you save. The wildcard does not override the named forwarder: mail to you@ follows its own rule, and the asterisk only catches local parts that have no forwarder and no mailbox.

If your domain runs GoDaddy Professional Email (powered by Titan) or Microsoft 365 mailboxes, check the order of operations. A catch-all forwarder applies to addresses that do not exist as mailboxes. Add a mailbox called info@ later and mail to it stops hitting the wildcard and starts landing in that mailbox. Keep a short list of addresses you may want as real mailboxes so you do not break a forwarder by accident.

Verify the Gmail destination and test a random local part

GoDaddy sends a verification message to the destination address the first time you save a forwarder. Open Gmail, find the message from GoDaddy, and click the confirmation link. Forwarding stays inactive until you do, and the panel usually shows a pending or unverified state next to the entry. Check the spam folder in Gmail if the link does not arrive within a few minutes, and confirm you typed the address with no trailing space.

Then test the wildcard with an address that could not possibly exist:

  1. From an outside account (not one on your domain), send a short message to something like q7x2-test@yourdomain.com.
  2. Wait up to five minutes. Forwarding is near-instant but greylisting and DNS caching can add delay.
  3. Confirm the message arrives in Gmail and that the original sender address is preserved in the headers.
  4. Send a second test to your named forwarder to prove both rules work side by side.

Use an external sender for the test. Mail sent from one address on your own domain can behave differently because of internal routing and loop protection, which makes a failed test look like a broken catch-all when the rule is fine. If the random local part bounces with a “user unknown” reply, the wildcard was not saved or is still pending verification. If it vanishes with no bounce, move on to the MX and DMARC checks in the troubleshooting section.

Catch-All Plus a Gmail Forwarder Also Captures Spam Addressed to Random Local Parts

A catch-all rule is indiscriminate by design. The moment you turn it on, every message addressed to a local part that does not exist at your domain becomes a match: sales@, info@, office@, admin@, and everything else in a spammer’s dictionary list. If your wildcard points at the same Gmail address you use for real conversations, that traffic lands in the same inbox as your actual mail.

Expect the volume to be noticeable within days. Dictionary attacks cycle through common prefixes on thousands of domains per hour, and scraped addresses from old leaks get replayed for years. Because GoDaddy’s forwarder accepts the message at the domain layer and relays it onward, Gmail receives it as ordinary inbound mail. Gmail’s own spam filter catches most of it, but not all, and the false-negative rate climbs when the spam is plain text with no links.

Keeping the Destination Inbox Usable

Three approaches work, and you can combine them.

  • Filter at Gmail, not at GoDaddy. Create a filter matching to:(yourdomain.com) and route it to a label, skipping the inbox. Then add exceptions for the specific addresses you actually read. This keeps the catch-all useful as an archive without burying real mail.
  • Use a dedicated destination. Point the wildcard at a separate Gmail address, for example yourdomain.catchall@gmail.com, and keep your primary forwarder, such as hello@yourdomain.com, going to your main inbox. The two rules coexist: the specific forwarder wins for that exact address, and the wildcard handles everything else. Nowhere in GoDaddy’s panel does this require a second product; each forwarder is just a row with a source and a destination.
  • Allowlist the local parts you care about. Before enabling the wildcard, list the addresses that must never be filtered away: your own name, billing, support, and any address printed on invoices or contracts. Check those labels weekly for the first month.

One trade-off worth naming: a catch-all makes typo mail recoverable. If a customer writes to jon@ instead of john@, you see it. That is the entire reason people run catch-alls. The cost is that you now own the filtering problem, because the domain layer has no concept of “likely legitimate.” It matches on the address pattern and nothing else.

Watch for a second-order effect too. Some senders treat a non-bounce as confirmation that an address is live, so a catch-all that silently accepts everything can increase the volume of repeated spam over time. If the noise becomes unmanageable, the cleanest fix is to narrow the rule: disable the wildcard and add explicit forwarders for the handful of aliases you actually publish. GoDaddy’s forwarding configuration is independent of any mailbox product, so you can change it without touching email plans, DNS records beyond MX, or anything else on the domain.

Is GoDaddy Email Forwarding Still Free, and What the 2026 Setup Looks Like

GoDaddy no longer bundles free email forwarding with domains. The old Workspace Email product, which many domain owners used as a forwarding base, was retired, and the free forwarding that came attached to a domain purchase went with it. What remains is a forwarding system that runs on forwarding credits, and those credits have to exist on the account before any forwarder, catch-all included, will activate.

That single change is the reason so many 2026 how-to posts are wrong. A reader follows a 2018 tutorial, opens the domain settings, adds a destination, and nothing happens because there is no credit behind the rule. Before you plan a catch-all, log into the account and check what forwarding entitlements are actually present.

What to check before you rely on GoDaddy forwarding for business mail

  • Forwarding credits on the account. Email Forwarding requires existing forwarding credits. A newly purchased domain typically does not include them, so a forwarder created without credits stays inactive even though the panel accepts the entry.
  • Per-forwarder caps. Each forwarder is a single destination. If you need the catch-all landing in three inboxes, that is three forwarders, not one, and each consumes its own credit and its own quota.
  • Volume and rate limits. Forwarding is not a mailbox. There is no storage to absorb a burst, so a dictionary attack against your catch-all can push volume past whatever the current per-day threshold is and messages get dropped rather than queued.
  • Whether you actually need a mailbox. Professional Email is powered by Titan, and the Pro Plus, Premium and Ultra plans offer external forwarding. Microsoft 365 restricts automatic external forwarding by default, so if you move to that stack the catch-all pattern needs an admin-level change or a transport rule.

Email Forwarding is independent of the other GoDaddy email products. You can forward mail without a GoDaddy email product at all, which is useful if your real inbox is Gmail and you only want the domain to route. The catch is that independence cuts both ways: nothing about a Professional Email subscription automatically enables forwarding, and nothing about a forwarder gives you a mailbox to inspect when something goes missing.

Pricing moves. GoDaddy updates its help pages frequently, and the forwarding credit model has been adjusted more than once since Workspace Email was retired. Treat any figure you read, including the ones in this article, as a starting point and confirm it in the Email & Office Dashboard for your own account before you commit a business domain to it. The dashboard is the authoritative view of what your plan includes.

One practical rule for 2026: if inbound mail to your domain has revenue attached to it, do not put the catch-all on the free path alone. Run the wildcard, but keep a paid mailbox on the same domain as a fallback address and check it weekly. Forwarding is a routing convenience, not a delivery guarantee, and the difference only shows up when a message that mattered quietly fails to arrive.

Troubleshooting Common GoDaddy Forwarding and Catch-All Failures

Most forwarding problems come down to five causes: an unverified destination, MX records pointing somewhere else, a loop, a DMARC policy eating the mail, or a catch-all that was never really active. Work through them in that order and you will usually find the fault within a few minutes.

1. The destination was never verified. GoDaddy sends a confirmation email to every new forwarding address, and nothing routes until someone clicks the link. If you added a forwarder to Gmail and skipped the message (it often lands in Spam), the rule shows as pending and mail is dropped. Open the Email & Office Dashboard, check the forwarder status, and resend the verification. Also confirm the Gmail address is spelled exactly right, since a typo creates a forwarder that verifies fine but sends mail to a stranger.

2. MX records point away from the forwarding service. A catch-all only works if the domain’s MX records deliver mail to the servers that hold the forwarding rules. If you moved the domain to Microsoft 365, Google Workspace, or a host with its own mail, the MX records follow, and GoDaddy’s forwarders become decorative. Run an MX lookup for the domain and compare the result with what GoDaddy’s help pages currently list. If the domain uses a third-party DNS provider, the records must be edited there, not in the GoDaddy panel. When both GoDaddy forwarding and another mail service claim the same domain, pick one and remove the other’s records.

3. You built a loop. Forwarding sales@yourdomain.com to a Gmail account that auto-forwards back to sales@yourdomain.com, or a catch-all that forwards to an address which is itself a forwarder on the same domain, creates a cycle. Mail bounces after a few hops, or worse, the two servers keep passing the same message until one gives up. Check the destination inbox for any forwarding rule that points back at your domain, and keep the catch-all destination different from the specific forwarder’s destination.

4. DMARC is silently discarding the forwarded copy. This is the failure that wastes the most time because nothing bounces. When a sender publishes a strict DMARC policy (p=reject) and the forwarder rewrites nothing, the receiving provider sees a failed alignment check and rejects the message. Gmail and Outlook filter a lot of this quietly. Test with a message from a domain that publishes p=reject, such as most banks and large retailers, and check the destination’s Spam folder and the forwarder’s delivery log. There is no setting on your side that fixes a strict sender policy; the workaround is forwarding to a destination you control that accepts the mail, or asking the sender’s domain to relax its policy, which they will not do.

5. The catch-all looks on but routes nothing. A wildcard rule can appear active while every message to a random local part disappears. Common causes: the rule was saved under a different domain in the same account, the destination address is unverified, or the mailbox was created later and now shadows the wildcard for that local part. Send a test to a local part you know does not exist, such as zz-test-8842@yourdomain.com, then check the destination inbox, the Spam folder, and the forwarder’s activity log. If the test vanishes and the MX records are correct, delete the rule and recreate it. GoDaddy updates its help pages frequently, so confirm the current panel layout and limits before assuming the interface has changed under you.

Before you walk away from the setup, do one last pass in the GoDaddy Email & Office Dashboard. Confirm the catch-all rule and your Gmail forwarder both show as active, check that the destination address is verified (re-send the confirmation if it is not), and look at the MX records for the domain to make sure they still point to GoDaddy’s forwarding servers and not to a leftover Workspace Email or Microsoft 365 configuration. If you moved the domain to GoDaddy recently, MX changes can take up to 24 to 48 hours to propagate, so a test message sent right after setup may bounce even when everything is correct. Also confirm you have forwarding credits left, since Email Forwarding requires existing forwarding credits and GoDaddy no longer bundles free email forwarding with new domain purchases the way it once did. Send a test to a random local part like q7test-8471@yourdomain.com and a second test to a normal address such as info@yourdomain.com. Both should land in Gmail within a few minutes; if only one arrives, the specific forwarder is fine and the wildcard rule is the problem.

Then decide what happens to the noise. Set a Gmail filter on to:(yourdomain.com) that skips the inbox and applies a label, and add a second filter for known senders you actually want to see so they stay visible. If the catch-all is pulling in more dictionary spam than you can filter, point it at a separate Gmail address or a dedicated mailbox instead of your primary one, and keep only the named forwarders aimed at your main inbox. Recheck the setup once a quarter: GoDaddy updates its help pages frequently, forwarding limits and plan behavior change, and a rule that worked in January can quietly stop routing by summer. The catch-all is a routing rule at the domain layer, so it keeps working independently of which GoDaddy email product you use, or whether you use one at all. Keep the MX records and the verified destination in a note somewhere you will find them, and the next time a client says mail to a made-up address bounced, you will know exactly where to look.