You don’t need any technical background. A DNS record is just a labelled line in your domain’s public directory that states a fact about it. For email you’re adding three lines, and GoDaddy gives each one the same set of fields. Understand those fields once and the rest is filling in boxes.
TXT vs CNAME, and “Host” vs “Value”
Two record types matter here:
- A TXT record holds plain text. SPF and DMARC are both TXT records — the text is the policy.
- A CNAME record is a pointer that says “for this name, look at that other name instead.” Mail providers usually give DKIM as a CNAME so they can rotate the key behind the scenes.
GoDaddy calls the two fields Host (name) and Value. The Host is where the record lives: @ means the root of your domain (example.com itself); anything else, like _dmarc, is a subdomain. The Value is what the record says. Getting the Host right is where most people slip.
1. Open GoDaddy DNS Management
Sign in, go to your Domain Portfolio (or “My Products”), find the domain, and click the three-dot menu → Edit DNS (older accounts show DNS → Manage Zones). You land on a table of records with an Add New Record button. GoDaddy’s official help for adding a record is here (TXT) and here (CNAME). Everything below happens on that screen.
2. Add the SPF record (a TXT at the root)
SPF lists the servers allowed to send mail as your domain. Click Add New Record and set:
- Type: TXT
- Host:
@(the root domain) - Value:
v=spf1 include:_spf.google.com ~all
Leave TTL on the default (1 hour) and click Save. Crucial rule: only one SPF record is allowed. If a TXT record beginning v=spf1 already exists (GoDaddy often adds one for Microsoft 365 or Workspace), edit that record and merge the new include: in — never create a second SPF record. Build a clean string with the SPF Generator.
3. Add the DKIM record (usually a CNAME)
DKIM lets your provider sign each message cryptographically. Your provider hands you the exact record — commonly a CNAME at a selector. Click Add New Record and set:
- Type: CNAME
- Host: the selector, e.g.
selector1._domainkey - Value: the target your provider gave you, e.g.
selector1-example-com._domainkey.provider.com
The GoDaddy gotcha: type only selector1._domainkey in Host. GoDaddy automatically appends .example.com, so if you type the full selector1._domainkey.example.com you’ll end up with a broken selector1._domainkey.example.com.example.com. Same for the Value if it’s one of your own subdomains — but the provider’s target is usually a full external hostname, which you paste exactly as given. If your provider gave DKIM as a TXT record instead, add a TXT with the selector as Host and the long v=DKIM1; k=rsa; p=… string as Value. Verify later with the DKIM Checker.
4. Add the DMARC record (a TXT at _dmarc)
DMARC ties SPF and DKIM to the visible From address and tells inboxes what to do on failure. Click Add New Record and set:
- Type: TXT
- Host:
_dmarc(again, no domain suffix — GoDaddy adds it) - Value:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
Start with p=none to monitor without affecting delivery, and point rua= at a mailbox you check. Generate one with the DMARC Generator and validate it with the DMARC Checker. When you’re ready to enforce, follow moving DMARC to reject safely.
GoDaddy-specific gotchas
- Use
@for the root. GoDaddy doesn’t accept a blank Host — type@. - Never type your domain in Host. GoDaddy auto-appends it; doubling it silently breaks the record.
- One SPF record only. Edit and merge; don’t duplicate.
- Saves can take a while. GoDaddy edits sometimes take up to an hour to publish — don’t assume a fresh record failed just because a checker doesn’t see it in the first minute.
Verify propagation
Once saved, confirm the records are visible worldwide with the DNS Propagation Checker, then check each individually with the SPF Checker, DKIM Checker and DMARC Checker. To confirm all three together, run the Email Health Check.
For what each record actually does and how DMARC alignment decides a pass, read the complete SPF, DKIM & DMARC guide. Using a different registrar? See the equivalents for Cloudflare, Namecheap, AWS Route 53, cPanel and Squarespace.