How to Set Up Free Email Forwarding on Namecheap to Gmail

Paying $6 to $18/month per user for Google Workspace or Microsoft 365 on a simple landing page or side project is a waste of money. If all you need is to catch inbound inquiries and reply from a clean address like alex@yourdomain.com, you can route everything through your personal Gmail account without spending a dime.

Here is how I set up Namecheap’s free email forwarding to bounce incoming mail to Gmail, along with Gmail’s “Send As” feature via Google App Passwords so replies come from the custom domain instead of leaking a personal email.

Prerequisites and Namecheap DNS Requirements

Namecheap’s email forwarding only works if you use their DNS. If you pointed your nameservers elsewhere (like Cloudflare, Vercel, or Route 53), Namecheap’s mail servers will never see the traffic. Your domain needs to be on Namecheap BasicDNS or Namecheap Web Hosting DNS.

If you’re hosting a frontend externally, you can keep Namecheap BasicDNS and just point your A/CNAME records. Check out our breakdown on configuring root domains in Namecheap DNS to keep your site live while Namecheap handles email routing.

Check your nameserver setup before doing anything else:

1. Log in to Namecheap and head to your Domain List.
2. Hit Manage next to your domain.
3. Look at the Nameservers dropdown on the Domain tab.
4. Make sure it’s set to Namecheap BasicDNS. If it’s on Custom DNS, switch it back and save.

Step 1: Enable Namecheap Free Email Forwarding

Once you’re on BasicDNS, set up your forwarding rule. Namecheap handles the MX records under the hood.

1. Scroll down to Redirect Email on the main Domain tab.
2. Click Add Forwarder.
3. In Alias, put the prefix you want (like contact, support, or hello). Don’t include the domain.
4. In Forward to, enter your personal Gmail address (e.g., myname@gmail.com).
5. Hit the green checkmark to save.

I usually add a catch-all alias by putting * in the Alias field. That way, if someone typos an address like billing@yourdomain.com, it still lands in my inbox.

Step 2: Verify Namecheap Mail Records in Advanced DNS

Creating the forwarder tells Namecheap to configure its mail servers, but it’s worth checking the Advanced DNS tab to ensure stale MX records aren’t colliding with them.

If you previously hooked this domain up to Workspace or another provider, delete those old records. (See our guide on how to route custom domain email to Google Workspace if you ever need to migrate to dedicated mailboxes later). Under Mail Settings, verify it says Email Forwarding.

Namecheap sets up these MX records automatically:

Type: MX Record
Host: @
Value: mailhub.namecheap.com
Priority: 10 Type: MX Record
Host: @
Value: mailhub2.namecheap.com
Priority: 20

Verify that external resolvers see these records with a quick dig query:

dig yourdomain.com MX +short

You should see mailhub.namecheap.com and mailhub2.namecheap.com. If stale records show up, wait a few minutes for TTL caches to clear.

Step 3: Generate a Google App Password for Outbound SMTP

Inbound mail works now, but hitting “Reply” in Gmail will still send from your personal @gmail.com address. To reply as contact@yourdomain.com, we’ll route outbound mail through Google’s SMTP servers using an App Password.

Google killed off “Less Secure Apps” years ago, so an App Password is required. You must have 2-Step Verification enabled on your Google account first.

1. Head to your Google Account Security Settings.
2. Under “How you sign in to Google”, make sure 2-Step Verification is active.
3. Jump straight to the Google App Passwords setup page.
4. Give it a recognizable name like Namecheap Forwarding and click Create.
5. Copy the 16-character password (ignore the spaces) and save it somewhere handy.

Step 4: Configure “Send Mail As” Inside Gmail

Now, let’s tie the custom alias into your Gmail account so you can pick it from the “From” dropdown when composing.

1. Open Gmail, click the gear icon in the top right, and hit See all settings.
2. Switch to the Accounts and Import tab.
3. Find Send mail as and click Add another email address.
4. In the popup, enter your display name and your custom address (contact@yourdomain.com).
5. Uncheck “Treat as an alias”. Leaving this checked messes with reply headers.
6. Click Next Step.

Fill in the SMTP credentials like this:

SMTP Server: smtp.gmail.com
Port: 587
Username: yourpersonalemail@gmail.com
Password: your-16-character-app-password
Secured connection using: TLS

Click Add Account. Google sends a verification code to contact@yourdomain.com. Since your Namecheap forwarder is already active, that email will pop up in your Gmail inbox in seconds. Grab the code, paste it into the prompt, and click Verify.

Step 5: Configure SPF and DMARC on Namecheap DNS

Since Gmail is sending outbound mail on behalf of your custom domain, receiving mail servers (Outlook, Apple Mail, Yahoo) will verify whether Google is authorized to do so. Without an SPF record, your replies will land straight in spam.

Go back to the Advanced DNS tab in Namecheap and add the TXT records below. For a deeper look at syntax options, check our guide on how to configure SPF, DKIM, and DMARC records in Namecheap BasicDNS.

Add an SPF record allowing both Namecheap’s mail servers and Google’s SMTP pool to send for your domain:

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

Then add a basic DMARC policy so spoofed mail gets flagged:

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

Testing Inbound and Outbound Routing

Here is a gotcha that trips people up: do not test inbound mail by emailing your custom alias from your personal Gmail account. Gmail sees the outgoing Message-ID looping back to itself, deduplicates it, and silently archives it without showing it in your inbox. It’ll look completely broken when it isn’t.

Use a separate email address (an iCloud, Outlook, or secondary work account) to run the test:

1. Send a message from your external address to contact@yourdomain.com.
2. Verify it shows up in your Gmail inbox within a few seconds.
3. Hit Reply in Gmail and verify the From dropdown is set to contact@yourdomain.com.
4. Send the reply back to your external test account.
5. Open the received email on the other end and check the raw headers to confirm SPF passed.

You can check the raw headers directly in your mail client or run a quick check to see the SPF verdict:

Received-SPF: pass (google.com: domain of contact@yourdomain.com designates 209.85.220.41 as permitted sender)

Frequently Asked Questions

Can I send attachments when using free email forwarding?

Yes. Inbound attachments flow through Namecheap straight to Gmail, while outbound attachments go through standard Gmail SMTP (supporting files up to 25 MB). Just remember Namecheap caps incoming forwarded messages at around 10 MB.

Why does my reply show “via gmail.com” to recipients?

This happens if you forgot to uncheck “Treat as an alias” or didn’t set up the SPF record properly. Modern clients hide this once your Google App Password and custom SPF TXT records are in place.

How many email aliases can I create on Namecheap?

Namecheap BasicDNS gives you up to 100 free forwarding aliases per domain. You can create support@, jobs@, and billing@, and dump them all into the same Gmail inbox or split them across different accounts.

Can I use custom DKIM keys with free Namecheap forwarding?

No. Because you’re sending through Google’s free consumer SMTP endpoint (smtp.gmail.com) instead of a paid Google Workspace tenant, Google signs outgoing messages with its own DKIM key rather than your domain’s key. If you need full DKIM alignment and a strict DMARC policy (p=reject), you’ll eventually need a dedicated email host or transactional mail service.

Next Steps

You now have a fully functional custom domain email setup without paying for another SaaS seat. If your project also needs to send transactional emails (like sign-up confirmations or password resets), don’t send those through your personal Gmail SMTP—use a proper transactional service like Postmark or Resend. If you’re building out the rest of your stack, check our guide on how to point Namecheap domains to static hosting.