SECURITY LIBRARY

SPF, DKIM and DMARC

Understand how public email authentication records reduce unauthorized use of a domain.

SPF identifies permitted senders, DKIM signs messages and DMARC tells receivers how to handle alignment failures while providing reporting. The three controls work together and must reflect every legitimate sender.

01

Why it matters

SPF identifies permitted senders, DKIM signs messages and DMARC tells receivers how to handle alignment failures while providing reporting. The three controls work together and must reflect every legitimate sender.

02

What to review

  • List marketing, support, billing and transactional mail providers before changing records.
  • Keep SPF within lookup limits and avoid authorizing broader provider ranges than needed.
  • Roll out DMARC with reporting and measured enforcement so legitimate mail is not silently disrupted.
03

How to interpret the result

Public records show declared policy, not whether every message is signed correctly. Validate real mail flows and review aggregate reports with the mail administrator.

04

A safe remediation workflow

Confirm the asset owner and change authority first. Apply the change in small, recoverable steps, test service functionality and repeat the check against the same public endpoint. Preserve the evidence and decision rationale when closing the finding.

SCANMYHOST / NEXT STEP

Turn the observation into a decision.

Review the illustrative report first, then define the domains and hosts you are authorized to assess in your workspace.