How do you add a DMARC record in GoDaddy?
To add a DMARC record in GoDaddy, open your Domain Portfolio, select the domain, select DNS, then Add New Record. Choose type TXT, enter _dmarc as the name, paste a value such as v=DMARC1; p=none; rua=mailto:reports@example.net, keep the default TTL and select Save. First check whether GoDaddy already created a DMARC record, and edit that one instead.
That check matters more at GoDaddy than at most DNS hosts, because GoDaddy now publishes a default DMARC record on new domains. This guide covers the nameserver check, GoDaddy's default record, the exact fields, Microsoft 365 bought through GoDaddy, verification and managing many client domains with delegate access. DMARC (Domain-based Message Authentication, Reporting and Conformance) builds on SPF (Sender Policy Framework) and DKIM (DomainKeys Identified Mail). For the protocol itself, start with the DMARC guide, and for each tag in the record, see how to create a DMARC record step by step.
Version note: GoDaddy changes its dashboard from time to time. The steps and field names here were checked against GoDaddy's own help pages in November 2026. If a label looks different in your account, the record itself does not change: one TXT record named _dmarc.
Key takeaways
- The record is a TXT record with the Name
_dmarc. GoDaddy wants the prefix only, without the domain name. - GoDaddy says that new domains bought from April 2025 get DMARC set up automatically, with a quarantine policy and reports sent to a GoDaddy address. Edit that record rather than adding a second one.
- Editing DNS at GoDaddy only changes live DNS when the domain uses GoDaddy nameservers. Check with
dig NSfirst. - GoDaddy's Microsoft 365 sample still includes the
pcttag, and another sample omitsmailto:before the report address. Under RFC 9989, droppctand always writerua=mailto:. - For client portfolios, use GoDaddy delegate access instead of shared logins, and keep a record of who changed each
_dmarcvalue.
Is the domain's DNS actually hosted at GoDaddy?
Check before you edit anything. GoDaddy's Manage DNS records page says that domains using GoDaddy nameservers can have their records managed in the GoDaddy account, whether or not GoDaddy is the registrar. If the domain uses other nameservers, its DNS is managed at that other provider, and a record added at GoDaddy is never served.
$ dig +short NS example.com
ns41.domaincontrol.com.
ns42.domaincontrol.com.
GoDaddy's own DNS troubleshooting article notes that GoDaddy's nameservers usually include domaincontrol.com. On Windows, run Resolve-DnsName -Name example.com -Type NS. Our DNS lookup tool gives the same answer without a terminal.
| Nameservers end in | Where to add _dmarc |
Guide |
|---|---|---|
domaincontrol.com |
GoDaddy DNS | This page |
ns.cloudflare.com |
Cloudflare dashboard | Cloudflare DNS |
Azure DNS (azure-dns) |
Azure portal, CLI or PowerShell | Azure DNS |
| A web host's own nameservers | Often the host's cPanel | cPanel |
This split is common with client domains: the domain is registered at GoDaddy, but DNS moved to Cloudflare or the web host years ago. The GoDaddy DNS page may still show old records that nobody queries.
Does GoDaddy already add a DMARC record for you?
Often, yes. GoDaddy's help page What is DKIM, DMARC and SPF? says that all new domains purchased with GoDaddy from April 2025 have DMARC set up automatically, and that domains bought earlier will get it in the future. So look for an existing _dmarc TXT record before you add anything.
The same page gives the record GoDaddy uses, which you can also add yourself:
v=DMARC1; p=quarantine; adkim=r; aspf=r; rua=mailto:dmarc_rua@onsecureserver.net;
GoDaddy's announcement on its DMARC implementation describes quarantine as the initial policy for new and transferred domains, says customers keep full control of the record, and says customers using third-party email providers must complete SPF and DKIM themselves. The help page adds that aggregate reports go to GoDaddy by default and that you can change the address.
Three consequences for anyone setting up a domain:
- Do not add a second record. RFC 9989 says that if more than one DMARC record is returned, they are all discarded. Two records leave the domain with no policy at all.
- Quarantine starts on day one. If Microsoft 365, Google Workspace or a newsletter platform sends for the domain before SPF and DKIM are aligned, that mail can land in junk folders.
- Reports go to GoDaddy. To see your own aggregate data, replace or extend the
ruavalue with an address you control.
How do you add the DMARC record in GoDaddy DNS?
Sign in, open the domain's DNS records, select Add New Record, choose TXT, enter _dmarc in Name, paste the DMARC string into Value, leave TTL at its default and select Save. These are the steps from GoDaddy's Add a TXT record page, with DMARC values filled in.
- Sign in to your GoDaddy Domain Portfolio.
- Select the domain to open its Domain Settings page.
- Select DNS to see the domain's records. Look for an existing TXT record named
_dmarc. If one exists, edit it instead (see the next section). - Select Add New Record and choose TXT from the Type menu.
- Name:
_dmarc. - Value: the full DMARC string on one line.
- TTL: keep the default, which GoDaddy lists as 1 hour.
- Select Save. If the domain has Domain Protection, GoDaddy asks you to verify your identity with a two-step verification code or a one-time password.
A first record in monitoring mode:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net
GoDaddy limits the Value to 1024 ASCII characters, far more than a DMARC record needs. GoDaddy does not check DMARC syntax, so build the value with the DMARC record generator if you are unsure.
What do you enter in the Name field?
Enter _dmarc only. GoDaddy's field takes the host or prefix without the domain name, uses @ for the root domain, and rejects names that start or end with a period or hyphen. Do not enter @ for DMARC: that would publish the text at example.com itself, where receivers never look for a DMARC policy.
For a subdomain such as marketing.example.com, enter _dmarc.marketing. More patterns are in DMARC record examples for common setups.
What TTL should you use?
Keep GoDaddy's default of 1 hour unless you plan a policy change soon. GoDaddy says most DNS changes take effect within an hour but can take up to 48 hours to update globally. Its developer documentation gives 600 seconds as the minimum TTL on the v3 API.
How do you change GoDaddy's default DMARC record?
Open the domain's DNS records, select the Edit icon next to the _dmarc TXT record, change the Value and select Save. GoDaddy's Edit a TXT record page describes the same fields as for a new record, plus a globe icon in the Propagation column that shows whether the change has spread.
Typical edits to the default record:
| Situation | Edit | Example value |
|---|---|---|
| Senders not yet known, or mail landing in junk | Step back to monitoring | v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net |
| You want your own reports | Replace the GoDaddy rua address |
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.net |
| You want reports in both places | Comma-separated rua list |
rua=mailto:dmarc-reports@example.net,mailto:dmarc_rua@onsecureserver.net |
| All senders aligned for a while | Move to enforcement | v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.net |
The adkim=r and aspf=r tags in GoDaddy's value set relaxed alignment, which is already the default, so removing them changes nothing. RFC 9989, Section 4.7, defines rua as a comma-separated list, so receivers send reports to each address.
One caution when copying GoDaddy's samples: the value on GoDaddy's hosting email page shows rua=dmarc_rua@onsecureserver.net without mailto:. RFC 9989 defines rua as a list of URIs and requires receivers to support mailto:, so write the scheme in front of every address.
What changes when Microsoft 365 is bought through GoDaddy?
The DMARC record itself is the same, but GoDaddy sets the order and some of the values. GoDaddy's article Add a DMARC record to my domain for Microsoft 365 lists an SPF record and DKIM as prerequisites, then adds the TXT record at _dmarc with the default TTL. Its steps apply only when DNS is managed at GoDaddy.
- SPF. GoDaddy's SPF article gives
v=spf1 include:secureserver.net -allfor Microsoft 365 from GoDaddy, and says GoDaddy adds it for you when the domain, DNS and email are in the same account. Other senders go into the same record. See multiple SPF records: how to merge them. - DKIM. GoDaddy's DKIM article has you create the keys in the Microsoft 365 Defender portal, add the two CNAME records it generates in GoDaddy DNS, then switch signing on. The article does not say GoDaddy adds these automatically.
- The sample value. GoDaddy's Microsoft 365 article uses
p=quarantineplus the removedpcttag, with bothruaandruf. Droppct, and addrufonly if you want failure reports and accept the personal data they can contain.
Microsoft's own DMARC setup guide confirms there is no Microsoft 365 admin portal for DMARC on custom domains: you create the record at your registrar or DNS host, and the hostname _dmarc is required. It recommends starting at p=none. For the rest of the tenant setup, see DMARC and Microsoft 365.
Should the GoDaddy DMARC record include pct?
No. RFC 9989 replaced RFC 7489 and removed pct, along with ri and rf, and receivers must ignore unknown tags. GoDaddy's Microsoft 365 sample and Microsoft Learn still show pct, but a percentage ramp is historic. Publish each policy in full: p=none, then p=quarantine, then p=reject.
For a cautious step, RFC 9989 adds t=y, which asks receivers to apply the next lower policy while reports continue as normal:
v=DMARC1; p=quarantine; t=y; rua=mailto:dmarc-reports@example.net
Remove t=y once the level is confirmed. New DMARC tags: np, psd and t explains the other additions, and pct is going away covers what replaces the ramp. The UK NCSC email security and anti-spoofing guidance follows the same principle: start at none, fix legitimate senders using reports, then enforce.
How do you verify the GoDaddy DMARC record?
Query _dmarc and confirm exactly one DMARC record comes back with the value you saved. Then ask one of the domain's GoDaddy nameservers directly, which skips resolver caches. GoDaddy's developer documentation uses the same approach of querying its authoritative nameserver to confirm a change.
$ dig +short TXT _dmarc.example.com
"v=DMARC1; p=none; rua=mailto:dmarc-reports@example.net"
$ dig @ns41.domaincontrol.com +short TXT _dmarc.example.com
Use the nameserver names your own dig NS query returned. On Windows, use either of these:
Resolve-DnsName -Name _dmarc.example.com -Type TXT
nslookup -type=TXT _dmarc.example.com
If two strings come back, there are two records, usually GoDaddy's default and a new one. Delete one. The DMARC checker validates syntax and flags duplicates, and how to fix "no DMARC record found" covers an empty answer.
How should MSPs manage DMARC for client domains at GoDaddy?
Ask each client to invite you as a delegate rather than share their GoDaddy password. GoDaddy's delegate access levels include Domains Only, which allows domain management actions without product access or purchases. Delegates cannot view or change the account's credentials, manage payment methods or invite others.
- Invitations. The client sends the invite from the Delegate Access page under People who can access my account, choosing Invite to Access. GoDaddy's invite guide says pending invitations expire after 48 to 72 hours, that the invitee needs a GoDaddy account, and that domain access is managed separately through delegate folder permissions.
- Check what "management" covers. GoDaddy's levels page does not mention DNS by name. Confirm on a test change that your delegate role can edit DNS records before you plan a client rollout.
- Inventory. Run
dig NSanddig TXT _dmarcfor every client domain. Mark which ones usedomaincontrol.com, which have GoDaddy's default record, and which have none. - Report destinations. Replace or extend GoDaddy's
ruaaddress with your reporting address. If it is on another domain, that domain must publish an authorisation record as defined in RFC 9990, Section 4. See authorising external DMARC report destinations. - Automation. GoDaddy's developer documentation lists v3 DNS record endpoints under
/v3/domains/zones/{domain}/dns-records, with thedomains.dns:updatescope for changes. Read existing records first, so a script does not create a second_dmarcrecord. - Change log. Note the old value, the new value and the reason for each edit. DMARC change management for MSP portfolios suggests a format.
DMARC AI collects aggregate reports for every client domain in one multi-tenant view, so after a GoDaddy change you can confirm that reports arrive at your address and that each client's legitimate senders align before moving to enforcement. More on running DMARC as a service is on DMARC for MSPs.
What should you check when the GoDaddy DMARC record does not work?
Start with the nameservers, then the number of records, then the name and value. Most GoDaddy problems come from editing a zone that is not live, adding a record beside GoDaddy's default, or copying a sample value without changes. The table lists the usual symptoms.
| Symptom | Likely cause | Fix |
|---|---|---|
Record visible in GoDaddy, but dig returns nothing |
Nameservers point to another DNS host | Check dig NS and add the record where DNS is hosted |
| Checker reports no valid policy | GoDaddy's default record plus a new one | Keep one; RFC 9989 discards all when more than one returns |
Record found at example.com, not _dmarc.example.com |
@ entered as the Name |
Delete it and re-add with _dmarc |
| No reports arrive at your address | rua still points to GoDaddy, or mailto: missing |
Edit rua to mailto: plus your address |
| Legitimate mail in junk on a new domain | Default p=quarantine before senders were aligned |
Step back to p=none, fix SPF and DKIM, then enforce |
| Save asks for a code | Domain Protection is on | Enter the two-step code or one-time password |
| Microsoft 365 mail fails DMARC | DKIM CNAMEs added but signing not switched on | Enable signing in the Microsoft 365 Defender portal |
Frequently asked questions
Does GoDaddy add a DMARC record automatically?
For new domains, yes. GoDaddy says domains purchased from April 2025 have DMARC set up automatically, with a quarantine policy and aggregate reports sent to a GoDaddy address. Domains bought earlier will get it later, according to GoDaddy. Check the DNS page or run dig TXT _dmarc.example.com before adding your own record.
What host name does GoDaddy need for a DMARC record?
Enter _dmarc in the Name field. GoDaddy expects the prefix only and appends the domain, so the record becomes _dmarc.example.com. Do not use @, which is the root domain, and do not type the full domain name. For a subdomain in the same zone, enter _dmarc.marketing instead.
Can I keep GoDaddy's reports and receive my own?
Yes. List both addresses in one rua tag, separated by a comma, each starting with mailto:. RFC 9989 defines rua as a comma-separated list, so receivers send aggregate reports to each address. If your address is on a different domain from the client's, publish the external authorisation record from RFC 9990.
How long does a GoDaddy DNS change take?
GoDaddy says most DNS updates take effect within an hour but can take up to 48 hours globally. The default TTL is 1 hour, so resolvers that cached the old value may keep it that long. Query a GoDaddy nameserver directly with dig to confirm the new value is published.
Next steps
Adding a DMARC record in GoDaddy takes a minute. The checks around it take longer: confirm GoDaddy nameservers, look for GoDaddy's default record, point rua at an address you control, set up SPF and DKIM for every sender, and keep one _dmarc record. Then use aggregate reports, as described in moving from monitoring to enforcement safely, to decide when each domain moves from p=none to p=reject.