GoDaddy
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.
Before you start
A DMARC GoDaddy setup comes down to one TXT record named _dmarc, which you add or edit in your domain's DNS tab.
Check first whether the record already exists. GoDaddy says that since April 2025 new domains purchased or transferred into it get a default DMARC record with a quarantine policy, and that reports go to GoDaddy by default. For domains bought earlier, it says DMARC "will be added automatically in the future" and gives no date.
You also need:
- DNS hosted at GoDaddy. The Domain Settings page lists your nameservers at the top, and GoDaddy's usually include
domaincontrol.com. If yours point elsewhere, make this change at that DNS provider. - SPF and DKIM first. GoDaddy's instructions ask for both before DMARC, which needs one of them to pass for a domain aligned with your From address. See SPF at GoDaddy and DKIM at GoDaddy.
- Access to the account. Use the account that holds the domain, or sign in as a delegate whose permissions cover it.
- An address for reports. Aggregate reports are XML files, so use a mailbox you check or a service that reads them. See how rua and ruf work.
Steps
Add the GoDaddy DMARC record
-
Sign in to your Domain Portfolio and select the domain to open Domain Settings.
-
Select DNS to view the records. If a TXT record named
_dmarcis listed, skip to the next section. -
Select Add New Record, then choose TXT under Type.
-
In Name, enter
_dmarc. GoDaddy asks for the prefix without the domain name. -
In Value, paste this record with your own address:
TXTv=DMARC1; p=none; rua=mailto:dmarc@example.com
p=noneasks receivers to take no action and only send reports.ruasays where those go. -
Leave TTL at its default of 1 hour and select Save.
Edit a record that already exists
Never add a second record. RFC 9989, the current DMARC standard, has receivers discard all _dmarc records when they find more than one, so your policy stops applying.
- In the DNS tab, select Edit next to the
_dmarcrecord. - In Value, change the address after
rua=mailto:to yours. GoDaddy's help listsv=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;, so yours probably looks similar. - Preserve the existing
p=policy and alignment tags while editing report addresses. - Select Save.
Domains with Domain Protection need extra identity verification: a 2-step verification code, or a one-time password sent to your account email.
Caution: p=quarantine can send legitimate mail to spam at receivers that honor it, and p=reject can block it. GoDaddy marks quarantine as recommended, but RFC 9989 says domain owners usually start at p=none and must fix what the reports reveal before enforcing. Raise the policy one level at a time. See none, quarantine and reject.
Confirm it worked
GoDaddy says its nameservers apply a change within minutes, but outside resolvers can keep the old value for up to the previous TTL. Most updates take effect within an hour and could take up to 48 hours globally.
-
Run the DMARC checker on your domain, or query the record directly:
nslookup -type=TXT _dmarc.example.com 1.1.1.1 -
Look for exactly one answer that starts with
v=DMARC1, with thepandruavalues you saved. -
Wait for the first report. Periods typically cover one UTC day, and not every receiver sends reports.
Common problems
- Two
_dmarcrecords. Keep one valid, owner-approved DMARC record with the intended policy and report destinations. Do not concatenate policy records. - The lookup finds nothing. Confirm Name is
_dmarc, with no domain after it, and that the domain uses GoDaddy's nameservers. - Reports never reach you. GoDaddy's default sends them to GoDaddy until you change
rua. An address on another domain also needs an authorization record there. See DMARC reports not arriving. ruawithoutmailto:. GoDaddy's hosting email article showsrua=dmarc_rua@onsecureserver.net. RFC 9989 expects a URI there, and RFC 9990 tells receivers to ignore malformed ones. Always writerua=mailto:before the address.pct=100in the value. GoDaddy's Microsoft 365 example includes it. RFC 9989 removedpct, so leave it out.- Legitimate mail fails under an untouched default. Diagnose the failing sender first. The owner may temporarily choose
p=nonewhile fixing it, accepting reduced spoofing protection; restore enforcement after validation.