DNS host · DKIM

DKIM record for Namecheap

How to add a DKIM record when DNS or mail is at Namecheap. Real steps, then a live lookup.

Use Namecheap Advanced DNS. If you turned on PremiumDNS or pointed NS at Cloudflare, this panel is inert.

  1. TXT or CNAME as specified. Host is the part before your domain, e.g. google._domainkey.

Official docs: Namecheap. Other records for this provider: SPF · DKIM · DMARC

Does this page apply to you?

Run this first. Namecheap only matters if it is where your DNS or mail actually lives.

dig +short NS yourdomain.com

Expect: Names ending in registrar-servers.com (BasicDNS or PremiumDNS). If you see something else, such as Cloudflare, the Advanced DNS panel at Namecheap is inert.

Specific to Namecheap

  • The Host field takes the part before your domain, such as google._domainkey. Namecheap appends the rest.
  • Allow up to about 30 minutes before testing; changes on Namecheap's own DNS are quick but not instant.
  • If the provider gave you a CNAME, add a CNAME record with the same host rule.

What you should end up with

Illustrative values. Use the exact host and value your provider shows you where it generates them.

Type  Name  Value
TXT  google._domainkey  v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8A…

What the receiving server does with this record

Your sending server signs each message with a private key and adds a DKIM-Signature header naming the signing domain (d=) and the selector (s=). The receiver builds the hostname s._domainkey.d, fetches the public key from DNS, and verifies the signature. A valid signature proves the message came from that domain and was not changed on the way.

Mistakes that break it

  • Published, but signing never switched on. Most providers need a second step after the DNS record exists. Until then they sign with their own domain, which passes DKIM but does not align with your From address, so it does nothing for DMARC.
  • A doubled hostname. Typing the full name into a field that already appends your domain gives selector._domainkey.yourdomain.com.yourdomain.com.
  • A damaged key. A 2048-bit key is longer than one 255-character DNS string. Stray spaces, line breaks and silent truncation all invalidate it.
  • The wrong selector. The record is published under one name and the sender signs with another.

Check it from the command line

The final test is a real message: send one to a Gmail address, open Show original, and read the DKIM line. Before that, confirm the record resolves:

dig +short TXT google._domainkey.yourdomain.com

Check it live

Check the DKIM record

Look up the live DNS after you save. This tool does not spend credits.

Related