Sender Integrity Logo

DMARC, SPF and DKIM explained

From technical records to controlled email domain protection

Written by Shyaam and Patrick

Published:

Last technically reviewed:

Why this matters

Email domains are used daily for communication, customer contact and supplier workflows. When unauthorized systems can send mail as if it came from your domain, trust and business risk increase quickly.

DMARC, SPF and DKIM help structure that risk. Not as isolated DNS records, but as controls that show which senders are legitimate and how receiving systems should treat failures.

The business question behind DMARC

The technical question is how the records are configured. The business question is simpler: can your organization prove who is allowed to send email on behalf of your domain?

Without that visibility, monitoring often stays at p=none for too long while management assumes the domain is already protected. A mature setup makes your current position, residual risks and safe next steps visible.

Core concepts: DMARC, SPF and DKIM

  • SPF specifies which systems are allowed to send mail on behalf of a domain.
  • DKIM adds a cryptographic signature so receiving systems can verify that a message has not been altered unexpectedly in transit.
  • DMARC ties SPF and DKIM to the visible From domain and publishes policy and reporting instructions.

Alignment: how SPF and DKIM connect

DMARC does not only check whether SPF or DKIM passes technically. It also checks whether the authenticated domain aligns with the visible sender domain in the From header.

That closes the gap where a message can look technically valid while still presenting a different brand or domain to the recipient. Alignment is often the difference between monitoring and real protection.

DMARC policies: p=none, quarantine and reject

  • p=none means monitoring. Receivers get reporting instructions, but failing messages are not actively blocked.
  • p=quarantine asks receiving systems to treat failing messages as suspicious, for example by routing them to junk or quarantine.
  • p=reject asks receiving systems to refuse failing messages. It is the strongest form of domain protection, but it requires controlled preparation.

Reporting: rua and ruf

DMARC reporting helps you understand which sources send on your behalf and where authentication is failing.

Aggregate reporting through rua provides summarized XML data per receiver or sending source. Failure reporting through ruf can provide more detailed samples, depending on what receiving parties support and are willing to share.

DMARC controls: t, sp, np, adkim and aspf

  • t signals whether a published quarantine or reject policy is in testing mode. RFC 9989 introduced it as a replacement for part of the former pct functionality.
  • sp defines policy for subdomains when you want that to differ from the parent domain.
  • np defines policy for non-existent subdomains.
  • adkim defines how strict DKIM alignment should be.
  • aspf defines how strict SPF alignment should be.

Safe implementation

A safe route to enforcement starts with visibility into legitimate senders, visible validation issues and exceptions in existing mail flows.

Only when known senders align correctly is it safe to move from p=none toward quarantine or reject. That avoids disruption to legitimate messages while steadily increasing protection.

Limitations

DMARC does not stop all phishing. It mainly protects against unauthorized use of your domain in the visible sender address.

It also does not guarantee deliverability. Good alignment and sender consistency help, but receiving parties still apply their own reputation and filtering logic.

What a mature DMARC setup looks like

  • Legitimate senders are known and reviewed over time.
  • SPF, DKIM and alignment work consistently across relevant mail flows.
  • DMARC reporting is used to spot new risks and configuration drift.
  • Management understands what p=none, quarantine and reject mean for risk and governance.
  • Changes in vendors or email routes are assessed before the domain drifts back into silent exposure.

Full DMARC FAQ

DMARC tag explanations

These are the DMARC tags most commonly reviewed in DNS.

TagMeaning
vVersion tag. For DMARC this should be DMARC1.
pPrimary policy for failing messages: none, quarantine or reject.
ruaDestination for aggregate reporting.
rufDestination for failure or forensic reporting.
spPolicy for subdomains.
adkimDefines how strict DKIM alignment should be.
aspfDefines how strict SPF alignment should be.
tSignals testing mode for a quarantine or reject policy; replaces part of the former pct functionality.
npPolicy for non-existent subdomains.
psdIndicates whether the record is published for a Public Suffix Domain.
foRequested options for generating failure reports when ruf is present.
What is a DMARC record lookup tool?

A DMARC lookup tool reads the DNS TXT record for _dmarc.yourdomain to show policy, reporting settings and visible syntax or configuration issues.

Why check your DMARC record?

Regular checks show whether the record is published, whether reporting works and whether your domain is still only monitored or actually moving toward enforcement.

Why are DMARC reports important?

They help show which sources send on your behalf, which sources fail authentication and where configuration or governance needs to be tightened.

What does DMARC compliant mean?

A message is DMARC compliant when SPF or DKIM passes and the authenticated domain aligns with the visible From domain according to the published policy.

How does DMARC work?

DMARC builds on SPF and DKIM by checking alignment, publishing policy and telling receiving systems how to treat failing messages.

What does domain alignment mean?

Alignment means the visible sender domain matches, or under relaxed mode shares the organizational domain of, the domain authenticated by SPF or DKIM.

How does DMARC work with subdomains?

Subdomains normally inherit the parent-domain policy unless you publish a separate sp= setting or their own _dmarc record.

Can you use DMARC without DKIM?

Yes, but then you depend entirely on SPF alignment. In practice, mature implementations use SPF and DKIM together for broader protection and more stable validation.

Authoritative technical references

This guide was reviewed against the current IETF specifications for DMARC, aggregate and failure reporting, SPF and DKIM.

Read what RFC 9989 changed in the DMARC standard

Email trust is not a one-time setting.

Your organization changes. Vendors change. Email flows change.

Sender Integrity helps you keep control over who is allowed to send email on your behalf, so your domain does not quietly drift back into risk.

Start with visibility. Move toward enforcement. Keep control over time.

Understand, implement and manage DMARC

Managed DMARC

Managed DMARC and DMARC-as-a-Service with active RHEVOX analysis and follow-up. We operate the platform and turn available reporting into findings, advice and clear next steps.

DMARC monitoring

Understand DMARC reports and observed sending sources. RHEVOX Sender Integrity Managed combines monitoring with analysis, advice and follow-up.

DMARC implementation

Validate legitimate senders, remediate authentication issues and build an informed route to DMARC enforcement.