The Movement Athlete · Email Deliverability Fix

Fix the broken DMARC record

Our emails risk landing in spam because the domain publishes three conflicting DMARC records at once. This guide fixes it — a ~15-minute DNS change, no code. Follow it top to bottom.

Verified live 7 Jul 2026 · domain: themovementathlete.com · DNS host: SiteGround
The problem in one line

A domain is only allowed one DMARC record. Ours has three. When there's more than one, Gmail/Outlook ignore all of them — so we effectively have no policy, and the domain looks misconfigured, which pushes mail toward spam. The fix is to delete the extras and keep one clean record.

Before you start

Where the change is made: DNS is managed at SiteGround (not GoDaddy — the domain is registered at GoDaddy, but the nameservers point to SiteGround, so the records live there). You'll need SiteGround login access.

What "good" looks like at the end: exactly one DMARC record, set to safe "monitor" mode. We tighten it later, once we've confirmed our email is authenticating.

The steps

  1. Log in to SiteGround DNS

    Go to SiteGround → Site Tools for themovementathlete.com → Domain → DNS Zone Editor. (If the site isn't in this SiteGround account, whoever set up the hosting has the login.)

  2. Find the three DMARC records

    In the DNS Zone Editor, filter or scroll to the TXT records. Look for the ones whose Name/Host is _dmarc. You'll see three of them:

    DELETE v=DMARC1; p=none;
    DELETE v=DMARC1; p=reject; sp=none; rua=mailto:re+ee9a19c7ab05@inbound.dmarcdigests.com; pct=100
    KEEP & EDIT v=DMARC1; p=reject; pct=100; rua=mailto:re+ee9a19c7ab05@inbound.dmarcdigests.com; sp=none;

    The two DELETE ones are: the bare p=none record, and one of the two near-duplicate p=reject records. Keep just one to edit in the next step — it doesn't matter which of the two reject ones you keep, they're duplicates.

  3. Delete two of them

    Delete the two marked DELETE above (there's a trash/delete icon on each row). You should be left with one _dmarc TXT record.

  4. Edit the one remaining record to monitor mode

    Open the record you kept and replace its value with exactly this:

    v=DMARC1; p=none; rua=mailto:re+ee9a19c7ab05@inbound.dmarcdigests.com; pct=100

    Why p=none? It means "watch and report, don't block anything yet." This is the safe setting — it can't accidentally bounce real emails. Reports keep flowing to our existing dmarcdigests account so we can see what's passing. Save the record.

  5. Wait, then confirm there's only one

    DNS takes ~30–60 minutes to update. Then confirm the fix — either paste this into a terminal:

    dig +short TXT _dmarc.themovementathlete.com

    …it should return one single line (not three). Or use a free checker like dmarcian.com/dmarc-inspector or mxtoolbox.com/dmarc.aspx — enter the domain, it should show one valid record. Or just tell Claude it's done and it'll re-check the DNS instantly.

  6. Later: tighten the policy (2–3 weeks after)

    Leave it on p=none for 1–2 weeks and check the dmarcdigests reports. Once ActiveCampaign, SendGrid and Google all show as passing, change p=nonep=quarantine, and a couple of weeks later → p=reject. Don't skip straight to reject — that can bounce legitimate mail before we've confirmed everything aligns.

✅ That's it

Once there's one clean record on p=none, the immediate misconfiguration is gone and inbox trust starts recovering. The step-6 tightening is the finishing move, not urgent.

How we'll know it's actually working