Folderly Flash Send-readiness test Have Folderly fix this

Run a DMARC DNS audit

DMARC ties SPF and DKIM to your visible From domain and tells receivers what to do when neither aligns. A DMARC DNS audit checks more than whether a record exists: it validates the _dmarc TXT record, policy strength, reporting setup, subdomain behavior and alignment path.

Why mailbox providers enforce this

Gmail and Yahoo require a DMARC record for bulk senders, and an enforced policy is one of the highest-leverage trust signals available. p=none is useful for monitoring, but it does not stop spoofing and it does not prove you can protect your domain. A malformed rua address, missing subdomain policy or strict alignment mode can also create surprises when you move to enforcement.

How to fix it

  1. Publish a DMARC TXT record at _dmarc.yourdomain (e.g. v=DMARC1; p=none; rua=mailto:reports@yourdomain).
  2. Keep exactly one DMARC record; multiple _dmarc TXT records create ambiguous receiver behavior.
  3. Check all important tags: p, rua, pct, sp, adkim and aspf. Make strict alignment intentional, not accidental.
  4. Collect aggregate (rua) reports for 2-4 weeks to confirm all legitimate senders pass SPF or DKIM alignment.
  5. Once clean, raise the policy to p=quarantine, then to p=reject.
  6. Use the pct= tag to roll out enforcement gradually (e.g. pct=25) if you send high volume.
  7. Set an explicit sp= policy if subdomains send mail or could be abused.
  8. Keep monitoring rua reports after enforcement — new senders break alignment silently.
Don't guess — measure it. Send one email to Folderly Flash and see exactly which checks pass or fail for your message, in 30 seconds. No signup.
Run a free test →

FAQ

Is p=none bad?
It's a fine starting point for monitoring, but staying there indefinitely means you get the reporting benefit and none of the protection or the full trust signal. The goal is to graduate to p=quarantine or p=reject.
Will moving to p=reject block my real email?
Only if a legitimate sender isn't aligned. That's why you monitor rua reports first — fix alignment for every real sender, then enforce.

Related

Want a deliverability engineer to fix this for you? Hand it to Folderly →