Set Up Namecheap Private Email MX Records: Step-by-Step Guide

Your new Namecheap Private Email mailbox won’t receive a single message until your DNS zone points to the right mail exchangers. I hit this exact issue last week on a new project: the mailbox showed active in my dashboard, but every test email bounced immediately with 550 5.1.1 User unknown or hung indefinitely in DNS limbo.

Getting it working takes under five minutes once you know where Namecheap tucks these records away.

Check where your nameservers actually point

Before touching any mail settings, double-check which DNS provider actually controls your zone file. If your domain uses custom nameservers for a VPS or third-party host, tweaking records in Namecheap’s BasicDNS dashboard won’t do anything.

Pop open your terminal and check your NS records with dig:

dig ns yourdomain.com +short

If you see dns1.registrar-servers.com and dns2.registrar-servers.com, you’re using Namecheap BasicDNS and can manage everything directly in their dashboard. If you see nameservers for Cloudflare, DigitalOcean, or AWS, you need to plug these MX records into that provider’s panel instead.

To switch back to Namecheap’s DNS, go to your Domain List, hit Manage next to your domain, find Nameservers, and select Namecheap BasicDNS. If you need a refresher on how zone records interact, check out our guide on configuring root domains in Namecheap DNS.

Option 1: The automatic Mail Settings dropdown

Namecheap has a built-in shortcut that injects the required MX records straight into BasicDNS. If you don’t have custom routing rules, this is the quickest path.

1. Log into your Namecheap Account and head to the Domain List.
2. Click Manage next to your domain.
3. Scroll down to the Mail Settings section on the main Domain tab.
4. Flip the dropdown from No Email Service or Email Forwarding to Private Email.
5. Click the green checkmark icon to save.

Note: Selecting this preset wipes any existing MX records and injects Namecheap’s defaults. If you previously configured free email forwarding on Namecheap to Gmail, turning on Private Email disables that forwarding immediately.

Option 2: Manual MX record configuration in Advanced DNS

If the dropdown doesn’t take or you manage DNS through an external panel, add the raw MX records manually. Here are the target values for Namecheap Private Email:

• Type: MX Record
• Host: @
• Value: mail.privateemail.com
• Priority: 10
• TTL: Automatic (or 30 min / 1800)

Some subscriptions or regional clusters specify two separate endpoints. If your setup email lists two targets, use both with matching or stepped priorities:

• Record 1: Host @, Value mx1.privateemail.com, Priority 10
• Record 2: Host @, Value mx2.privateemail.com, Priority 10

To enter these manually in Namecheap, open the Advanced DNS tab, scroll down to Mail Settings, pick Custom MX, enter the values, and click Save all changes.

Double-check that you don’t have stale records lingering from Google Workspace or Microsoft 365. If you’re coming off a different provider, take a look at our walkthrough on routing custom domain email to Google Workspace to see how orphaned high-priority MX entries cause split-brain delivery.

Add SPF, DKIM, and Autoconfig records

MX records only cover inbound mail. If you skip SPF and DKIM, outbound emails sent from your new address will get flagged by spam filters almost immediately.

Go to the Host Records table under Advanced DNS and add the following entries:

1. SPF Record (TXT)

Add a TXT record on the root domain so downstream mail servers know Namecheap is authorized to send for you:

• Type: TXT Record
• Host: @
• Value: v=spf1 include:spf.privateemail.com ~all
• TTL: Automatic

If you’re also sending transactional mail from an app server, merge your includes into a single line. Never keep two separate SPF TXT records on the same root domain. For granular policy adjustments, see our guide on how to configure SPF, DKIM, and DMARC in Namecheap BasicDNS.

2. Autoconfig and Webmail Shortcuts (CNAME)

These CNAME records let clients like Thunderbird, Apple Mail, and Outlook auto-discover the right server ports, while giving you a clean subdomain for webmail:

• Type: CNAME Record | Host: mail | Value: privateemail.com.
• Type: CNAME Record | Host: autoconfig | Value: privateemail.com.
• Type: CNAME Record | Host: autodiscover | Value: privateemail.com.

Notice the trailing dot on the target values—some external DNS managers require it so they don’t append your root domain twice. In Namecheap’s native UI, you can safely enter privateemail.com without the dot.

Verify DNS propagation from the command line

Namecheap BasicDNS usually pushes updates to edge resolvers in 5 to 15 minutes, but TTL caching can slow things down. Don’t waste time sending trial emails back and forth—query the records directly.

Check your published MX records with dig:

dig mx yourdomain.com +short

You should see Namecheap’s mail cluster returned in the answer section:

10 mail.privateemail.com.

Then verify that your SPF record is visible:

dig txt yourdomain.com +short

Make sure the output contains the valid include string:

"v=spf1 include:spf.privateemail.com ~all"

Prefer a web tool? Run your domain through MXToolbox to spot open relays, reverse DNS issues, or syntax mistakes.

What I ran into and how to fix it

When I set this up, my outbound mail worked immediately, but inbound messages vanished without a bounce notice. Here is what went wrong and how I fixed it.

Duplicate MX records from previous setups

If you used cPanel mail, Titan, or Google Workspace previously on the same domain, old MX records might still be sitting in your zone. If a sending MTA hits an old entry with a lower priority number (like 0 or 5), it routes mail to a dead server instead of Namecheap.

Fix: Delete every MX record in your DNS manager except mail.privateemail.com.

The CNAME flattening collision

If you have an explicit CNAME on your apex/root host (@) pointing to GitHub Pages, Vercel, or Netlify, it can suppress MX queries per RFC 5321. Namecheap handles ALIAS flattening internally, but a raw apex CNAME will break standard resolver lookups for MX and TXT records.

Fix: Point your root apex to static IP addresses using A Records, and reserve CNAMEs for subdomains like www.

DKIM signature failures

Private Email generates unique DKIM keys in its webmail backend. If you don’t copy that selector record into BasicDNS, services like Gmail and Yahoo may reject your mail over strict DMARC alignment.

Fix: Open your Private Email dashboard, go to Settings > Email Domains > select your domain > DKIM, copy the public key string, and add it under BasicDNS as a TXT record with host default._domainkey.

Namecheap Private Email FAQ

How long does it take for Private Email MX records to start working?

If your previous record TTL was set to 30 minutes (1800s), public resolvers like Cloudflare (1.1.1.1) and Google (8.8.8.8) typically update within 15 to 30 minutes. If your old records were cached with a 24-hour TTL, it may take up to a full day for old caches to drop globally.

Can I use Namecheap Private Email and Gmail forwarding at the same time?

No. A single domain can only route incoming mail to one set of MX records. Pointing MX to Private Email directs all incoming mail there. However, you can easily set up an auto-forwarding rule inside the Private Email webmail interface to shoot a copy to your personal Gmail.

What SMTP and IMAP ports does Namecheap Private Email use?

Use these secure connection parameters when setting up desktop or mobile mail clients:

• Incoming (IMAP): mail.privateemail.com | Port 993 | SSL/TLS
• Incoming (POP3): mail.privateemail.com | Port 995 | SSL/TLS
• Outgoing (SMTP): mail.privateemail.com | Port 465 (SSL) or Port 587 (STARTTLS)
• Authentication: Full email address as the username, plus your mailbox password.

Once your MX records resolve cleanly and SPF passes validation, your mailbox is ready for daily use.