Free Email Forwarding in Namecheap DNS: Route to Gmail

Paying six bucks a month for Google Workspace or Microsoft 365 on a weekend project hurts. All I wanted was to catch incoming messages sent to a custom address—like contact@mydomain.com—and pipe them straight into my regular Gmail inbox without maintaining an actual mailbox.

Namecheap gives you free email forwarding out of the box if you’re on BasicDNS. It takes about five minutes to configure, but if your nameservers or MX records aren’t set up right, incoming mail drops straight into a black hole with zero bounce notifications.

The Prerequisites and Nameserver Reality Check

Before you touch the forwarding settings, check where your domain actually resolves. Namecheap’s free forwarding system only works if the domain points to Namecheap BasicDNS or Namecheap Web Hosting DNS.

If you pointed your nameservers elsewhere—like Cloudflare, Vercel, or DigitalOcean—Namecheap’s dashboard lets you add forwarders all day long, but nothing will happen. Inbound mail servers query your active nameservers, not Namecheap’s panel, and the messages bounce.

If you’ve already delegated your nameservers to a host, check our guide on how to point Namecheap domain to Hostinger nameservers without breaking email to see how DNS routing splits web traffic from MX records. Otherwise, keep your domain parked on Namecheap BasicDNS.

Step 1: Set Up Forwarding in the Namecheap Dashboard

Log in to Namecheap, go to your dashboard, and follow these steps:

1. Head to your Domain List and click Manage next to your domain.
2. Stay on the main Domain tab and scroll down until you hit Redirect Email.
3. Click Add Forwarder.
4. In the Alias box, type the prefix you want to receive mail on (like hello, support, or admin). Don’t include the @ or the domain name.
5. In the Forward to box, drop in your full personal Gmail address (e.g., mydevaccount@gmail.com).
6. Click the green checkmark to save it.

You can also turn on the catch-all address right below the table to grab typos. I usually skip catch-all until I know the primary alias is routing properly, mostly because catch-alls become spam magnets within weeks.

Step 2: Check the Automated MX Records

Adding your first alias triggers Namecheap to inject two internal MX records into your zone. These tell other mail servers on the internet to hand your domain’s messages to Namecheap’s mail hubs, which then rewrite the headers and push them over to Google.

Hop over to the Advanced DNS tab and scroll to Mail Settings. The dropdown needs to say Email Forwarding. If it switched to Custom MX or No Email Service, flip it back to Email Forwarding and save.

Behind the scenes, Namecheap writes these two records into your zone:

# Namecheap default forwarding mail exchangers
Record: MX
Host: @
Value: mailstore1.secureserver.net (or efwd.registrar-servers.com)
Priority: 10 Record: MX
Host: @
Value: efwd2.registrar-servers.com
Priority: 20
TTL: Automatic (or 30m)

If you previously had Google Workspace, Zoho, or Proton on this domain, delete those old MX records now. Leaving old entries around with competing priority numbers means incoming mail gets delivered to dead accounts or bounces randomly.

Step 3: Verify MX Propagation with Dig

DNS updates usually kick in within a couple of minutes, but depending on your old TTL, it can take longer. Instead of refreshing your inbox and guessing, verify what the world sees with dig.

Query Google’s public resolver directly:

dig +short MX yourdomain.com @8.8.8.8

If everything is hooked up correctly, you’ll see Namecheap’s forwarding relays in the answer section:

10 efwd.registrar-servers.com.
20 efwd2.registrar-servers.com.

If the response comes back blank or still lists your old mail host, your old TTL hasn’t expired yet. Wait it out before testing. If you decide down the road that you actually need a dedicated standalone mailbox, take a look at our guide on how to set up Namecheap Private Email MX records step by step.

Step 4: Add an SPF Record So Gmail Doesn’t Junk Your Mail

This is where most people get tripped up. When someone sends an email to your custom domain, Namecheap catches it and immediately re-sends it to Gmail.

Gmail inspects the inbound packet, sees Namecheap’s relay IP, but notices the sender header says something like notifications@GitHub.com. If your domain’s SPF record is missing or configured with a strict hard fail (-all), spam filters drop the message or send it straight to Junk.

Take a look at the Google Email Sender Guidelines to see what modern inboxes expect for forwarded mail. To keep things clean, add or update a TXT record for SPF in Namecheap’s Advanced DNS tab:

Type: TXT Record
Host: @
Value: v=spf1 include:spf.efwd.registrar-servers.com ~all
TTL: Automatic

The ~all (soft fail) flag is here. It signals to receiving mail servers that while mail should ideally route through Namecheap’s infrastructure, forwarded messages shouldn’t get summarily discarded. For a broader look at securing your zone, we wrote a detailed walkthrough on how to configure SPF, DKIM, and DMARC in Namecheap DNS.

Step 5: Test the Forwarding Route (Don’t Make This Mistake)

Here’s a trap I’ve fallen into: do not test this by emailing your alias from the same Gmail account that receives the forward.

Gmail recognizes when the sender and recipient are the same account. When it sees an email sent from itself, forwarded through Namecheap, and handed right back to itself, it silently drops the duplicate to save inbox space. You’ll think your setup is broken when it’s actually working.

• Grab a completely different address (a work account, Outlook, or a friend’s email).
• Fire off a plain-text email to hello@yourdomain.com with a subject like Ping test 1.
• Give it 15–30 seconds and refresh your target Gmail inbox.
• If it doesn’t show in Primary, check Spam just in case.

Once it lands, open the email, click the three dots, and hit Show original. Check the SPF, DKIM, and ARC lines. You want ARC to show pass—that confirms Google recognized Namecheap as an authorized intermediary hop rather than a spam spoof.

Sending As Your Domain from Inside Gmail (Optional)

Forwarding handles inbound mail cleanly. But eventually you’ll need to answer an email, and you probably don’t want a customer seeing your personal @gmail.com address.

Namecheap’s free forwarding does not include outbound SMTP. You can’t send mail through Namecheap’s servers without buying their Private Email plan or routing outbound mail through a transactional provider like Brevo, Mailgun, or AWS SES.

If you want to send replies using your domain alias directly inside Gmail:

1. Sign up for a free transactional SMTP provider (like Brevo or Amazon SES) and verify your domain.
2. In Gmail, open Settings > See all settings > Accounts and Import.
3. Under Send mail as, click Add another email address.
4. Enter your name and your custom alias (hello@yourdomain.com). Keep “Treat as an alias” checked.
5. Add your provider’s SMTP host, your username, and your API key as the password on port 587 (TLS).
6. Grab the verification code Gmail routes to your inbox and complete the link.

That gives you a completely free, two-way custom domain setup inside standard Gmail without paying for a Google Workspace subscription.

Gotchas and Common Failure Points

If mail stops flowing through Namecheap, it’s almost always one of these four issues:

• Cloudflare is managing DNS: If your nameservers point to Cloudflare, the Namecheap forwarding screen does nothing. Either use Cloudflare’s own free Email Routing or switch back to Namecheap BasicDNS.
• Hosting auto-installer stomped your MX: Shared hosts (cPanel, Hostinger) love overwriting MX records during initial setup. Make sure efwd.registrar-servers.com is the only MX record configured.
• Attachment size limits: Namecheap’s free forwarding caps total message size around 10MB to 15MB. Large PDFs or zip files will bounce at their relay before hitting Gmail.
• Senders with strict DMARC: If an automated sender uses a strict policy (p=reject) without ARC support, forwarding will break their signature and Gmail may drop it. Most major platforms support ARC now, but older transactional services still run into issues.

Frequently Asked Questions

Is Namecheap email forwarding really 100% free?

Yes. As long as your domain is registered through Namecheap, BasicDNS and email forwarding are included free. No renewal surprises or hidden mailbox fees.

How many email forwarding aliases can I create?

You can create up to 100 aliases per domain. That’s plenty for side projects, catch-all routing, or routing distinct addresses to different members on your team.

Can I forward emails to multiple recipients at once?

Yes. Just create multiple forwarder entries using the exact same alias prefix pointing to different email addresses. Namecheap routes a duplicate to each one.

Why does Gmail show “via registrar-servers.com” on received emails?

Gmail adds that tag whenever an email is routed through a third-party relay instead of landing straight from the sender’s origin IP. It’s standard forwarding behavior and won’t go away unless you switch to a direct mailbox.

Next Steps for Your Domain DNS

With inbound mail safely flowing to your inbox, you should lock down the rest of your domain’s zone. If you’re spinning up web apps or APIs on this domain, check our walkthrough on how to configure CAA records in Namecheap DNS to restrict SSL issuance.