Cybersecurity & Email Security

A plain-English guide to SPF, DKIM and DMARC

Understand the three email authentication controls, what each does and how to approach implementation safely.

Published 2 min read

The practical takeaway

Your company domain is part of your identity. Attackers may try to send messages that appear to come from it. SPF, DKIM and DMARC are DNS-based controls that help receiving systems evaluate whether email is authorised. They are important, but they do not eliminate every type of phishing.

  1. SPF
  2. DKIM
  3. DMARC
  4. Review reports
How the three controls build on each other

SPF: which systems may send email for your domain?

Sender Policy Framework (SPF) publishes the sending infrastructure authorised for a domain. Receiving systems can check whether the server is permitted to send using the relevant envelope domain.

A common problem is forgetting legitimate services such as marketing, booking or invoicing tools. An incomplete SPF setup can affect genuine mail.

DKIM: was the message signed by an authorised domain?

DomainKeys Identified Mail (DKIM) uses a cryptographic signature added by a sending system. A recipient can verify that signature using a public key published in DNS.

DKIM helps establish authenticity and integrity for signed content; it does not prove that the sender is trustworthy.

DMARC: what should happen when authentication does not align?

Domain-based Message Authentication, Reporting and Conformance (DMARC) checks alignment with the visible From domain using SPF or DKIM results. Policies can request monitoring (none), quarantine or rejection of messages that fail.

Reports can help identify legitimate senders and potential misuse. A stricter policy should follow an inventory and testing process rather than being enabled blindly.

Why all three work together

SPF identifies authorised sending infrastructure; DKIM validates signatures; DMARC connects authentication to the visible From domain and communicates a handling policy.

Even a correctly configured domain still needs user awareness, account security, anti-phishing protections and incident procedures.

A safe rollout approach

  1. Inventory every legitimate sender and service.
  2. Check current DNS and authentication results.
  3. Enable and verify DKIM wherever supported.
  4. Publish a DMARC monitoring policy and review reports.
  5. Fix legitimate sending and alignment issues.
  6. Move towards stronger enforcement when evidence supports it.

Changes should be tested and scheduled carefully, especially where email is business-critical.

Practical checklist

  • Identify all services that send on behalf of the domain.
  • Check SPF record accuracy and DNS lookup limitations.
  • Verify DKIM signing and selectors for each provider.
  • Confirm DMARC alignment, reporting and policy.
  • Test important transactional emails before tightening enforcement.
  • Review phishing resilience beyond domain authentication.

Frequently asked questions

Does DMARC stop all phishing?

No. It reduces some forms of direct domain impersonation, but attackers can use lookalike domains, compromised accounts and other methods.

Can I immediately set DMARC to reject?

Only after confirming legitimate senders and alignment; otherwise valid messages may fail.

Is a DNS check enough for a complete security assessment?

No. Public DNS findings are a useful starting point, not a substitute for reviewing the wider email and identity environment.

How Nexa Point can help

Nexa Point can discuss a scoped Business Email Security Review, including publicly observable domain authentication settings and recommendations for further investigation where appropriate.

Sources and further reading

This guide is general information, not a substitute for a tailored technical, legal or regulatory assessment.