| 10 min read

How to add or edit a DMARC record in GoDaddy

GoDaddy's DNS interface lets you add or edit DMARC as a TXT record at _dmarc. Here's the current GoDaddy path, including what to do if a default DMARC record already exists.

Standards basis: DMARC setup advice based on RFC 9989 for policy records and RFC 9990 for aggregate report destinations.

ML
Marc Lelu
How to add or edit a DMARC record in GoDaddy

GoDaddy is one of the largest domain registrars. Millions of businesses host DNS there, and many existing domains still need a DMARC record or a better reporting setup.

There is one important update. GoDaddy says that, starting in April 2025, new domains purchased or transferred into GoDaddy receive a default DMARC record with p=quarantine. We verified this policy and the current Domain Portfolio steps in August 2026.

That default does not finish the work. Existing domains may have no record. Domains using other nameservers must be edited at the authoritative DNS provider. A default record also needs a reporting address and verified SPF or DKIM alignment.

From the zones we review, the most common GoDaddy mistake is editing the registrar account when DNS is hosted somewhere else. The second is adding a new _dmarc TXT record beside GoDaddy’s default record.

The edit itself takes a few minutes. DNS propagation takes longer. One duplicate record or a wrong host value can make the policy invalid.

This guide shows you how to add or edit a DMARC record in GoDaddy, step by step, from login to verification.

Before you start

You’ll need access to your GoDaddy account with permission to edit DNS records. You also need to confirm that DNS is actually managed at GoDaddy. GoDaddy’s own DNS help notes that domains using GoDaddy nameservers are managed in the GoDaddy account; if your nameservers point to Cloudflare, Wix, Squarespace, Route 53, or another provider, edit the DMARC record there instead.

DMARC also depends on SPF and/or DKIM being set up for your legitimate mail. GoDaddy’s Microsoft 365 DMARC instructions explicitly put SPF and DKIM before DMARC. You can still publish p=none to start collecting reports, but do not move to enforcement until your real senders pass alignment.

If SPF is not set up yet, use the GoDaddy SPF setup guide first, then come back here to publish DMARC.

You’ll also need a DMARCTrust account to receive and monitor reports, which we’ll set up in the first step.

Step 1: get your DMARCTrust reporting address

Before touching GoDaddy, you need a reporting address. Without one, your DMARC record is just a policy with no visibility.

Sign up for DMARCTrust (free tier available) and add your domain. You’ll get a unique reporting address that looks like this:

[email protected]

Now use our DMARC generator to create your full record. Select p=none for first-time monitoring and paste your reporting address in the rua field. The generator outputs something like:

v=DMARC1; p=none; rua=mailto:[email protected];

Copy this value. You’ll paste it into GoDaddy next. If GoDaddy already created a default p=quarantine record and your mail is working, you can keep that policy and update the rua destination instead of starting over.

Step 2: log into GoDaddy

Go to GoDaddy’s Domain Portfolio and sign in to your account.

GoDaddy’s current TXT-record help uses this path: select an individual domain to open the Domain Settings page, then select DNS to view records.

You may also get there through My Products: click your profile icon, select My Products, find your domain under Domains, and choose DNS next to the domain name.

Either path gets you to the same place: the DNS management screen for your domain.

Step 3: check for an existing DMARC record

Once you’re in DNS management, look through the TXT records for one named _dmarc.

This check matters. GoDaddy has been adding default DMARC records to some new domains since April 2025, and DMARC only allows one policy record at _dmarc.yourdomain.com.

If you already see a TXT record named _dmarc, edit that record. Do not create a second one.

If you do not see a _dmarc TXT record, select Add New Record and choose TXT from the Type menu.

Step 4: add or edit the DMARC TXT record

Fill in these fields:

Field Value
Type TXT
Name / Host _dmarc
Value / TXT Value Your DMARC record (from Step 1)
TTL Leave as default

The Name field should be exactly _dmarc (with the underscore). GoDaddy will automatically append your domain, so it becomes _dmarc.yourdomain.com. Don’t add quotes around the Value unless GoDaddy’s interface specifically requires them, which it usually doesn’t. Don’t include the domain name in the Name field, just _dmarc.

GoDaddy’s TXT record help says the Value field must be ASCII and can be up to 1024 characters. A normal DMARC record fits comfortably within that limit. Paste the value as one line and avoid smart quotes or non-ASCII punctuation.

Example of what you’re entering:

Name:  _dmarc
Value: v=DMARC1; p=none; rua=mailto:[email protected];

Step 5: save the record

Click Save.

If your domain has GoDaddy Domain Protection enabled, GoDaddy may require identity verification before the DNS change is saved. After saving, you should see one TXT record named _dmarc.

Step 6: verify it works

GoDaddy says most DNS updates take effect within an hour but can take up to 48 hours globally.

To verify your DMARC record is live, go to DMARCTrust’s domain checker, enter your domain name, and check the DMARC section.

If you also enabled DNSSEC in GoDaddy or at another DNS host, verify the chain separately with the DNSSEC checker. A stale DS record or expired signature can make otherwise correct DMARC DNS fail for validating resolvers.

You should see your record displayed with a green checkmark. If it’s not showing up yet, wait an hour and try again.

Common mistakes to avoid

Mistake 1: wrong name format

The Name field should be _dmarc. Not _dmarc.yourdomain.com (GoDaddy adds the domain automatically). Not dmarc (missing the underscore). Not @._dmarc (no @ symbol needed).

Mistake 2: multiple DMARC records

You can only have one DMARC record per domain. If you already have a _dmarc TXT record, edit it instead of creating a new one. Multiple DMARC records cause receivers to ignore all of them.

Mistake 3: syntax errors in the value

DMARC records are picky about formatting. They must start with v=DMARC1; and semicolons separate each tag. There should be no spaces around the = signs, and the mailto: prefix is required for reporting addresses.

Use our DMARC generator to avoid syntax errors.

Mistake 4: editing DNS in the wrong place

If your domain is registered at GoDaddy but uses another provider’s nameservers, GoDaddy’s DNS screen is not authoritative. Check the domain’s nameservers first. If they point somewhere else, add or edit _dmarc at that DNS provider.

Mistake 5: forgetting to monitor

Adding a DMARC record without monitoring leaves the most useful part unused. Aggregate reports show which sources are sending as your domain, whether SPF or DKIM aligned, and what receivers did with failing mail. That is the data you need before changing policy from p=none to enforcement.

Frequently asked questions

How do I add a DMARC record in GoDaddy?

In GoDaddy DNS management, check whether a TXT record named _dmarc already exists. If it exists, edit it. If not, select Add New Record, choose TXT, enter _dmarc in the Name field, paste your DMARC value (for example, v=DMARC1; p=none; rua=mailto:[email protected];), keep the default TTL, and save. Verify the record propagated using a DMARC checker.

How long does it take for a DMARC record to work in GoDaddy?

GoDaddy DNS updates are usually visible within an hour. Full global propagation can take up to 48 hours, but reports typically start arriving within 24-48 hours.

Can I have more than one DMARC record on a GoDaddy domain?

No. A domain can only have one DMARC TXT record at _dmarc.yourdomain.com. If a record already exists, edit it instead of creating a new one. Multiple DMARC records cause receivers to ignore all of them.

Does GoDaddy set up DMARC automatically?

Sometimes. GoDaddy announced that, starting in April 2025, new domains purchased or transferred into GoDaddy receive a default DMARC record with p=quarantine. Existing domains may not have one, and any default record should still be reviewed so the policy, SPF/DKIM alignment, and reporting address match your email setup.

Should I use p=none or p=quarantine in GoDaddy?

If you are starting from scratch, use p=none to collect reports without requesting a delivery change. RFC 9989 says to analyze reports and remediate legitimate unaligned senders before enforcement. If GoDaddy already created a working p=quarantine record, do not weaken it automatically. Add reporting and verify every legitimate sender first.

Why monitoring matters

DMARC is the policy and reporting layer. Without monitoring, you might have a syntactically valid _dmarc TXT record but no reliable view of who is using your domain in the From: header.

This is why we built DMARCTrust.

When you add your domain to DMARCTrust, you get a unique reporting address to use in your DMARC record’s rua tag. Every aggregate report is parsed automatically so you can see sending sources, aligned SPF, aligned DKIM, DMARC pass/fail rates, and policy outcomes.

That reporting address is the bridge between the GoDaddy DNS record and the operational DMARC program. Instead of XML reports piling up in an inbox, they become a sender inventory and an enforcement plan.

Summary

You’ve now completed the setup. You created a DMARCTrust account and added your domain. You got your unique reporting address. You generated your DMARC record with that address. You added or updated the record in GoDaddy. And you verified it’s working with our domain checker.

Participating receivers often send the first reports within 24 to 48 hours. Review more than one normal sending cycle. Then fix every legitimate alignment failure before changing policy.

After GoDaddy: what’s next

Adding the DMARC record is step one. Here’s what comes after.

In the first couple of weeks, reports start arriving. Review them in DMARCTrust to identify all legitimate senders.

Over the next couple of weeks, fix any alignment issues. Make sure your email services (Microsoft 365, Google Workspace, marketing tools) are properly authenticated. If SPF still needs work in GoDaddy, use the SPF record guide to update the root-domain TXT record without creating duplicates.

When the data is clean, consider p=quarantine; t=y. The RFC 9989 t=y flag asks receivers to apply the next-lower policy while you test. Our enforcement playbook explains the sequence.

From month three onward, remove t=y for quarantine enforcement, then decide whether p=reject is appropriate for this domain.

Don’t rush this process. The goal is to protect your domain without blocking legitimate email. Monitoring makes that possible.

Check your domain now

Enter your domain in our free checker. You’ll immediately see whether your DMARC record is configured correctly.

For DMARC, the important checks are specific: exactly one _dmarc TXT record, a valid v=DMARC1 value, a deliberate policy, and a rua destination that someone actually monitors.

That’s why adding or editing a DMARC record and signing up for DMARCTrust belong together. When you create your account, you get a unique reporting address. That address goes in your DMARC record. Reports flow to our dashboard. You see everything.

GoDaddy gives you the DNS editor. DMARCTrust turns the _dmarc reporting address into source and alignment data.

Standards basis: DMARC setup advice based on RFC 9989 for policy records and RFC 9990 for aggregate report destinations.

Share this article

Read Next

View all posts
ESPs, subdomains, and the "can't get DKIM to align w/ DMARC" rabbit hole
dmarc-setup ·

ESPs, subdomains, and the "can't get DKIM to align w/ DMARC" rabbit hole

A recurring forum storyline: you set up an ESP, authentication tools say it's fine, yet DMARC alignment is still broken. This usually comes down to how the ESP signs DKIM (d=), whether you're using a custom sending domain, and whether you should isolate with a sending subdomain.

DT
DMARCTrust
5 min read
DMARC, SPF, DKIM... and the thing everyone misses: alignment
dmarc-setup ·

DMARC, SPF, DKIM... and the thing everyone misses: alignment

Forum threads keep repeating the same confusion: "SPF and DKIM pass, so why does DMARC fail?" The missing mental model is DMARC alignment. We explain aspf/adkim, organizational vs strict alignment, and why you likely rely on DKIM alignment more than you think.

DT
DMARCTrust
5 min read

Need expert help with email deliverability?

Hire an email deliverability consultant who has shipped billions of emails. Free assessment, hands-on engagement, written quote before any work starts.