How to Set Up Namecheap DNS Records for Email Marketing

In Namecheap, email marketing records live in two places: the Host Records table for authentication and tracking, and the Mail Settings section for mail routing. Namecheap enforces strict rules on hostnames and quotation marks, which can cause verification errors if you paste values directly from your provider.

Namecheap mail settings: select Custom MX

Namecheap separates general DNS records from email routing. On the Advanced DNS tab, you will find a dedicated Mail Settings section below the Host Records table.

Check the current selection under Mail Settings before making changes. If your domain routes email through third-party servers such as Google Workspace, Microsoft 365, or another mail service, select Custom MX and enter the records from that provider.

To route mail to external servers:

1. Scroll down to the Mail Settings section on the Advanced DNS page.
2. Click the dropdown menu and select Custom MX.
3. Enter your mail server hostnames and priority numbers in this section.

These settings apply when your domain uses Namecheap BasicDNS, PremiumDNS, or FreeDNS. If your domain uses Namecheap Web Hosting DNS, add records in cPanel. If it points to external nameservers, manage your records in that external dashboard.

Namecheap documents the supported nameserver options in its guides for email authentication records and custom MX records.

Adding a record in Namecheap

1. Log in to your Namecheap account and click Domain List in the left sidebar.
2. Locate your domain and click Manage.
3. Select the Advanced DNS tab at the top of the page.
4. In the Host Records section, click Add New Record.
5. Select the record type (TXT Record or CNAME Record).
6. Enter the Host value:
   • For root domain records (such as SPF), enter @.
   • For subdomains (such as _dmarc or a DKIM selector), enter only the subdomain prefix. Namecheap automatically appends your root domain.
7. Enter the Value provided by your email service. Do not wrap the value in quotation marks.
8. Leave the TTL at Automatic (30 minutes) unless your provider gives you a different value.
9. Click the green checkmark icon on the right side of the row to save the record.

Required authentication records

Receiving mail servers use these three records to verify that messages sent from your domain are authentic.

1. SPF (Sender Policy Framework)

• Type: TXT Record
• Host: @ (Namecheap applies this to your apex domain)
• Value: The SPF string provided by your email service, such as:

  v=spf1 include:_spf.google.com include:sendgrid.net ~all

• TTL: Automatic

Merging multiple SPF records

A domain can only have one SPF record. If you already have an SPF record for Google Workspace, Microsoft 365, or another service, do not create a second TXT record starting with v=spf1. Multiple SPF records cause receiving servers to return a PermError, which routes messages to spam or rejects them.

Edit your existing SPF record and insert the new provider’s include: mechanism before the ~all or -all qualifier at the end.

Do not add quotation marks around the SPF string in the Value field. Namecheap stores the value literally, and quotes will break the SPF syntax.

2. DKIM (DomainKeys Identified Mail)

Email platforms provide DKIM in one of two formats:

CNAME-based DKIM

Most modern email platforms (including Klaviyo, Postmark, SendGrid, and Amazon SES) use CNAME records:

• Type: CNAME Record
• Host: The selector prefix without your root domain, such as s1._domainkey or k1._domainkey
• Value: The target hostname provided by your email platform, such as s1.domainkey.example-esp.com.
• TTL: Automatic

If your email service provides a full hostname like s1._domainkey.yourdomain.com, enter only s1._domainkey in the Host field. Entering the full domain causes Namecheap to publish s1._domainkey.yourdomain.com.yourdomain.com, which breaks verification.

TXT-based DKIM

Some platforms (such as Google Workspace or older mail servers) provide a raw public key string:

• Type: TXT Record
• Host: The selector prefix, such as google._domainkey
• Value: The raw public key string starting with v=DKIM1; k=rsa; p=...
• TTL: Automatic

Paste the public key without enclosing quotation marks. Namecheap accepts full 2048-bit keys in the Value field.

3. DMARC (Domain-based Message Authentication, Reporting, and Conformance)

• Type: TXT Record
• Host: _dmarc (enter only _dmarc; Namecheap appends your domain)
• Value:

  v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com; pct=100;

• TTL: Automatic

Start with p=none. This keeps DMARC in monitoring mode so you can collect reports without risking delivery issues. Once SPF and DKIM pass across all sending services, update the policy tag to p=quarantine or p=reject.

Optional deliverability and branding records

These records configure custom subdomains for handling bounces and campaign click tracking. If omitted, your email service routes tracking through its shared infrastructure.

4. Custom return path (bounce domain) (optional)

• Type: CNAME Record
• Host: bounces (or the subdomain prefix specified in your platform settings)
• Value: The mail server hostname assigned by your email platform (such as pm.mtasv.net or sendgrid.net)
• TTL: Automatic

5. Branded tracking domain (optional)

• Type: CNAME Record
• Host: links (or track, click, or email as specified by your platform)
• Value: The tracking hostname assigned by your email platform
• TTL: Automatic

Setting up custom MX records (if required)

If your email service provider requires MX records for incoming replies, feedback loops, or dedicated sending subdomains:

1. Go to the Advanced DNS tab and scroll down to Mail Settings.
2. Select Custom MX from the dropdown menu.
3. Click Add New Record.
4. Enter the details:
   • Type: MX Record
   • Host: @ (or the subdomain prefix if using a dedicated sending subdomain)
   • Value: The mail server address provided by your platform (such as feedback-smtp.us-east-1.amazonses.com)
   • Priority: The integer specified by your provider (such as 10)
   • TTL: Automatic
5. Click the green checkmark icon to save.

Verifying your DNS records

New host and MX records in Namecheap typically take about 30 minutes to take effect, though resolvers that cached earlier values may take longer to update.

You can verify your DNS records in Windows PowerShell using Resolve-DnsName:

Check SPF

Resolve-DnsName -Name yourdomain.com -Type TXT

Check the Strings column. Verify that only one SPF record exists and that your sending provider’s include: tag is present.

Check DMARC

Resolve-DnsName -Name _dmarc.yourdomain.com -Type TXT

Verify that the Strings column contains v=DMARC1; p=....

Check DKIM

Replace s1 with the selector from your email platform:

Resolve-DnsName -Name s1._domainkey.yourdomain.com -Type CNAME

If your platform uses TXT-based DKIM, change the -Type argument to TXT. The output should return your provider’s hostname or public key.

Check tracking and bounce records (if configured)

Resolve-DnsName -Name bounces.yourdomain.com -Type CNAME

The output should show your provider’s target hostname in the NameHost column.

Check MX records (if configured)

Resolve-DnsName -Name yourdomain.com -Type MX

Verify that the NameExchange column lists your mail servers with the correct priority numbers in the Preference column.

Common troubleshooting issues

Issue	Root cause	Solution
Subdomain hostname is duplicated (s1._domainkey.yourdomain.com.yourdomain.com)	The full domain was entered into the Host field.	Enter only the prefix (such as s1._domainkey). Namecheap appends your root domain automatically.
ESP reports MX records missing	The current Mail Settings option does not contain the third-party MX records.	Scroll to Mail Settings on the Advanced DNS page, select Custom MX, and enter the exact MX records from your provider.
SPF or DKIM fails authentication check	Quotation marks were pasted into the Value field.	Remove surrounding quotes from the Value field. Namecheap stores the value as a raw string.
SPF status shows PermError	Two or more separate TXT records begin with v=spf1.	Delete the duplicate record and merge all include: mechanisms into a single SPF entry.
Advanced DNS records do not resolve externally	The records were added in a dashboard that is not authoritative for the domain.	Use Advanced DNS for BasicDNS, PremiumDNS, or FreeDNS; use cPanel for Namecheap Web Hosting DNS; otherwise edit records at the active nameserver provider.