Namecheap Free Email Forwarding to Gmail: Complete Setup Guide

Paying $6 to $18 a month per user for Google Workspace just to get contact form submissions on a fresh side project is a waste of cash. For MVPs, landing pages, or small utility tools, you can route domain-branded emails straight into your regular personal Gmail inbox for free using Namecheap BasicDNS and basic email forwarding.

I set this up on almost every new domain I register before committing real money to email infrastructure. Here is the exact setup I use to receive inbound messages and send authenticated replies from my custom domain right inside Gmail.

How Free Email Forwarding Actually Works

When someone sends an email to hello@yourdomain.com, their mail server looks up your domain’s MX records to see where to deliver the payload.

Instead of pointing those MX records to Google Workspace or Fastmail, you point them to Namecheap’s free forwarding servers. Namecheap grabs the envelope, rewrites the destination header, and hands it off to your personal @gmail.com address over SMTP.

To reply from the same domain address, you wire up Gmail’s “Send mail as” feature using a Google App Password or a free transactional SMTP relay, along with SPF records so your replies don’t get tossed into spam.

Prerequisites and Namecheap Nameserver Requirements

Namecheap’s built-in email forwarding only works if your domain uses Namecheap’s default nameservers. If you delegated your nameservers to Cloudflare, Route 53, or DigitalOcean, the forwarding UI in Namecheap will be locked out.

Double-check your nameservers before doing anything else:

1. Log in to Namecheap and head to your Domain List.
2. Click Manage next to your domain.
3. On the Domain tab, look at the Nameservers dropdown.
4. Make sure it’s set to Namecheap BasicDNS or Namecheap Web Hosting DNS.

If you just switched back from custom nameservers, give it 10 to 30 minutes for DNS propagation. If you’re hosting an app elsewhere on a subdomain, you can still point a Namecheap subdomain to a separate server while keeping your root DNS and mail forwarding intact on Namecheap.

Step 1: Configure Namecheap MX and Redirect Email Records

With BasicDNS active, enabling the forwarder takes about thirty seconds. Namecheap handles the MX records under the hood when you use their UI.

In your domain management dashboard, scroll down to Redirect Email:

1. Click Add Forwarder.
2. In the Alias field, enter the prefix you want (like contact, support, or hello). Leave out the @yourdomain.com part.
3. In the Forward to field, enter your full personal address (e.g., yourname@gmail.com).
4. Click the green checkmark to save.

You can also set the Alias to * if you want a catch-all for typos, though fair warning: catch-alls tend to attract more automated spam over time.

Right below that, verify that Mail Settings is set to Email Forwarding. Namecheap generates these MX records automatically:

Type: MX
Host: @
Value: mailfeed.registrar-servers.com
Priority: 10 Type: MX
Host: @
Value: mailfeed2.registrar-servers.com
Priority: 20

If you see eforward1.registrar-servers.com through eforward3 on older domains, don’t worry—both server pools do the exact same job.

Step 2: Set Up Outbound “Send Mail As” via Gmail

Forwarding covers inbound mail. But if a user writes to hello@yourdomain.com and you reply from yourname@gmail.com, it looks messy and confuses recipients.

You can solve this with Google’s native Send emails from a different address feature by sending through Gmail’s SMTP servers with an App Password.

Generating a Google App Password

Google won’t let you use your account login password for SMTP. You need a dedicated 16-character App Password, which requires 2FA on your Google account.

1. Open your Google Account Security settings.
2. Verify that 2-Step Verification is enabled.
3. Search for App Passwords in the top search bar.
4. Name it something recognizable (like Namecheap Mail Alias) and hit Create.
5. Copy the 16-letter password Google gives you. Strip out any spaces.

Adding the Custom Alias inside Gmail

Next, hook the alias into your Gmail web UI:

1. In desktop Gmail, click the gear icon (top right) and select See all settings.
2. Head to the Accounts and Import tab.
3. Under Send mail as, click Add another email address.
4. Enter your name and your custom alias (e.g., hello@yourdomain.com).
5. Uncheck “Treat as an alias” so replies originate cleanly. Click Next Step.
6. Configure the SMTP fields as follows:

SMTP Server: smtp.gmail.com
Port: 587
Username: yourname@gmail.com (your full personal Gmail address)
Password: [Your 16-character Google App Password]
Connection: Secured connection using TLS (recommended)

Hit Add Account. Google sends a verification code to hello@yourdomain.com. Since your Namecheap forwarder is already active from Step 1, that email drops into your inbox right away. Paste the code into the verification window, and you’re done.

Step 3: Configure SPF, DKIM, and DMARC to Stop Spam Flags

Without proper DNS authentication records, major providers (especially Gmail and Yahoo) will either dump your outbound replies straight into Spam or flat-out bounce them with 550 5.7.26 SPF errors.

Go to the Advanced DNS tab for your domain in Namecheap and add the TXT records below. For a deeper look at these protocols, check our guide on how to configure SPF, DKIM, and DMARC in Namecheap DNS.

1. The SPF Record

Your SPF record tells the world that both Google (for outbound replies) and Namecheap (for forwards) are authorized to handle email for your domain.

Add this TXT record under Advanced DNS:

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

2. The DMARC Record

DMARC tells receiving mail servers what to do if an incoming message fails SPF checks. Starting with p=none lets you monitor delivery without having valid messages randomly dropped during configuration.

Add this TXT record:

Type: TXT Record
Host: _dmarc
Value: v=DMARC1; p=none; sp=none; rua=mailto:hello@yourdomain.com
TTL: Automatic

Once you confirm everything delivers cleanly over a couple of weeks, you can tighten p=none to p=quarantine or p=reject to protect against domain spoofing.

Verifying Your Mail Routing with CLI Tools

Don’t wait for a customer to tell you an email bounced. Check your DNS records directly from your terminal using dig.

First, verify your MX records against Cloudflare’s public resolver:

dig @1.1.1.1 yourdomain.com MX +short

You should see Namecheap’s registrar servers returned with their priorities:

10 mailfeed.registrar-servers.com.
20 mailfeed2.registrar-servers.com.

Next, confirm your SPF record is live and includes both Google and Namecheap:

dig @1.1.1.1 yourdomain.com TXT +short

Your output should return the combined SPF string:

"v=spf1 include:_spf.google.com include:spf.efwd.registrar-servers.com ~all"

One critical catch: if you see more than one record starting with v=spf1, delete the extras immediately. Per RFC 7208, domains cannot have multiple SPF TXT records. Having more than one causes a PermError and sends your emails straight to junk folders.

Common Gotchas and How to Fix Them

I’ve run into a few edge cases over the years using this setup. Here is how to work around them.

Gotcha 1: Forwarded Emails Disappearing into Gmail Spam

Because Namecheap rewrites the headers when forwarding, Gmail’s automated spam filters occasionally get suspicious of incoming messages.

The fix is a simple inbound filter:

1. In Gmail, search for to:hello@yourdomain.com.
2. Click the search options icon on the right edge of the search bar.
3. Click Create filter.
4. Check Never send it to Spam.
5. Click Create filter to save.

Gotcha 2: “Send As” Shows “On Behalf Of” in Outlook Recipients

When sending through smtp.gmail.com with a custom domain alias, Outlook clients might display your sender header as yourname@gmail.com on behalf of hello@yourdomain.com.

If that unpolished look bothers you, swap smtp.gmail.com for a free transactional SMTP provider like Brevo (300 free emails/day) or SendGrid (100 free emails/day). Add their DKIM CNAME records to Namecheap, and plug their SMTP credentials into Gmail’s “Send mail as” settings instead of the Google App Password.

Gotcha 3: DNS Record Conflicts When Combining Services

If you point your root domain to an external host, make sure your A or CNAME records don’t break existing mail routing. If you run a static site on GitHub, check out our guide on how to point a Namecheap domain to GitHub Pages with apex DNS while preserving your email setup.

Namecheap Forwarding vs. Dedicated Google Workspace

Free forwarding is great, but understand the trade-offs before using it on a flagship product:

• Cost: Free forwarding is $0 beyond domain registration. Google Workspace runs $72/user/year minimum.
• Storage: Forwarding consumes your personal 15GB Google storage. Workspace gives each account dedicated storage.
• DKIM Signing: Standard Gmail SMTP uses shared signing. A paid mailbox lets you sign DKIM directly for your apex domain.
• Latency: Forwarding adds a network hop through Namecheap’s servers, which can add a 5 to 60-second delay under load. Workspace delivers instantly.

For side hustles, micro-SaaS MVPs, and personal sites, free forwarding is more than enough. You can always migrate to paid Workspace once the project makes money.

Frequently Asked Questions

How many email forwarders can I create on Namecheap?

Namecheap gives you up to 100 free email forwarding aliases per domain on BasicDNS. You can point all 100 to one Gmail address or scatter them across different inboxes.

Why does my test email sent from my own Gmail not show up?

If you send a test message from yourname@gmail.com to hello@yourdomain.com (which forwards right back to yourname@gmail.com), Gmail de-duplicates it because the Message-ID already exists in your Sent folder. Test it using an entirely separate email address.

Can I use email forwarding with Cloudflare nameservers?

No. Namecheap’s forwarding engine requires Namecheap BasicDNS. If you manage DNS in Cloudflare, use Cloudflare’s free Email Routing feature instead.

Does email forwarding support attachments?

Yes, Namecheap forwards attachments up to around 10MB to 15MB. Anything bigger might get rejected by upstream SMTP limits, so use a file-sharing link for larger transfers.

Next Steps

Once your forwarder and outbound SMTP are running, make sure your DNS security records are fully valid. Follow our walkthrough on configuring SPF, DKIM, and DMARC in Namecheap DNS to keep your domain out of spam folders for good.