DNS host · DKIM

DKIM record for GoDaddy

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

GoDaddy is often the registrar and the DNS host. If NS records point elsewhere, these steps will not apply.

Your mail provider (Google, Microsoft, a sequencer) generates the DKIM host and value.
In GoDaddy DNS, add a TXT (or CNAME, if they gave you a CNAME) with that host — usually something._domainkey.
Do not put the full hostname in the name field if GoDaddy already appends the domain; use the selector._domainkey part only.

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

Does this page apply to you?

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

dig +short NS yourdomain.com

Expect: Names ending in domaincontrol.com. If you see something else, GoDaddy is only the registrar and DNS is edited at the host those nameservers belong to.

Specific to GoDaddy

In the Name field enter only the selector part, such as google._domainkey. GoDaddy appends your domain, and a doubled-up name is the most common DKIM failure on this host.
Paste a TXT value without surrounding quotes; the panel adds them.
If your provider supplied a CNAME instead of a TXT, create a CNAME with the same name 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.