Skip to content
YHP DMARC

Understanding DMARC

Life after p=reject

Reaching reject is not the end. What to keep watching, and what you can add next.

Reaching p=reject means receivers refuse mail that fakes your domain. It is a milestone, not the end of the work.

Keep watching reports

New services get added: a new CRM, a marketing tool, a supplier sending invoices on your behalf. If nobody sets up SPF or DKIM for them, their mail is now rejected. Alerts for new failing sources and compliance drops catch this early.

Watch for DNS changes

A DNS migration or a well-meaning edit can remove your DMARC or SPF record, or push SPF over its lookup limit. Monitoring your records, not just your reports, catches this before mail bounces.

Protect domains that never send

Parked and redirect-only domains can be spoofed too. Give them:

v=spf1 -all
v=DMARC1; p=reject

and a null MX if they receive no mail.

Add the next layers

  • MTA-STS and TLS-RPT ensure mail to you is delivered encrypted.
  • BIMI shows your logo in supporting inboxes, now that you enforce DMARC.
  • Key rotation. Rotate DKIM keys periodically and remove keys for services you stopped using.

See it on your own domain.

Check your DMARC, SPF and DKIM setup in seconds, then let us watch your reports for you.

Start free