Namecheap Private Email + Amazon Route 53
Set up Namecheap Private Email email on Amazon Route 53
The records Namecheap Private Email needs, written with the field names Amazon Route 53 uses (Record name, Value), in the order to add them.
- 5 steps
- 6 DNS records
- Sources checked October 21, 2026
Before you start
- Have your Namecheap Private Email account ready. Some values are unique to your account and come from the Namecheap account (Private Email).
- Open DNS at Amazon Route 53: Open the Route 53 console and select Registered domains, then your domain. Select Manage DNS, then the hosted zone for your domain. If no hosted zone exists, create one first.
- Keep both tabs open and add the records below one at a time.
Records to add
Copy each value with the button next to it. Rows marked “Copy from Namecheap account (Private Email)” are unique to your account.
| Record | Type | Record name | Value | Priority | TTL | |||||
|---|---|---|---|---|---|---|---|---|---|---|
| MX records Where incoming email goes | Type | MX | Record name | Leave empty | Value | 10 mx1.privateemail.com | Priority | in the value | TTL | Default |
| MX records Where incoming email goes | Type | MX | Record name | Leave empty | Value | 10 mx2.privateemail.com | Priority | in the value | TTL | Default |
| SPF record Which servers may send as you | Type | TXT | Record name | Leave empty | Value | "v=spf1 include:spf.privateemail.com ~all" | Priority | n/a | TTL | Default |
| DKIM A signature on every message | Type | TXT | Record name | privateemail._domainkey | Value | Copy from Namecheap account (Private Email) | Priority | n/a | TTL | Default |
| DMARC record What to do with fakes · recommended | Type | TXT | Record name | _dmarc | Value | "v=DMARC1; p=none; rua=mailto:postmaster@yourdomain.com" | Priority | n/a | TTL | Default |
| Autodiscover Automatic app setup · recommended | Type | CNAME | Record name | autodiscover | Value | privateemail.com | Priority | n/a | TTL | Default |
Step by step in Amazon Route 53
Point your MX records
MX records tell every other mail server where to deliver email for your domain. They must point to your provider and nowhere else.
- Type
- MX
- Record name
- Leave this field empty
- Value
-
10 mx1.privateemail.com
- Type
- MX
- Record name
- Leave this field empty
- Value
-
10 mx2.privateemail.com
In Amazon Route 53
- In the hosted zone, select Create record.
- Leave Record name empty, choose MX as Record type, and keep Simple routing.
- In Value, enter the priority, a space, then the mail server (for example 10 mail.example.com). Put each mail server on its own line in the same record.
- Select Create records, then delete any older MX records.
- Repeat for each MX record above.
Add the SPF record
SPF is a TXT record that lists the services allowed to send email from your domain, so receivers can spot forgeries.
- Type
- TXT
- Record name
- Leave this field empty
- Value
-
"v=spf1 include:spf.privateemail.com ~all"
In Amazon Route 53
- Select Create record.
- Enter the Record name (leave it empty for your bare domain) and choose TXT.
- In Value, enter the text inside double quotes. If you already have a TXT record on that name, add the new value as another line in the same record.
- Select Create records.
Set up DKIM
DKIM publishes a public key so receivers can confirm your messages really came from you and were not changed on the way.
- Type
- TXT
- Record name
-
privateemail._domainkey - Value
- Copy it from Namecheap account (Private Email) (see below)
Record name: Subscriptions bought on or after June 2, 2026 use privateemail._domainkey; older ones use default._domainkey.
Where to find your value
In your Namecheap account open the Private Email menu, click Manage next to your domain, then click Generate under DKIM and copy the value.
- Namecheap calls DKIM a mandatory entry for outgoing mail to work correctly.
- Paste the whole value into one field; don't split it.
- It normally takes about 60 minutes to take effect.
In Amazon Route 53
- Select Create record.
- Enter the Record name (leave it empty for your bare domain) and choose TXT.
- In Value, enter the text inside double quotes. If you already have a TXT record on that name, add the new value as another line in the same record.
- Select Create records.
Add the DMARC record (recommended)
DMARC tells receivers what to do with mail that fails SPF and DKIM, and where to send reports about it.
- Type
- TXT
- Record name
-
_dmarc - Value
-
"v=DMARC1; p=none; rua=mailto:postmaster@yourdomain.com"
In Amazon Route 53
- Select Create record.
- Enter the Record name (leave it empty for your bare domain) and choose TXT.
- In Value, enter the text inside double quotes. If you already have a TXT record on that name, add the new value as another line in the same record.
- Select Create records.
Add the Autodiscover record (recommended)
Autodiscover lets Outlook and other mail apps find your account settings without manual setup.
- Type
- CNAME
- Record name
-
autodiscover - Value
-
privateemail.com
- Optional. Namecheap also lists optional mail and autoconfig CNAMEs pointing to privateemail.com.
In Amazon Route 53
- Select Create record.
- Enter the Record name (for example autodiscover) and choose CNAME.
- Enter the target in Value.
- Select Create records.
Check your setup
Once the records are saved, run a live check. We look up your domain in public DNS and tell you what is right, missing or wrong, with the fix in Amazon Route 53’s words.
Common mistakes with Namecheap Private Email on Amazon Route 53
Using the wrong DKIM host name
Subscriptions bought before June 2, 2026 use default._domainkey; newer ones use privateemail._domainkey.
Splitting the DKIM value
Namecheap warns not to put part of the value in one field and the rest in another. Paste the full string in one field.
Adding a second SPF record
Merge Private Email into your existing SPF record instead of adding another one.
Amazon Route 53: One TXT record per name
With simple routing, Route 53 keeps all TXT values for a name in the same record, one value per line. Add SPF next to a verification value instead of creating a second TXT record.
Amazon Route 53: Split long TXT values
A single quoted string can hold up to 255 characters. Split longer values, such as DKIM keys, into quoted pieces on one line: "part one" "part two".
Rather have someone do it for you?
Tell us your domain and we will add and verify every record for Namecheap Private Email on Amazon Route 53, then send you the check results.
Namecheap Private Email on Amazon Route 53: questions
Where do I add Namecheap Private Email DNS records in Amazon Route 53?
Open the Route 53 console and select Registered domains, then your domain. Select Manage DNS, then the hosted zone for your domain. If no hosted zone exists, create one first. Add each record there, one at a time.
What goes in the Record name field at Amazon Route 53?
Leave it empty for records on your bare domain, such as MX and SPF. For the others, enter only the part before your domain, for example _dmarc. Amazon Route 53 adds your domain automatically.
Do I need to delete my existing MX records at Amazon Route 53?
Yes. Mail servers deliver to every MX record you publish, so keep only the Namecheap Private Email MX records and delete the rest.
Where do I get my Namecheap Private Email DKIM record?
In your Namecheap account open the Private Email menu, click Manage next to your domain, then click Generate under DKIM and copy the value.
Sources
Every value and step on this page comes from these official pages. Dashboards change, so if something doesn’t match what you see, tell us.
- Connect your DNS records at Amazon Web Services (AWS) to Microsoft 365 (Microsoft Learn) Checked October 21, 2026
- How to set up a DKIM record for Private Email (Namecheap Knowledgebase) Checked October 21, 2026
- Namecheap Private Email records for domains with third-party DNS (Namecheap Knowledgebase) Checked October 21, 2026
- RFC 7208: Sender Policy Framework (IETF) Checked October 21, 2026
- Supported DNS record types (Amazon Route 53 Developer Guide) Checked October 21, 2026
Namecheap Private Email on other hosts
- Namecheap Private Email on Bluehost
- Namecheap Private Email on Cloudflare
- Namecheap Private Email on DreamHost
- Namecheap Private Email on GoDaddy
- Namecheap Private Email on Hostinger
- Namecheap Private Email on IONOS
- Namecheap Private Email on Name.com
- Namecheap Private Email on Namecheap
- Namecheap Private Email on Network Solutions
- Namecheap Private Email on OVHcloud
- Namecheap Private Email on Porkbun
- Namecheap Private Email on SiteGround
- Namecheap Private Email on Squarespace Domains
- Namecheap Private Email on Wix
- Namecheap Private Email on WordPress.com
Other email providers on Amazon Route 53
- Fastmail on Amazon Route 53
- Google Workspace on Amazon Route 53
- Hostinger Email on Amazon Route 53
- iCloud+ Custom Email Domain on Amazon Route 53
- Microsoft 365 on Amazon Route 53
- Migadu on Amazon Route 53
- Proton Mail on Amazon Route 53
- Rackspace Email on Amazon Route 53
- Titan Email on Amazon Route 53
- Zoho Mail on Amazon Route 53