Paying $6 to $10 a month for Google Workspace just to receive a few messages at contact@yourdomain.com is a waste on a side project that isn’t making money yet. You don’t need a paid inbox on day one. Namecheap has free built-in email forwarding that pipes incoming mail straight into your existing personal Gmail account.
I use this exact setup whenever I spin up a new domain. Here’s how to configure Namecheap’s DNS settings, wire up the forwarding aliases, and fix the spam and MX conflicts that usually break delivery.
Prerequisites and Nameserver Requirements
Namecheap’s free email forwarding works only if your domain points directly to Namecheap’s nameservers. If you offloaded DNS management to Cloudflare, DigitalOcean, or AWS Route 53, Namecheap’s mail forwarding servers will never see the traffic.
Check your domain settings before changing anything else. Your domain must use one of these two setups:
- Namecheap BasicDNS: What you get by default on almost every fresh domain registration.
- Namecheap WebHosting DNS: Assigned automatically if you use Namecheap’s shared hosting.
If you pointed your nameservers elsewhere, you have two choices: handle your MX routing on that remote DNS host, or flip the domain back to BasicDNS and copy your web A/CNAME records back into Namecheap. If you’re splitting traffic between different hosts, see how to point Namecheap DNS to Hostinger without breaking email so you don’t nuke your site while fixing mail.
Verify Your DNS Settings in Namecheap
Log into your Namecheap dashboard, find your domain under the Domain List, and click Manage. Then jump over to the Advanced DNS tab.
Scroll down to the Mail Settings section. On a clean domain, this usually defaults to “No Email Service” or “Namecheap Web Hosting DNS”. Switch that dropdown to Email Forwarding.
Once you select Email Forwarding, Namecheap injects the required Mail Exchanger (MX) records for you:
mailstore1.secureserver.net(or Namecheap’s cluster:mx1.privateemail.com/eforward1.registrar-servers.com)eforward2.registrar-servers.comeforward3.registrar-servers.comeforward4.registrar-servers.com
They come with standard ascending priorities (10, 20, 30, 40). Namecheap handles this part automatically. Click Save Changes and wait a few seconds for the dashboard to confirm.
Add the Email Redirect in Domain Settings
Now jump back to the first tab: Domain. Scroll down past the nameservers until you see the Redirect Email card.
Click Add Forwarder to set up your inbox alias:
- Alias: Put only the prefix before the @ sign. Type
contactforcontact@yourdomain.com, orhelloforhello@yourdomain.com. Don’t paste your full domain here. - Forward to Email: Enter your destination address, like
myname@gmail.com. Check the spelling twice; a typo here fails silently and drops every incoming email into a black hole. - Click the green checkmark to save.
You can create multiple aliases routed to the exact same Gmail address. I usually set up contact@, support@, and my personal first name right out of the gate.
Setting Up a Catch-All Address
If you want any misspelled or unlisted address sent to your domain to hit your Gmail, Namecheap supports catch-all routing. Put an asterisk (*) in the Alias box and point it to your Gmail address.
Fair warning: don’t leave this on long-term. Spambots hit domains with dictionary attacks all day long. A catch-all forwarder will eventually dump hundreds of junk messages into your primary Gmail inbox every week. Explicit aliases are much cleaner.
What I Ran: Verifying MX Records in the Terminal
DNS changes take a few minutes to show up. Instead of refreshing your inbox and guessing why emails haven’t landed, check the actual records from your terminal using dig.
Run this query, swapping in your actual domain:
dig example.com MX +shortYour terminal should return Namecheap’s forwarding nodes along with their priority weights:
10 eforward1.registrar-servers.com.
10 eforward2.registrar-servers.com.
20 eforward3.registrar-servers.com.
20 eforward4.registrar-servers.com.If you see Google Workspace records, old cPanel hosts, or no answers at all, your local cache is stale or Namecheap hasn’t applied the mail setting yet. Query Cloudflare or Google’s public resolvers directly to see what the rest of the web sees:
dig @1.1.1.1 example.com MX +shortAs soon as those registrar-servers.com lines come back, inbound forwarding is ready to test.
The Gotcha: Conflicting Custom MX Records
Here is where people get stuck. If this domain had email attached to it previously—like Google Workspace, Zoho, or an old cPanel instance—custom MX records might still be sitting in your records table.
If you’re dealing with stray records, you might need to clean them out or review how to manually configure Namecheap private email MX and SRV records to figure out what shouldn’t be there. Head into Advanced DNS and scan the table. If you see custom MX records pointing to old mail hosts alongside the Email Forwarding setting, delete the custom MX rows. Having two conflicting sets of mail servers on the same domain causes mail servers to pick randomly, and most of your incoming mail will bounce.
Per the Namecheap Email Forwarding documentation, the system needs clean control over apex MX records to route inbound mail properly.
Sender Policy Framework (SPF) Adjustments
Email forwarding handles delivery fine, but Gmail’s spam filters are aggressive. When someone emails contact@yourdomain.com, Namecheap receives the email and relays it to Gmail. To Google, Namecheap is now the connecting IP.
Under Google’s current Email sender guidelines, unauthenticated forwarded mail is a fast track to the spam folder. To make sure Google accepts forwarded messages, add Namecheap’s forwarding SPF include to your DNS.
In Advanced DNS, check your TXT records. If you don’t have an SPF record yet, create one:
- Type:
TXT Record - Host:
@ - Value:
v=spf1 include:spf.efwd.registrar-servers.com ~all - TTL: Automatic
If you already have an existing SPF record for transactional mail, don’t add a second TXT record—multiple SPF records break validation completely. Merge the include string into your existing one instead. For the exact syntax, check our guide on how to configure SPF, DKIM, and DMARC records in Namecheap.
Testing Inbound Delivery from an Outside Address
Do not test your new forwarder by sending an email from the same Gmail inbox you are forwarding to. Gmail will spot the identical Message-ID in your Sent folder and swallow the incoming email to avoid a loop. It looks like the forwarder failed even though it worked fine.
Test from an unrelated third-party account:
- Open an Outlook, Proton, iCloud, or work account.
- Send a simple email to your new alias:
contact@yourdomain.com. - Give it a clear subject line like “Forwarding Test 1”.
- Hit send and check your Gmail inbox.
Most messages arrive within 15 to 30 seconds. When it shows up, click the three-dot menu on the message in Gmail and hit Show original. Check the header section:
SPF: PASS with IP 198.54.122.x
DMARC: 'PASS'If you see SPF PASS, your forwarded mail is passing Google’s incoming filters clean.
Sending Replies from Gmail (Send Mail As)
Forwarding only solves incoming mail. When someone reaches out to contact@yourdomain.com and you hit Reply, Gmail sends that response from your personal youremail@gmail.com address by default.
Gmail lets you hook up external outbound addresses using “Send mail as” under Settings > Accounts and Import. But keep this in mind: Namecheap’s free forwarding service is incoming only. It gives you zero outbound SMTP access.
If you want to reply using your custom domain for free, route outbound replies through a free transactional mail service like Brevo or SendGrid:
- Create a free account on Brevo or SendGrid and generate an SMTP API key.
- Authenticate your domain in their dashboard by adding the DKIM TXT/CNAME records into Namecheap Advanced DNS.
- In Gmail, go to Settings > See all settings > Accounts and Import.
- Under “Send mail as”, click Add another email address.
- Enter your custom domain address and uncheck “Treat as an alias”.
- Enter the transactional host’s SMTP endpoint, your username, and your API key as the password over port 587 with TLS enabled.
After you verify the confirmation code Gmail sends you, you’ll get a “From” dropdown in your compose box to toggle between your personal Gmail address and your custom domain.
Frequently Asked Questions
Why am I not receiving forwarded emails in Gmail?
First, run dig yourdomain.com MX to confirm the records actually resolve. Second, make sure you didn’t send the test email from the destination Gmail account itself. Finally, dig through your Spam and Trash tabs—Gmail occasionally dumps newly forwarded emails there until you train the filter.
Can I forward emails to multiple destination addresses?
Yes. Add another row under Namecheap’s Redirect Email section using the same alias prefix but a different destination email. An email sent to team@yourdomain.com will fan out to both recipients.
Does Namecheap free email forwarding support outbound SMTP?
No. Namecheap only handles inbound routing on free accounts. If you need native outbound SMTP without setting up third-party relay keys, you’ll need a dedicated service like Namecheap Private Email or Google Workspace.
Will changing DNS A records affect my email forwarding?
No, not as long as your nameservers and MX records stay intact. A and CNAME records handle HTTP web traffic, while MX records route mail. They operate independently. If your web host forces you to change nameservers completely, see our guide on how to keep Namecheap email working on remote nameservers.
Next Steps
Your incoming forwarding is set up and working. Once your project grows and you need real calendar sync, dedicated webmail, and full IMAP/SMTP without relying on relays, check out our guide on how to set up Namecheap Private Email MX records to upgrade cleanly.
