Route Custom Domain Email to Gmail for Free with Namecheap

Paying $7 a month for a Google Workspace seat just to catch contact form pings on a side project is a waste of money. You can wire your custom domain straight into your personal Gmail inbox for $0 using Namecheap’s built-in forwarding and a free SMTP relay.

I set this up last week for two client sites. Here’s the exact setup: Namecheap forwards inbound mail, we configure SPF and DMARC so messages don’t vanish into spam, and we hook up Gmail’s “Send mail as” feature using an external relay so you can reply from your domain without paying Google a dime.

The Architecture: Inbound vs Outbound Routing

Email delivery is two completely different beasts: inbound (getting mail) and outbound (sending mail). Confuse them and your setup breaks.

Inbound is simple. Namecheap handles MX records on their edge servers. When an email hits hello@yourdomain.com, Namecheap catches the envelope and immediately hands it off to your @gmail.com address. They don’t store messages on disk, so you don’t have to worry about mailbox storage limits.

Outbound is where people get stuck. Google killed unauthenticated sending years ago. You can’t just tell Gmail to spoof hello@yourdomain.com through Google’s default servers anymore—external mail servers will reject the message or drop it straight into spam.

The fix? Pair Namecheap’s free inbound forwarding with a free transactional SMTP relay like Brevo or SMTP2GO (both give you hundreds of free outbound emails a day), then plug those credentials right into Gmail’s web settings.

Prerequisites: What You Need Before Touching DNS

Before editing any zone files, have these ready in separate tabs:

• A domain registered with or pointed to Namecheap BasicDNS or Namecheap Web Hosting DNS.
• Your personal @gmail.com inbox.
• A free account on a transactional SMTP service (Brevo, SMTP2GO, or SendGrid) for sending authenticated mail.
• A terminal or a web-based DNS lookup tool to verify records.

If your domain points to third-party nameservers like Cloudflare or Hostinger, you’ll need to add these records over there instead. If you’re keeping existing hosting records intact, check our guide on pointing Namecheap DNS to web hosting without breaking email.

Step 1: Enable Free Email Forwarding in Namecheap

Head to your Namecheap dashboard, jump to Domain List, and hit Manage next to your domain. Stay on the Domain tab and scroll down to Mail Settings.

By default, it’s usually set to “No Email Service” or “Namecheap Private Email”. Switch that dropdown to Email Forwarding and save it.

Scroll down to the Redirect Email section. This is where you map aliases to your real Gmail address:

1. Click Add Forwarder.
2. In Alias, type what goes before the @ (like hello, support, or your first name). Leave off the domain part.
3. In Forward to, enter your actual personal address: yourname@gmail.com.
4. Hit the green checkmark.

You can set up a catch-all with * as the alias, but I’d skip that. Within two weeks, automated scrapers will find it and start dumping junk straight into your personal Gmail inbox.

Step 2: Add MX and SPF Records to Stop Forwarding Bounces

Selecting “Email Forwarding” usually provisions the default MX records automatically. But if this domain previously had Google Workspace, Zoho, or private mail attached, the old records often stick around. Jump over to the Advanced DNS tab to verify what’s actually there.

You need two MX records pointing at Namecheap’s mail servers with these exact priorities:

; Namecheap Free Email Forwarding MX Records
Type: MX Record
Host: @
Value: mx1.registrar-servers.com.
Priority: 10
TTL: Automatic Type: MX Record
Host: @
Value: mx2.registrar-servers.com.
Priority: 10
TTL: Automatic

Now add your SPF record. Forwarded mail often trips SPF checks because Namecheap receives the email and relays it to Gmail. If Gmail evaluates the sender against Namecheap’s relay IP without alignment, it’ll trigger a softfail or hardfail.

Namecheap provides an include tag for their forwarding infrastructure. Drop this TXT record into your Advanced DNS zone:

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

If you’re using an outbound relay like Brevo, merge its include tag into this exact same record. Never create two separate SPF TXT records on one root domain—validators will invalidate both. Here’s what the combined SPF looks like with Brevo:

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

If you need a deeper dive into SPF mechanics, read our guide to configure SPF, DKIM, and DMARC in Namecheap DNS.

Step 3: Test Inbound Email Delivery with Dig

DNS propagation takes anywhere from two minutes to an hour depending on your previous TTLs. Before spamming test emails, verify the records with dig from your terminal.

Here’s what I ran to check the live MX routing:

dig +short MX yourdomain.com

You should see Namecheap’s forwarding servers in the answer section:

10 mx1.registrar-servers.com.
10 mx2.registrar-servers.com.

Next, pull the TXT record to make sure your SPF string is resolving publicly:

dig +short TXT yourdomain.com

Once both resolve, send a test email from a third account (like a work address, iCloud, or secondary Gmail) to hello@yourdomain.com. In my test run, the forwarded message hit my inbox in about 1.2 seconds.

Open that message in Gmail, click the three-dot menu in the upper right, and select Show original. Make sure SPF shows PASS and there are no transport delivery warnings.

Step 4: Configure Gmail “Send Mail As” for Outbound Replies

Inbound works. But if you hit “Reply” right now, your personal @gmail.com address leaks out. We need Gmail to send replies directly from hello@yourdomain.com.

Since Google won’t let you relay through their servers for free, we hook in a free outbound SMTP host. I’m using Brevo here because their free tier allows 300 emails a day with no credit card required.

1. Sign up for Brevo, head to Senders & IP > Domains, and add yourdomain.com. Add the DKIM TXT records they generate into Namecheap’s Advanced DNS tab.
2. Go to Transactional > Settings > Configuration in Brevo to grab your SMTP credentials (server: smtp-relay.brevo.com, port: 587, your login, and the generated master key password).

Now jump back into Gmail:

1. Click the Gear icon > See all settings.
2. Select 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 domain address (hello@yourdomain.com).
5. Uncheck “Treat as an alias”. Leaving this checked creates messy thread nesting when replying to external clients.
6. Click Next Step.

Plug in the SMTP details from Brevo:

SMTP Server: smtp-relay.brevo.com
Port: 587
Username: your-brevo-login-email@example.com
Password: your-generated-smtp-master-key
Connection: Secured connection using TLS (recommended)

Click Add Account. Gmail will test the connection and fire a verification code to hello@yourdomain.com. Because your Namecheap forwarder is already running, that verification email drops into your Gmail inbox seconds later.

Grab the code, paste it into the prompt, and confirm.

One last setting: under Send mail as in Gmail, tick the radio button for “Reply from the same address the message was sent to”. That way, any email sent to your custom address gets answered from your custom address automatically.

Step 5: Enforce DMARC to Keep Your Mail Out of Spam

Google and Yahoo both enforce strict authentication rules now. If your domain sends outbound mail without at least a barebones DMARC policy, expect your emails to get quarantined or binned straight into spam. Check the Google Email Sender Guidelines if you want the official breakdown.

To keep things compliant without paying for monitoring SaaS tools, add this TXT record under Namecheap’s Advanced DNS tab:

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

Here’s what each part actually does:

• v=DMARC1: Tells the receiving server this is a DMARC policy.
• p=none: Monitoring mode. It tells Gmail not to reject messages if something weird happens with an SPF/DKIM check while you’re still tweaking DNS.
• rua=mailto:...: Where servers send daily XML delivery summaries.
• aspf=r: Sets SPF alignment to relaxed mode so subdomains and root domains don’t fail unnecessarily.

Once you’ve confirmed your outbound emails consistently pass DKIM through the relay, you can eventually bump p=none to p=quarantine or p=reject to protect your domain from spoofing.

Gotcha: Fixing the “550 SPF Check Failed” Forwarding Bug

When I set this up on an older domain, I ran into a nasty issue: automated notifications from Stripe and GitHub were bouncing back to senders with a 550 5.7.23 SPF validation failed error.

The problem is strict senders publish SPF records with -all (hard fail) alongside a strict DMARC p=reject policy. When Namecheap forwards these, it passes the raw envelope. Gmail sees the email coming from Namecheap’s IP, but Namecheap’s IP isn’t in Stripe’s SPF record. Result: hard bounce.

Namecheap handles this via SRS (Sender Rewriting Scheme), which rewrites the return path to something like SRS0=xxxx=xx=stripe.com=user@registrar-servers.com. But on my domain, SRS wasn’t triggering because I had a stale MX record from a previous cPanel setup lingering in Advanced DNS.

If you’re hitting bounces from strict senders, clean out your Advanced DNS tab. Delete every single MX record that doesn’t point to registrar-servers.com so all incoming traffic flows through Namecheap’s SRS gateway.

If you decide down the road that forwarding isn’t enough and you want real IMAP boxes, read our guide on how to set up Namecheap Private Email MX records without breaking existing DNS.

Testing Outbound Delivery with Mail-Tester

Don’t assume everything works just because a test email reached your personal inbox. You need to verify that your relay’s DKIM signature, SPF alignment, and reverse DNS pass third-party spam filters.

1. Head over to Mail-Tester and grab the temporary email address it gives you.
2. In Gmail, hit Compose, change your From dropdown to your custom domain address (hello@yourdomain.com).
3. Send a normal email with a realistic subject and body. Don’t just type “test test”, or the filter will penalize you for low-quality content.
4. Click Check your score on Mail-Tester.

You should see a 9/10 or 10/10. Check the report details: SPF should show your relay include passing, DKIM should show a valid signature for your custom domain, and DMARC should report clean policy discovery.

If you’re managing custom mail servers and need to generate keys by hand, see our walkthrough on configuring Namecheap email MX, SPF, and DKIM records manually.

Frequently Asked Questions

Can I reply directly from my iPhone or Android Gmail app?

Yes. Once you add and verify the external address under Accounts and Import in Gmail on desktop, the official Gmail mobile apps sync it automatically. Just tap the From field when composing a reply on your phone and select your custom domain.

Does Namecheap Free Email Forwarding support file attachments?

Yes, standard attachments forward fine. But Namecheap caps incoming forwarded messages at around 10MB to 15MB. If someone tries to email you a 25MB PDF, Namecheap drops it with a 552 Message size exceeds fixed maximum message size error. If you regularly handle big files over email, you’ll need an actual paid mailbox.

Why does my recipient see “via smtp-relay.brevo.com” next to my name?

That means your domain is missing a verified DKIM record that matches your sender domain. When DKIM isn’t signed properly, Gmail warns recipients about the actual relay server. Add the DKIM TXT keys from Brevo into Namecheap DNS, wait for them to propagate, and the “via” notice disappears.

Can I route multiple aliases to different Gmail accounts?

Yes. Namecheap supports up to 100 forwarders per domain. You can send billing@yourdomain.com to your inbox and point support@yourdomain.com to a co-founder’s Gmail address without paying extra.

Next Steps: Lock Down Your DNS Records

Once your custom domain is handling inbound and outbound mail cleanly inside Gmail, make sure you don’t break your DNS during future site migrations. If you host web apps on this same root domain, check out our guide on registering custom nameservers with glue records on Namecheap to keep your records stable under one setup.