DMARC Record Generator

Built for operators & agencies
Live DNS - no cached APIs
No login required
No data retention
Privacy first diagnostics
Prevents blacklisting - not causes it

Choose policy and optional reporting addresses.

Important: DMARC only passes when SPF or DKIM aligns with the visible From domain. “Valid DMARC” can still fail and silently suppress inboxing.

Use pct only during rollout. Keep it at 100 once stable.

Tip: After publishing DMARC, always validate alignment (SPF/DKIM + DMARC) using /check.

What the DMARC Generator does

DMARC tells mailbox providers what to do when SPF and DKIM checks fail, and it gives you reporting so you can see who is sending on behalf of your domain. If you get DMARC wrong, you can break legit mail or leave your domain wide open to spoofing.

This DMARC generator helps you build a clean _dmarc TXT record with a safe policy, correct tags, and a sane rollout plan.

Fast workflow (recommended):

  1. Run a full SPF, DKIM and DMARC check together
  2. Apply FixKit recovery blueprint if anything fails
  3. Enable Monitoring so changes never blindside you again

When you should use this

  • You want to stop spoofing and protect your brand.
  • Gmail or Microsoft warnings mention unauthenticated email or domain spoofing risk.
  • Your emails sometimes pass SPF or DKIM but DMARC still fails because alignment is wrong.
  • You want DMARC reports to see unknown senders and fix configuration safely.

How to use it

  1. Choose a starting policy. If you’re unsure, start with p=none to collect reports without blocking.
  2. Set report addresses (rua, optional ruf) that you actually monitor.
  3. Generate the record and publish it in DNS as a TXT record at _dmarc.yourdomain.com.
  4. Validate it using the InboxGreen checker.
  5. Once you see legitimate traffic is aligned, move to p=quarantine, then p=reject.

Common mistakes

  • Jumping straight to p=reject: missing emails / support tickets; fix is rollout via p=none first.
  • Wrong DMARC hostname: publish at _dmarc (not root).
  • Bad reporting address: typos or mailbox rejects; use a monitored mailbox.
  • Alignment confusion: dmarc=fail while spf=pass; SPF passed for another domain.
  • Multiple DMARC records: duplicates at _dmarc cause unpredictable behavior.

FAQ

What DMARC policy should I start with?

Start with p=none if you don’t have full certainty over all senders. It gives visibility without breaking mail. Move to enforcement only after you’ve fixed alignment for legit streams.

Why does DMARC fail even if SPF passes?

Because DMARC needs alignment. SPF can pass for the return-path domain while the visible From domain is different. Use the email header analyzer to inspect Authentication-Results and confirm alignment.

Do I need both SPF and DKIM for DMARC?

No. DMARC passes if either SPF aligns or DKIM aligns. In practice, you want both configured correctly for resilience.

How long does it take for DMARC changes to apply?

Depends on DNS TTL and caching. Sometimes minutes, sometimes hours. After publishing, validate using /check.

What to do next

After publishing your DMARC record, run a full scan with the InboxGreen checker. If SPF is not solid yet, generate a clean SPF record using the SPF generator.