Why might my unauthenticated Mailchimp campaigns be quarantined on GoDaddy domains already?

Because GoDaddy ships a default DMARC record on domains purchased or transferred in since April 2025, set to p=quarantine with reports sent to GoDaddy. An enforcing DMARC policy plus an unauthenticated sender equals quarantine or rejection at receivers that honour the policy — meaning your own registrar-issued record may already be acting on your Mailchimp campaigns before you have changed anything. Authenticating the domain is the fix; deleting the DMARC record is not, because it removes the protection and the receiving-side benefits entirely.

Mailchimp tells me to create a DMARC record, but one already exists at GoDaddy. What do I do?

Edit, never add. Two DMARC records at one name cause receivers to apply no DMARC policy at all. Keep exactly one deliberate record: set its policy knowingly, and make sure its rua report address reaches you — GoDaddy's shipped default reports to GoDaddy, so change that address to your own. Before starting Mailchimp's flow, copy the current _dmarc value somewhere safe (a snapshot), and after the flow completes, read the record back to confirm the single record present is the one you intend.

Does Mailchimp's automatic setup work with GoDaddy?

Mailchimp's setup article links GoDaddy's CNAME help in its provider resources, and Entri — the service behind Mailchimp's automatic method — supports GoDaddy (the two companies announced a Domain Connect integration in 2025). Mailchimp does not publish its own list of supported automatic-setup providers, so if the automatic path is offered for your GoDaddy domain in-account, it is genuine; the manual path remains fully documented either way. Whichever path you take, run the snapshot and read-back steps in this guide, because neither vendor documents what the automatic path does to a pre-existing DMARC record.

Mailchimp · GoDaddy · Authentication

Mailchimp emails going to spam — with DNS on GoDaddy, start one step earlier

First published 20 October 2026 · Mailchimp's flow follows our Cloudflare edition (same verified research); everything GoDaddy below was checked against GoDaddy's and Mailchimp's current documentation for this guide.

RUNG 0 Your registrar may already enforce DMARC against your campaigns

Domains that arrived at GoDaddy after April 2025 can carry GoDaddy's default DMARC — p=quarantine, reports to GoDaddy. An enforcing policy + unauthenticated Mailchimp = your campaigns quarantined by a record you never wrote. Authentication is still the fix. Deleting the record is not.

3 official guides, 1 record nameThe only safe verb: EDIT

The fast answer

Snapshot first: copy your current _dmarc TXT value somewhere safe (screenshot the GoDaddy DNS list). You will read it back at the end; neither vendor documents what setup tools do to a pre-existing record, so the snapshot is your insurance.
From address check: campaigns must send from your own domain — free webmail From addresses cannot be authenticated.
Mailchimp: profile icon → Account & billing → Domains → Start authentication → automatic (Entri) or manual. (Entri does support GoDaddy — the companies announced a Domain Connect integration in 2025 — though Mailchimp publishes no provider list of its own.)
Manual records at GoDaddy: the two CNAMEs Mailchimp shows (Name relative — GoDaddy appends your domain; TTL 1 hour default) and DMARC handled per the collision rule below.
The collision rule: DMARC = edit the one existing record, set the policy deliberately, point rua at an address you read. Never a second record.
Verify both ways: Mailchimp shows Authenticated, the _dmarc readback shows your single intended record, and a real campaign's headers show dkim=pass with your domain and dmarc=pass.

Why the DMARC step is different here (read before touching it)

Three official texts converge on your _dmarc name: GoDaddy ships a default record there; GoDaddy's own hosting walkthrough teaches that record as an add, with no existing-record check; and Mailchimp's flow says create a DMARC record. Follow any of them literally on a post-April-2025 GoDaddy domain and you can end with two DMARC records — which receivers treat as no DMARC at all. The safe sequence is the fast answer's: snapshot → one record → deliberate policy → your own report address → read back. Two more GoDaddy-specific cautions:

Type the DMARC value yourself. GoDaddy's help renders its default value without the required mailto: prefix that the live record actually carries. Copying the printed help text republishes a broken report address.
Don't delete _dmarc to “start clean.” On a default-GoDaddy domain you'd be removing an enforcement policy mid-incident and losing the receiving-side trust it confers. Editing achieves everything deletion promises, without the gap.

The CNAMEs at GoDaddy — fields and the local friction

Item	What to expect
Fields	Type CNAME; Name = Mailchimp's displayed name, relative; Value/Points to = Mailchimp's displayed target; TTL 1 hour (GoDaddy default).
The doubling trap	GoDaddy appends your domain to the Name. Type the full `name.yourdomain` and the record lands at `name.yourdomain.yourdomain` — Mailchimp's own troubleshooting describes this exact corpse. Read back after saving.
“Let's double-check…” pop-up	GoDaddy shows a save-confirmation modal for DNS edits; owners routinely misread it as an error. It's a confirmation. Confirm, then read back.
Name already occupied	GoDaddy forbids a CNAME where another record sits at the same name. The usual occupant at Mailchimp's names is a previous Mailchimp attempt's leftover — edit it to the current values rather than adding beside it. (GoDaddy's own hosting DKIM and Microsoft 365's selectors live at different names and coexist fine.)
No proxy here	Cloudflare habits don't transfer: GoDaddy has no proxy/flattening layer on these records. Name accuracy and singleness are the whole game.

The stale-guide trap is armed on GoDaddy

Current “Mailchimp + GoDaddy” tutorials still teach the retired SPF step (include:servers.mcsv.net). Two facts retire it everywhere — Mailchimp's current flow has no SPF step, and campaign envelope senders are Mailchimp domains, so the SPF leg cannot align regardless (full explanation in the Cloudflare edition). On GoDaddy it's worse than useless: GoDaddy's editor silently saves duplicate SPF records, so “add this for Mailchimp” on top of GoDaddy-product SPF residue (—secureserver.net, which governs your domain's own mail, not campaigns—) manufactures a duplicate-SPF PermError for mail that was previously fine. Pattern to remember: any Mailchimp instruction that begins with your SPF record describes a retired product.

Still in spam after “Authenticated”?

Same honest ladder as every Mailchimp setup, because the remaining causes are the same: list provenance first, the unengaged second, sending-pattern spikes third, and no — a dedicated IP is not the answer at small-business volumes (Mailchimp's own FAQ puts the sensible threshold around 100k emails a week, and says most senders do better shared). If it worked before GoDaddy's default arrived and broke after, re-check Rung 0: ensure the single surviving DMARC record is yours, deliberate, and reporting to you.

FAQ

GoDaddy's default DMARC — should I just leave it as my record?

Its policy (quarantine) is a legitimate end-state for a domain whose senders are all authenticated, but its report address sends your telemetry to GoDaddy. Keep the name, change the address, and set the policy by your own rollout logic — the record must be yours, not merely present.

Automatic setup finished. How do I know it didn't change my DMARC?

Compare the readback to your snapshot. If the record differs (one consultancy has reported the automatic path replacing a policy with p=none — unconfirmed by either vendor, which is exactly why the snapshot exists), restore your deliberate single record by editing, and confirm the final state by lookup.

My domain came from GoDaddy years ago. Does the default apply to me?

The documented default covers purchases/transfers since April 2025. Older domains vary — which is why this guide starts with looking, not assuming: whatever sits at _dmarc today is your starting fact.

Sources

Mailchimp Help — domain authentication (as verified for Article #15), provider resources naming GoDaddy's CNAME help · GoDaddy Help — CNAME records, DNS editing behaviour, default DMARC announcement (April 2025), hosting-email walkthrough · Entri/GoDaddy Domain Connect integration announcement (Business Wire, June 2025) · SendGrid and Flodesk support documentation on GoDaddy name-appending (independent ESP corroboration).

Verification note: the Entri–GoDaddy relationship and the DMARC collision were confirmed from the sources above on 20 October 2026. Whether Mailchimp's in-account flow detects or preserves an existing DMARC record is documented by neither vendor; this guide's snapshot-and-readback procedure is designed to be safe under every version of that unknown — and says so, rather than guessing.

Did this fix work for you?

Your reaction tells us whether this guide solved the problem it promised to solve.