·6 min read
ByGabriel CA·Kraftwire Software

Email Security Audit for DMARC Compliance: Sending Sources, Reports and Enforcement

Illustration for Email Security Audit for DMARC Compliance: Sending Sources, Reports and Enforcement

DMARC helps protect a domain from direct email spoofing. It links the sender address readers see to the domain used by SPF or DKIM. A valid record, clear policy and regular report review are key parts of that protection.1, 2

How domain alignment works

The From header holds the sender address shown in mail apps. The MAIL FROM address is used between mail servers. These addresses can use different domains, so SPF alone does not require them to align.2

The visible sender address is also called 5322.From. DMARC checks alignment between its domain and the domain used by SPF or DKIM.2

For SPF to count towards DMARC, the sending source must be authorised for the MAIL FROM domain. That domain must also align with the domain in the visible From address.2

DKIM signs mail using a domain named in the d= tag. The receiver gets a public key from DNS to verify the signature.3

For DKIM to count towards DMARC, that signing domain must align with the From domain. The receiver uses the s= selector to validate the signature.2

A message passes DMARC if either SPF or DKIM passes with alignment. Both can pass, but DMARC does not require both. It fails when neither check passes with alignment.2

Sending source and DNS checklist

Start by listing every system and service that sends mail for your domain. Include third-party services, not just the mail systems your team runs.4

Check that the SPF record includes all authorised sending IP addresses. Publish the DKIM public keys needed to verify signed mail.4

DKIM record tools can check records and help confirm that mail uses digital signatures. They can also generate and analyse DKIM records.5

DNS record tools can validate SPF, DKIM and DMARC records. They can flag errors that weaken email security.5

A DMARC lookup shows whether the record exists and flags problems with it. Reports add detail about legitimate senders, unauthorised senders and reasons for failure.5

Reading DMARC reports

Aggregate reports give periodic summaries of DMARC passes and failures. Failure reports give details of failed messages, often soon after the failure.2

A failure report can include redacted headers, body extracts and the source IP address. It can also contain sender and recipient addresses and the subject line. This message detail raises privacy concerns.6

Aggregate reports show who sends mail using your domain and where alignment fails. They can reveal a marketing platform, printer, cloud service or old app unknown to the security team.3

Review known senders that fail SPF or DKIM and fix their setup. Unknown IP addresses claiming to use your domain may be spoofing or untracked services.6

A rua address alone is not enough to manage reports. Assign an owner, set retention rules and use a common format for the data. Define how newly seen sending sources will be raised for review.3

Treat report data as untrusted input. A parser must not execute supplied values or fetch arbitrary linked resources. Do not pass raw report content into tools with broad rights without controls.3

Moving from monitoring to enforcement

A policy of p=none does not enforce DMARC. It does not ask receivers to block mail that fails, leaving the domain open to spoofing.4

Start with monitoring before moving to p=quarantine or p=reject. This reduces the risk of blocking legitimate mail.1

Use p=quarantine to observe how a stricter policy affects delivery. This stage helps reduce the risk of blocking legitimate messages by mistake.4

Set rua for aggregate reports and ruf for failure reports. Move gradually towards p=reject. Tell IT, security and teams that send email about the change.4

Look for a rising pass rate before tightening the policy. Review legitimate senders that fail a check and fix their setup.6

Keep SPF, DKIM and DMARC records current when you add vendors, cloud services or sending tools. New services can leave gaps if these records are not updated.1

Review email security policies regularly and update them as threats change. Security measures need to match the threats your organisation faces.4

What DMARC does not protect

DMARC limits direct spoofing of your domain. It does not block look-alike domains, display-name abuse or compromised accounts. Phishing can still come from a domain that passes its email checks.3

Passing SPF, DKIM and DMARC does not prove who a person is. It does not prove a message is true or a link is safe.3

Keep domain checks separate from mailbox security and protection for readers. An audit also needs to treat security during mail transport as a distinct concern.3

Sender rules and data protection

DMARC is a supporting control for email security practices aligned with PCI-DSS. It helps reduce the risk of impersonation in regulated mail.1

Failure to prevent spoofing could contribute to breaches of GDPR or HIPAA duties. Such breaches may lead to fines or legal consequences.4

Google and Yahoo have introduced stricter checks for domains that send large volumes of mail. Those senders need a valid DMARC record and mail that passes DMARC.1

Mailbox providers place more weight on mail that passes sender checks. DMARC compliance can help inbox placement and reduce the risk of filtering or rejection.1

Current DMARC standards

RFC 9989 is the core DMARC Proposed Standard. It replaced RFC 7489 and RFC 9091. Reporting is now split into RFC 9990 for aggregate reports and RFC 9991 for failure reports.3

An audit based only on older guidance may accept items whose status has changed. Some items were removed from the new standard.3

Email security checks with SimplyScan

SimplyScan grades eight areas in one scan, including email security. Its email security checks cover SPF, DKIM and DMARC. SimplyScan runs scans in 30 seconds.

SimplyScan offers 61 free standalone tools. Free scans require a free account.

SimplyScan's check_email_security tool checks SPF, DKIM and DMARC. It checks whether the domain is spoofable.7

SimplyScan's MCP server exposes check_email_security for use by connected tools. It also exposes tools for website scans, security headers and local code.

You can connect SimplyScan as a remote MCP server in Claude, Cursor, Windsurf or another supported client. Use https://api.simplyscan.io/mcp as the endpoint. Sign in and create a free account API key in Settings to connect.7

Sources

  1. mimecast.com › dmarc-compliance
  2. learn.microsoft.com › email-authentication-dmarc-configure
  3. 4crypto.eu › email-security-audit-dmarc
  4. sbscyber.com › implementing-a-dmarc-policy-to-prevent-email-spoofing
  5. easydmarc.com › dmarc-lookup
  6. duocircle.com › how-to-read-dmarc-reports-and-analyze-email-authentication-…
  7. simplyscan.io › mcp

Frequently asked questions

No. DMARC limits direct spoofing of your domain, but not look-alike domains, display-name abuse or compromised accounts. A phishing message can still come from a domain that passes email checks.
RFC 9989 is the core DMARC Proposed Standard and replaced RFC 7489 and RFC 9091. RFC 9990 covers aggregate reports, while RFC 9991 covers failure reports.

Is your app secure? Run a free security scan in 30 seconds · free account required.

Scan your app free →