Warning

Your DMARC policy only monitors (p=none)

The short version

Move to p=quarantine, then p=reject, once reports show your mail passes.

What it means

Your DMARC record has the policy p=none. Receivers send you reports, but they deliver mail that fails DMARC as if the record weren't there. It is the right first step, meant to last weeks, not years.

Why it matters

With p=none, forged mail in your name still reaches inboxes. Many domains stay on it because nobody reads the reports, so the protection DMARC was set up for never switches on. Mailbox providers also give a little more trust to domains that enforce their policy.

How to fix it

  1. Read your aggregate reports, or feed them into a report service, and list every source that sends as your domain.
  2. Fix SPF or DKIM for any real sender that fails.
  3. Change the policy to p=quarantine. You can phase it in with pct=25, then raise it to 100.
  4. After a few weeks without surprises, change to p=reject. The DMARC builder shows the record for each stage.

Cloudflare

Open the domain, go to DNS then Records, and add or edit a TXT record with the name _dmarc. Cloudflare's own DMARC management page can write the record too.

Other DNS hosts

Add a TXT record whose name (host) is _dmarc. Some hosts want the full name, _dmarc.example.com; others add your domain for you, so type only _dmarc.

Check it worked

Run the DMARC checker or the full email check. DMARC records are read fresh once the old record's TTL has passed, usually within an hour. The DMARC section should show the new policy and the finding should be gone. The policy should read quarantine or reject.