Skip to content
DMARC Pulse
Guides

Namecheap

Namecheap DKIM: set up DKIM, SPF and DMARC records

Namecheap DKIM setup: generate the Private Email key, use the right host (privateemail or default), then add SPF and DMARC without breaking mail.

How Namecheap DKIM works

Namecheap DKIM for Private Email is a TXT record: you generate the key in your Namecheap account and publish it at privateemail._domainkey under your domain. Private Email subscriptions bought before June 2, 2026 use default._domainkey instead. DKIM (DomainKeys Identified Mail) adds a signature to each message, and receivers check it against that public key.

Existing DMARC policy: authenticating Namecheap does not require resetting it. Keep one _dmarc record, preserve p, subdomain and alignment settings, and merge any needed rua address with existing destinations. The p=none example below is only for a new deployment without a valid record.

Namecheap can play three roles, and each one leads to different records:

  • Private Email is Namecheap's subscription mailbox service. The DKIM key comes from your Namecheap account.
  • cPanel email comes with Namecheap Web Hosting. The records come from cPanel's Email Deliverability page.
  • DNS hosting only means another company runs your mail. That company gives you the records, and you publish them at Namecheap.

Where each record goes

Your nameservers decide which panel publishes your records:

  • BasicDNS, PremiumDNS or FreeDNS: your Namecheap account, under Domain List, Manage, then the Advanced DNS tab.
  • Web Hosting DNS (dns1.namecheaphosting.com and dns2.namecheaphosting.com): cPanel, under Domains, then Zone Editor.
  • Third-party nameservers: the panel of your current DNS provider.

Set up DKIM for Private Email

Check your purchase date first, because it sets the selector. A selector is the label that tells receivers which key to fetch, as this page on DKIM selectors explains. Subscriptions bought before June 2, 2026 use default. The others use privateemail.

  1. Log in to Namecheap and open the Private Email menu.
  2. Click Manage next to your domain.
  3. Under DKIM, click Generate. If a key already exists, click Show DKIM instead.
  4. Copy the value from the DNS Record field. It starts with v=DKIM1. Enter it without brackets or quotes.
  5. Go to the panel your nameservers use and add a TXT record. In Advanced DNS, click Add New Record and choose TXT Record.
  6. Set Host to privateemail._domainkey, or default._domainkey on an older subscription. Paste the key into Value.
  7. Click Save all changes. Namecheap says changes normally take 60 minutes to come into effect.

Namecheap's DKIM article gives two answers for BasicDNS. One note says the record "should be configured automatically". Another says you add it manually on Basic or Premium DNS. Its BasicDNS setup article also has you add it by hand. So look in Host Records after you generate the key, and add the record if it is missing.

The public key sits under your own domain, so the signature's d= tag carries your domain. DKIM therefore aligns with your From address. Alignment means the domain a check validates matches the domain people see in From, and DMARC depends on it. Namecheap's setup articles do not say which envelope sender (the bounce address SPF checks) Private Email uses, so confirm SPF alignment from your own headers or reports.

Add SPF for Private Email

SPF (Sender Policy Framework) lists the servers allowed to send mail for your domain. Private Email needs this record at Host @:

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

On Namecheap's own DNS you can publish it two ways:

  • Automated setup: on the Advanced DNS tab, go to Mail Settings, choose Private Email and click Save changes. Namecheap creates the records for you. This option is meant for domains that use only Private Email.
  • Manual setup: in Mail Settings, choose Custom MX and add mx1.privateemail.com and mx2.privateemail.com as MX records at Host @, both with priority 10. Then add the TXT record above. Use this route if you send through more than one service.

Both routes point your incoming mail at Private Email. If another service receives your mail today, create your Private Email mailboxes before you change the MX records.

Each hostname can have only one SPF record. Namecheap warns that with several, none of the email services work properly, and RFC 7208 makes the result a permerror. If you already have a record, add include:spf.privateemail.com to it before the final ~all. SPF allows 10 DNS lookups in total, and this include used 4 of them on November 9, 2026.

Keep ~all until your reports look clean. Namecheap's spoofing article changes it to -all, which returns SPF fail for an unlisted sender. Each receiving server decides how to handle that result.

Private Email on Namecheap hosting nameservers

For a migration to Private Email, first create and test the destination mailboxes: changing MX redirects incoming mail. In cPanel Zone Editor, replace the old MX records with mx1.privateemail.com and mx2.privateemail.com, both priority 10. Set Email > Email Routing to Remote Mail Exchanger. Add the Private Email DKIM and SPF records in Zone Editor too. Private Email and cPanel email cannot run at the same time, and cPanel email stops working once the Private Email records are in place. Do not edit or remove your domain's A record, because that can take your website down.

Namecheap's article on Private Email records for hosting nameservers shows a merged SPF record with include:_spf.cpanel.net. That name did not exist in DNS on November 9, 2026. An include that points to a missing name makes SPF return permerror when a receiver reaches it, so leave that part out. Start from the SPF value that Email Deliverability suggests for your account and add include:spf.privateemail.com to it.

Publish DMARC on Namecheap

DMARC (Domain-based Message Authentication, Reporting and Conformance) tells receivers how you want failing mail handled and where to send reports. Publish one TXT record with Host _dmarc. If that host already has a DMARC record, edit it instead of adding a second one, because receivers discard all the records when they find more than one:

New policy only: use this starter value only when no valid DMARC record exists. For an existing record, keep its policy and merge the report address instead of pasting over the value.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

Replace the address with your own reporting address, such as the one DMARC Pulse gives you. With p=none you state no handling preference. Aggregate reports then show which IP addresses send as your domain and how SPF and DKIM did.

Namecheap's examples disagree, so check what you copy:

  • The BasicDNS and third-party DNS articles start at p=none. The hosting and Cloudflare articles show p=reject. Use p=none only for a new policy; preserve the settings of an existing valid record.
  • The automated part of the BasicDNS article prints rua=mailto@yourdomain.tld, with no colon after mailto. Write rua=mailto: followed by the address.
  • The TXT records article includes pct=100. RFC 9989 removed the pct tag, so leave it out.
  • cPanel's default record, v=DMARC1;p=none;, has no rua tag, and receivers send no aggregate reports without one.

Preserve existing policy during authentication. For a new policy, start at p=none and collect representative reports, which may take months. After fixing all legitimate streams, consider p=quarantine and observe reports again. Evaluate p=reject separately: it is optional, needs aligned DKIM rather than SPF alone, and RFC 9989 §7.4 advises against it when users post to mailing lists. Forwarding and list transformations need testing; receiving servers decide the final disposition.

cPanel email on Namecheap hosting

Skip the Private Email steps if cPanel sends your mail.

  1. In cPanel, open the Email section and click Email Deliverability.
  2. Find your domain and click Manage to see the suggested DKIM, SPF and DMARC values.
  3. Copy each value into your DNS zone. If the domain uses Namecheap's shared hosting nameservers, you can click Install the suggested record instead.

On those nameservers, Repair fixes invalid records for you. Review the suggested records before you confirm. If your SPF lists other senders, keep them in the record.

Namecheap states that SPF is not added to the DNS zone automatically, so this step is required. Its article does not name the DKIM selector, so use the one the page shows. The cPanel guide covers this path in more detail.

Confirm it worked

  1. Give the records up to 60 minutes. Then run the DKIM checker with your domain and your selector, privateemail or default.
  2. Check the root record with the SPF checker and the _dmarc record with the DMARC checker.
  3. Send a message to a mailbox at another provider and open its full headers.
  4. Paste them into the email header analyzer. Look for dkim=pass and header.d=example.com, plus a passing dmarc result.

Common problems

  • The DKIM lookup finds no record. You may be checking the wrong selector. Try default if your subscription dates from before June 2, 2026. Then confirm you saved the record in the panel your nameservers use.
  • The Host field contains your domain. Enter only the part before the domain, such as privateemail._domainkey. Namecheap calls this a system requirement, even when a provider asks for the full name.
  • The key fails after you paste it. Remove any brackets and quotes. If your panel has two value fields, put as much of the key as fits in the first and the rest in the second. Never leave only v=DKIM1; k=rsa; in the first field.
  • There are two SPF records. Merge them into one record at @ and delete the other.
  • DKIM passes and DMARC still fails. A signature counts for DMARC only when its d= domain aligns with your From domain. Another tool may be signing with its own domain. Your aggregate reports show which source it is.
  • Email Forwarding is selected in Mail Settings. Namecheap says the SPF record shown with it "is needed for free email forwarding to function, thus, it cannot be deleted". Its setup article has no DKIM step. Forwarding addresses cannot send mail, and Namecheap says free Email Forwarding cannot be used with Private Email or any other email service at the same time. To send from this domain with DKIM, move it to a mail service that signs your messages.
  • Mail bounces after you tighten the policy. Restore the last working policy if the new change caused the failure. Find and fix the legitimate source in reports before considering enforcement again.

Frequently asked questions

Does Namecheap support DKIM?
Yes, for Private Email and for cPanel email on Namecheap hosting. Private Email keys come from the Private Email menu in your account. cPanel shows its records under Email Deliverability. If another company sends your mail, that company gives you the record and you publish it in your DNS.
What is the DKIM selector for Namecheap Private Email?
It is privateemail, so the host is privateemail._domainkey. Subscriptions purchased before June 2, 2026 use default, so the host is default._domainkey.
What do I type in the Host field for DKIM at Namecheap?
Only the part before your domain, such as privateemail._domainkey. Namecheap says the domain name should not be included in the Host field.
What SPF record does Namecheap Private Email need?
A TXT record at host @ with the value v=spf1 include:spf.privateemail.com ~all. If the domain already has an SPF record, merge the include into it, because each hostname should publish only one.
How long does Namecheap DKIM take to start working?
Namecheap says DKIM changes normally take 60 minutes to come into effect. If a lookup still finds nothing after that, check the selector and confirm you saved the record in the panel your nameservers use.
Should I copy the p=reject example from Namecheap?
Not as a first step. Start with p=none and a rua address, read your aggregate reports, and tighten the policy only after every legitimate sender passes.

Sources consulted

RFC 7208 §5.2: include
checked 2026-11-09

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.