GoDaddy
How to set up SPF, DKIM and DMARC in GoDaddy DNS
Set up SPF, DKIM and DMARC in GoDaddy DNS: who supplies each value, what to type in Name, and how to handle GoDaddy's default DMARC record.
Check your current setup:
Step by step, by protocol
GoDaddy SPF record: how to add or edit it in DNS
Add or edit a GoDaddy SPF record: one TXT record at Name @, the Edit DNS path, what goes in Value and how to confirm it works.
GoDaddy DKIM: add the record and confirm mail is signed
GoDaddy DKIM setup: where to add the CNAME or TXT record, what to type in Name, and how to confirm Microsoft 365 or Google Workspace mail is signed.
DMARC GoDaddy setup: add or edit the _dmarc TXT record
DMARC GoDaddy setup: check for GoDaddy's default _dmarc record, then add or edit one TXT record so the reports reach you.
How the three records fit together
To set up SPF, DKIM and DMARC in GoDaddy DNS, you add their records in the domain's DNS tab. Each protocol answers a different question about a message.
- SPF (Sender Policy Framework) lists the servers allowed to send for your domain. You publish one TXT record at the root of the domain.
- DKIM (DomainKeys Identified Mail) adds a digital signature to each message. Receivers fetch the public key from DNS, at a name built from a selector. A selector is a label that lets a domain keep several keys.
- DMARC (Domain-based Message Authentication, Reporting and Conformance) connects those results to the From address people see. A message passes when SPF or DKIM passes for a domain aligned with From. The record also says how to treat failures and where to send reports.
GoDaddy's part is small. Its DNS tab stores the records. The values come from whoever sends your mail, and that may be GoDaddy or another service. Each record has its own walkthrough: SPF at GoDaddy, DKIM at GoDaddy and DMARC at GoDaddy.
Confirm that GoDaddy hosts your DNS
GoDaddy's editor controls your domain only if the domain uses GoDaddy nameservers, the servers that answer DNS for it. GoDaddy says domains on other nameservers are managed at that other provider. To see which ones yours uses, run this command with your domain:
nslookup -type=NS example.com 1.1.1.1
GoDaddy's own DNS troubleshooting page uses a domaincontrol.com host as its nameserver example. If your result names another company's servers, make every change below at that DNS provider.
Where the records live
Sign in to your Domain Portfolio and select the domain to open Domain Settings. Then select DNS to see the records. To add one, select Add New Record, choose the Type, and fill in Name, Value and TTL. TTL is how long servers cache the record, and GoDaddy's default is 1 hour. Select Save, or Save All Records if you added several. If the domain has Domain Protection, GoDaddy also asks you to verify your identity.
In Name, type only the part before your domain:
@for SPF, because it sits at the root of the domain._dmarcfor DMARC.- The prefix your sender gives you for DKIM, which ends in
._domainkey.
Who supplies each value
Professional Email powered by Titan. The SPF record is below. GoDaddy adds it for you when the domain, DNS and email sit in the same GoDaddy account.
v=spf1 include:secureserver.net -all
DKIM is two CNAME records, secureserver1._domainkey and secureserver2._domainkey. Their targets and the DMARC value come from the Email & Office Dashboard. The finished set is four records.
Microsoft 365 from GoDaddy. GoDaddy lists the same SPF value and adds it under the same condition. You generate the DKIM keys in the Microsoft Defender portal and publish them as CNAME records. With the Advanced Email Security add-on, the SPF value is in the Email & Office Dashboard and DKIM is one TXT record.
Hosting email. GoDaddy lists the same SPF value for Web Hosting (cPanel), VPS Hosting and Managed Hosting for WordPress. Only the VPS plans have DKIM steps. There, DKIM is a TXT record, and cPanel (Email Deliverability) or Plesk (Mail Settings) shows its Name and Value.
Another service. Copy what that service gives you. Google Workspace uses a TXT record at google._domainkey and this SPF record:
v=spf1 include:_spf.google.com ~all
Microsoft 365 uses CNAME records at selector1._domainkey and selector2._domainkey and this SPF record:
v=spf1 include:spf.protection.outlook.com -all
Your domain keeps one SPF record, so several senders share it. Add each new include: before the final -all or ~all. With -all, receivers can refuse mail from any server you left out, so list every sender first.
Check DKIM alignment
DMARC counts DKIM only when the signing domain matches your From domain or shares its organizational domain, which is usually the registered domain. The signing domain is the d= value in the signature.
GoDaddy's articles do not say which domain its signatures use. Receivers look up the key at the selector, then _domainkey, then the d= domain. A record published under your domain can therefore verify only a signature with your domain in d=. To confirm it, send yourself a message and read d= in the DKIM-Signature header.
Set them up in this order
GoDaddy's articles ask for SPF and DKIM before DMARC.
- SPF. Edit the TXT record at
@that starts withv=spf1, or add one if none exists. - DKIM. Add the records your sender gives you. Then finish the setup on the sender's side if it asks you to, as Microsoft does.
- DMARC. Look for
_dmarcin the DNS tab first. If a record is there, edit it instead of adding a second, keep its current policy and confirm every sender passes before tightening it. If nothing is there, add a TXT record with Name_dmarcand this Value:
Use this starter value only if no DMARC policy exists at this name. Otherwise edit the existing record, preserving its p=, alignment settings and report addresses; add your monitored rua destination there. Never create a second policy record.
v=DMARC1; p=none; rua=mailto:dmarc@example.com
With p=none you ask for reports and no enforcement. rua is the reporting address, so use the one DMARC Pulse gives you. Preserve existing policy, alignment and report destinations. For a first deployment, monitor at p=none; after all legitimate senders align, assess p=quarantine. p=reject is optional and needs a separate mailing-list/forwarding risk assessment. Receivers decide individual delivery.
Confirm it worked
GoDaddy says most DNS changes take effect within an hour but could take up to 48 hours to update globally. In the DNS tab, the world icon in the Propagation column shows the global update status. Then run the SPF checker, the DKIM checker and the DMARC checker. You want exactly one SPF record and exactly one DMARC record.
Common problems
- A
_dmarcrecord already exists. Since April 2025, GoDaddy gives new domains, purchased or transferred in, a default DMARC record withquarantineas the initial policy. It says older domains will get one in the future and gives no date. Edit that record instead of adding a second. RFC 9989 tells receivers to discard every_dmarcrecord when more than one comes back, so your policy stops applying. - A new default causes legitimate failures. Diagnose the sender first. Preserve intentional enforcement; the owner may temporarily choose
p=nonefor an untouched automatic default, accepting reduced protection, then restore it after validation. - Reports go to GoDaddy. GoDaddy's default sends them there until you change the
ruaaddress. ruais missingmailto:. GoDaddy's hosting email article printsrua=dmarc_rua@onsecureserver.net. RFC 9989 definesruaas a list of URIs, and RFC 9990 says receivers should ignore malformed ones. Always writemailto:before the address.pct=100in GoDaddy's Microsoft 365 example. RFC 9989 removed thepcttag, so leave it out.- Two SPF records. GoDaddy warns that only one SPF record works on a domain at a time, and RFC 7208 returns
permerrorwhen a check finds more than one. GoDaddy may have added one already, so check first and merge them into a single record. - Enter only the prefix in Name. GoDaddy defines Name as "The hostname or prefix of the record, without the domain name." For a DKIM record, type
selector1._domainkey, notselector1._domainkey.example.com. - GoDaddy refuses the record. A CNAME Name can't be
@or a name already in use. A TXT Value accepts up to 1024 ASCII characters. - Your changes have no effect. The domain probably uses other nameservers. Edit the records where they point.
- A checker still shows the old value. GoDaddy says its nameservers apply changes within minutes. Outside resolvers can keep the old value for up to the previous TTL.
- Microsoft's articles show two SPF values. Its GoDaddy article prints
include:secureserver.net, and its SPF article printsinclude:spf.protection.outlook.com. GoDaddy documents the first for Microsoft 365 bought from GoDaddy. Otherwise use the second. In DNS,secureserver.netcurrently leads throughspf-0.secureserver.nettospf.protection.outlook.com, and that record also lists IP ranges of its own.