The DNS records
The key is unique to each subscription, so copy it from the Private Email page in your Namecheap account. Enter it without brackets or quotes.
DKIM key (subscriptions from 2 June 2026)
Type: TXT · Host: privateemail._domainkey
v=DKIM1;k=rsa;p=<public key shown under DKIM in your Namecheap account>
DKIM key (subscriptions bought before 2 June 2026)
Type: TXT · Host: default._domainkey
v=DKIM1;k=rsa;p=<public key shown under DKIM in your Namecheap account>
Use one of the two hosts, the one that matches your subscription, not both.
Set it up and turn on signing
- Sign in to Namecheap, open the Private Email menu and click Manage next to your domain or subscription.
- Under DKIM, click Generate to create the key, or Show DKIM to copy one that already exists.
- Copy the DNS record field: the value that begins
v=DKIM1;k=rsa;p=MIIBIjANB.... - Add it as a TXT record where your DNS is hosted: automatic on BasicDNS, in cPanel for Web Hosting DNS, in your Namecheap account for Premium DNS, or at your outside DNS provider.
- If your DNS host splits long values across two fields, put as much of the key as possible in the first, rather than separating
v=DKIM1; k=rsa;from the rest. - Allow up to an hour, then look up
privateemail._domainkey.yourdomain.comto confirm it is live.
DMARC alignment
Private Email signs with your own domain, and the key sits under your domain's _domainkey name, so a passing signature lines up with your From address for DMARC. Namecheap says the DKIM record is mandatory for outgoing mail to work correctly and recommends publishing it together with SPF and a DMARC record on _dmarc, starting from v=DMARC1; p=none; with a report address.
Key length and rotation
This is a TXT key in your own zone, so Namecheap can't swap it for you: a new key means generating it in the Private Email page and replacing the record. The key shown is RSA (k=rsa); Namecheap's article doesn't state its length or a rotation schedule. Moving the domain to new nameservers means copying the record across too.
Common mistakes
- The wrong selector for your plan. Subscriptions bought before 2 June 2026 sign with
default; newer ones withprivateemail. A key under the other name is never checked. - Quotes or brackets pasted into the value. Namecheap says to enter the key without them.
- A value split in the wrong place. Splitting off only the
v=DKIM1; k=rsa;tag leaves a record some hosts store incorrectly. - Records added at Namecheap while the domain uses outside nameservers. Add the TXT where the nameservers point.
Check your Private Email DKIM key
The selector is filled in for you; add your domain. Free, reads public DNS only.
Frequently asked questions
What is the DKIM selector for Namecheap Private Email?
privateemail for subscriptions bought on or after 2 June 2026, so the record name is privateemail._domainkey. Subscriptions bought before that date use default._domainkey. The DKIM Checker below is prefilled with the newer selector.
Where do I find my Private Email DKIM key?
In your Namecheap account: open Private Email, click Manage next to the subscription, then Generate or Show DKIM under the DKIM section. The key is unique to your subscription, so a value from a guide or another domain won't work.
Is Private Email DKIM set up automatically?
On Namecheap BasicDNS, yes: Namecheap says the TXT record should be configured automatically. On Web Hosting DNS, Premium DNS or third-party nameservers, you add it yourself.
Sources
- Namecheap Knowledgebase: How to set up a DKIM record for Private Email
- Namecheap Knowledgebase: Namecheap Private Email records for domains with third-party DNS
- RFC 6376: DomainKeys Identified Mail (DKIM) Signatures
- RFC 8301: Cryptographic Algorithm and Key Usage Update to DKIM
Checked against Private Email's documentation on November 3, 2026. Providers change their setup screens; if yours differs, follow the values your admin console shows.
DKIM records for other providers
- Microsoft 365CNAME: selector1, selector2
- Google WorkspaceTXT: google
- Zoho MailTXT: you choose (e.g. zoho)
- GoDaddyCNAME: secureserver1, secureserver2
- FastmailCNAME: fm1, fm2, fm3
- Proton MailCNAME: protonmail, protonmail2, protonmail3
- iCloud MailCNAME: sig1
- HostingerCNAME: hostingermail-a, hostingermail-b, hostingermail-c
- IONOSCNAME: s1-ionos, s2-ionos, s42582890
- Rackspace EmailTXT: shown in the Cloud Office Control Panel
- Amazon SESCNAME or TXT: <token1>, <token2>, <token3> (Easy DKIM), your own (BYODKIM)
- SendGridCNAME or TXT: s1, s2
- MailgunTXT or CNAME: assigned by Mailgun (e.g. pic, krs, smtp), pdk1, pdk2 (Automatic Sender Security)
- PostmarkTXT: <timestamp>pm (e.g. 20131031155228pm)
- MailjetTXT: mailjet
- SMTP2GOCNAME: shown in SMTP2GO for your domain
- SparkPostTXT: scph<number> (generated, e.g. scph0316), your own (API)
- Elastic EmailTXT: api
- ResendTXT: resend
- MailerSendCNAME: ms1, ms2
- MailchimpCNAME: k2 and a second CNAME (Marketing), mte1, mte2 (Transactional)
- BrevoTXT or CNAME: mail (TXT), 2 CNAMEs from your account
- HubSpotCNAME: hs1-<number>, hs2-<number>
- KlaviyoCNAME: km1, km2 (marketing), kt1, kt2 (transactional), ks1, ks2 (service)
- ActiveCampaignCNAME: acdkim1, acdkim2
- Constant ContactCNAME or TXT: ctct1, ctct2 (CNAME), generated per key (TXT)
- SquarespaceCNAME: squarespace
- Dynamics 365 Customer InsightsCNAME: CNAME1 and CNAME2 from the wizard (e.g. namkey1)
- MailerLiteCNAME: litesrv
- Campaign MonitorTXT: cm, your own (existing keys)
- KitCNAME: cka
- MarketoTXT: chosen by you in Marketo
- Account Engagement (Pardot)TXT: shown in Expected DNS Entries
- Customer.ioTXT: cio
- Zoho CampaignsTXT: numbered per account (e.g. 2232)
- SalesforceCNAME: you choose two (e.g. example-sf-a, example-sf-b)
- ZendeskCNAME: zendesk1, zendesk2
- Help ScoutCNAME: strong1, strong2
- IntercomCNAME: intercom
- OdooCNAME: odoo
Compare every provider's selectors in one table · SPF record for Private Email
Related guides
How to find a domain's DKIM selector, and check its key
Find a DKIM selector from the s= tag in an email header, see the selectors Microsoft 365, Google Workspace and common senders use, then check the key.
8 min read SPF, DKIM & DMARCHow to rotate DKIM keys without breaking email
How often to rotate DKIM keys, which key length to use, how to name selectors, and how to rotate in Microsoft 365, Google Workspace and on your own server.
9 min read SPF, DKIM & DMARCDKIM "body hash did not verify" and other DKIM failures: causes and fixes
Fix DKIM failures: body hash did not verify, signature did not verify, no key for signature and short keys. Causes from mailing lists to broken TXT records.
9 min readLast updated