How to Set Up Namecheap Private Email MX Records Step by Step

Your inbox is dead quiet because sending servers don’t know where to route your messages. Without MX records pointing to Namecheap’s mail cluster, every inbound email either disappears or bounces back to the sender with a delivery failure.

I hit this exact headache migrating a client to Private Email a few weeks ago. Test emails vanished for twenty minutes until I realized an old, forgotten default MX record from their cPanel host had higher priority and was silently eating every inbound packet. Here are the exact DNS values you need, how to apply them on Namecheap BasicDNS or external nameservers, and how to test them from your terminal.

The Exact Namecheap Private Email DNS Records You Need

Before jumping into your dashboard, get these values copied somewhere handy. Namecheap runs two redundant mail exchanger servers, both set to the exact same priority so load distributes evenly and failover works cleanly:

• Primary MX: Host: @ | Target: mx1.privateemail.com | Priority: 10 | TTL: Automatic (or 1800)
• Secondary MX: Host: @ | Target: mx2.privateemail.com | Priority: 10 | TTL: Automatic (or 1800)
• SPF TXT: Host: @ | Value: v=spf1 include:spf.privateemail.com ~all | TTL: Automatic
• Autodiscover CNAME: Host: autodiscover | Target: privateemail.com | TTL: Automatic

These values follow the standard mail routing rules laid out in RFC 5321. Keep in mind: leaving even one stray MX record pointing to an old host like Titan, Google Workspace, or your old web hosting will break delivery randomly depending on which server the sender queries.

Check Where Your DNS Actually Lives First

This is where people waste the most time. If your domain is registered on Namecheap but your nameservers point to an external host, editing records in your Namecheap panel does absolutely nothing.

Log in to Namecheap, go to your Domain List, hit Manage next to the domain, and look at the Nameservers section on the main tab:

• Namecheap BasicDNS or Web Hosting DNS: You’ll manage your MX records right inside Namecheap under the Advanced DNS tab.
• Custom DNS: If the nameservers point to Cloudflare, Hostinger, AWS Route 53, or DigitalOcean, you must add these MX and TXT records in that provider’s dashboard, not Namecheap.

If you recently switched hosts, check out our guide on how to point a Namecheap domain to Hostinger nameservers without breaking email so you don’t clobber active DNS zones.

Method 1: Automatic Setup on Namecheap BasicDNS

If your domain runs on Namecheap BasicDNS, you don’t even need to type the mail servers manually. Namecheap has a one-click preset that wipes conflicting mail records and configures everything under the hood.

1. Open your Namecheap dashboard and head to Domain List.
2. Click Manage next to your target domain.
3. Stay on the first Domain tab and scroll down to the Mail Settings section.
4. Open the dropdown (which usually defaults to No Email Service or Email Forwarding) and pick Private Email.
5. Hit Save Changes (or the green checkmark).

That automatically writes mx1.privateemail.com and mx2.privateemail.com at priority 10 to your zone. If you were previously using Namecheap’s free redirect service, see our walkthrough on how to route custom domain email to Gmail for free to see how basic forwarding compares to a standalone Private Email mailbox.

Method 2: Manual MX Record Configuration

Use manual setup if your DNS is hosted somewhere else (like Cloudflare) or if you want granular control under Namecheap’s Advanced DNS tab.

Step 1: Delete Old MX Records

Never run two email providers simultaneously on the same apex domain. If you have legacy records pointing to mail.yourdomain.com, secureserver.net, or Google, delete them right now. If an old record sits there with a lower priority like 0 or 5, sending servers will prefer it and your new inbox will stay empty.

Step 2: Add the Private Email MX Records

In your DNS editor table, create two separate MX entries:

1. Click Add New Record and choose MX Record.
2. Set Host to @ (points to your apex root domain).
3. Set Value (or Mail Server) to mx1.privateemail.com.
4. Set Priority to 10.
5. Set TTL to Automatic or 30 min (1800s).
6. Repeat the exact same steps for the second record, setting the server target to mx2.privateemail.com with priority 10.

If you’re using a DNS manager that demands a trailing dot for fully qualified domain names (like BIND or Route 53), enter mx1.privateemail.com. instead. Namecheap strips that automatically, but external providers can be picky.

Add the Required SPF, DKIM, and Autodiscover Records

MX records only tell the world where to deliver your incoming mail. If you want your outbound mail to bypass spam folders, you need an SPF record. Autodiscover makes setting up desktop and mobile apps painless.

1. The SPF Record

Create a new TXT record in your DNS settings:

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

If you already have an SPF record for services like SendGrid or Postmark, merge them into one string. You can only have one valid SPF record per domain:

v=spf1 include:spf.privateemail.com include:sendgrid.net ~all

For a full rundown on signing outbound emails properly, take a look at our step-by-step on how to configure SPF, DKIM, and DMARC in Namecheap DNS.

2. Autodiscover and SRV Records

To let apps like Outlook and Apple Mail detect your ports automatically, add this CNAME record:

• Type: CNAME Record
• Host: autodiscover
• Target: privateemail.com
• TTL: Automatic

If you’re configuring modern mobile clients that query SRV records, Namecheap recommends adding these entries under Advanced DNS:

_oxauth._tcp.yourdomain.com. SRV 0 1 443 mail.privateemail.com.
_autodiscover._tcp.yourdomain.com. SRV 0 1 443 mail.privateemail.com.

In Namecheap’s UI, map these fields out as Service (_oxauth), Protocol (_tcp), Priority (0), Weight (1), Port (443), and Target (mail.privateemail.com).

Verify DNS Propagation with Terminal Commands

Don’t just send a test email and cross your fingers. Query DNS directly to see what upstream resolvers are seeing.

Fire up your terminal and run dig against Google’s public resolver:

dig MX example.com @8.8.8.8 +short

If your changes took, you’ll see both servers returned in the answer section:

10 mx1.privateemail.com.
10 mx2.privateemail.com.

Next, make sure your SPF TXT record resolves properly:

dig TXT example.com @8.8.8.8 +short | grep privateemail

You should see "v=spf1 include:spf.privateemail.com ~all" in the output. On Windows without BIND utilities installed? Run this in PowerShell:

Resolve-DnsName -Name example.com -Type MX

You can also sanity-check the global rollout using Google Admin Toolbox Dig to ensure edge servers worldwide are serving the right records.

Debugging Email Delivery Failures and Common Gotchas

If your MX records look fine but mail still isn’t arriving, check these four common mistakes I run into regularly on client audits.

1. The Subdomain MX Trap

When adding your MX records in Namecheap, make sure Host is just @. If you accidentally paste your full domain (e.g., example.com) into the Host field, Namecheap appends it to your zone, generating an MX record for example.com.example.com. Double-check that your dashboard shows a lone @.

2. Multiple Conflicting SPF Records

A domain cannot have more than one TXT record starting with v=spf1. If you add Namecheap’s record while an old hosting SPF record is still sitting there, Gmail and Yahoo will hit a PermError and flag or drop your messages. Combine all outbound includes into a single record.

3. Cloudflare Proxy Enabled on Mail Subdomains

If your DNS is managed on Cloudflare, never proxy mail-related records. Cloudflare’s standard HTTP proxy doesn’t support raw IMAP, POP3, or SMTP traffic. If you set up an A or CNAME record for mail.yourdomain.com or autodiscover, ensure that orange cloud is switched to DNS Only (grey cloud).

4. CAA Record Blocking SSL Certificates

Namecheap Private Email provisions SSL certificates automatically on their hostnames, but if your apex domain uses tight CAA policies, check out our guide on how to configure CAA records in Namecheap DNS so your certificate rules don’t clash with external infrastructure.

Namecheap Private Email Client Connection Settings

Once your records propagate, plug these details into your desktop or mobile email client (Apple Mail, Thunderbird, Outlook):

• Incoming (IMAP): mail.privateemail.com | Port: 993 | Encryption: SSL/TLS
• Incoming (POP3): mail.privateemail.com | Port: 995 | Encryption: SSL/TLS
• Outgoing (SMTP): mail.privateemail.com | Port: 465 (or 587) | Encryption: SSL/TLS (or STARTTLS)
• Username: Your full email address (e.g., hello@example.com)
• Password: Your Private Email mailbox password

Make sure SMTP authentication is turned on and set to Password. Private Email will flat-out reject outbound relays if you skip authentication.

Frequently Asked Questions

How long does it take for Namecheap MX records to take effect?

On Namecheap BasicDNS with TTL set to Automatic, updates usually propagate within 15 to 30 minutes. But if your old MX records had a high TTL (like 86400 seconds / 24 hours), remote caching servers might keep routing mail to your old host until that cache expires.

Why am I getting emails sent from my own domain, but not from outside senders?

Internal messages stay inside Namecheap’s local routing, so they bypass public DNS entirely. Outside senders depend on your public MX records. If external mail bounces or vanishes, your public MX records are either missing, misconfigured, or pointing elsewhere.

Can I use Namecheap Private Email with hosting on another platform?

Yes. Web hosting and email hosting are completely independent. Your domain’s A record routes web traffic to your host, while your MX records point to mx1.privateemail.com and mx2.privateemail.com. As long as the DNS pointers are right, they won’t interfere with each other.

What should I do if my outbound emails land in Gmail’s spam folder?

Check your SPF record first. Then open your Namecheap Private Email webmail console, generate your domain’s DKIM keys, and publish the resulting TXT record in your DNS. Unauthenticated mail without valid SPF and DKIM signatures gets penalized fast by modern spam filters.

Next Steps for Your Mail Setup

Once your MX records resolve and your terminal checks come back clean, fire off a test message from a personal Gmail or Outlook address to verify your inbox receives it. Once inbound routing works, head over to our guide on how to configure DKIM and DMARC in Namecheap DNS to fully lock down your domain’s email security.