PCI DSS 4.0 and email: SPF, DKIM and DMARC checklist

PCI DSS 4.0 requirement 5.4.1 asks for automated protection against phishing, and its guidance names SPF, DKIM and DMARC. Check your domain.

Applies to
Every organisation that stores, processes or transmits payment card data.
In force
Requirement 5.4.1 is mandatory since 31 March 2025.

Check your domain against this list

We only read public DNS records. The domains you check are not stored.

The email checklist

  1. SPF record Req. 5.4.1

    Lists the servers that may send as your domain, so receivers can spot forged mail.

    Our check verifies this. How to set it up

  2. DKIM signing Req. 5.4.1

    Signs your mail so receivers can verify it came from you and was not changed.

    Our check verifies this. How to set it up

  3. DMARC policy that blocks spoofing Req. 5.4.1

    A policy of quarantine or reject tells receivers to stop mail that fakes your domain. p=none only monitors, so it does not protect anyone.

    Our check verifies this. How to set it up

  4. Subdomains protected Recommended Req. 5.4.1

    Without an enforced subdomain policy, attackers can use invoices.yourdomain.com instead.

    Our check verifies this. How to set it up

  5. DMARC reports received and reviewed Req. 5.4.1

    Aggregate reports show who sends as your domain and whether spoofing is blocked.

    Our check verifies this. How to set it up

  6. Phishing filter for incoming mail Req. 5.4.1

    Your mail provider should check SPF, DKIM and DMARC on incoming mail and scan links and attachments. This is a setting of your mail system, not of your DNS.

    Not visible from outside: check it yourself.

  7. Staff trained to recognise phishing Req. 12.6.3.1

    Security awareness training has to cover phishing and social engineering.

    Not visible from outside: check it yourself.

  8. Evidence for your assessor

    Keep proof that the controls are in place and working, such as your DMARC policy history and pass rates.

    Not visible from outside: check it yourself.

What PCI DSS asks

Requirement 5.4.1 of PCI DSS 4.0 (and 4.0.1) asks for processes and automated mechanisms that detect phishing attacks and protect your staff against them. It was a best practice until 31 March 2025 and has been mandatory since.

The standard doesn't order you to publish DMARC. Its guidance for 5.4.1 does name anti-spoofing controls such as SPF, DKIM and DMARC as examples, next to link scanning and malware filtering. In practice, an enforced DMARC policy is the usual way to show that nobody can send phishing mail in your name, and assessors ask about it.

Why p=none is not enough

With p=none receivers only report on mail that fails DMARC; they still deliver it. That is fine as a first step, but it doesn't stop anyone from sending a fake invoice from your domain. Move to quarantine or, better, reject once all your real mail passes. How to get there without blocking your own mail.

What to show your assessor

  • Your published SPF, DKIM and DMARC records, and since when the DMARC policy has been enforced.
  • That someone receives and reviews the DMARC reports, and acts on what they show.
  • Your inbound mail filtering settings, and records of phishing awareness training (requirement 12.6.3.1).

MailWatch keeps the history of your DNS records and DMARC results, and turns it into an evidence PDF you can hand over.

Check it, then keep it that way

A record that is right today can break tomorrow: a new tool gets connected, a DNS migration drops a line, a provider rotates its keys. Check your domain now, and let MailWatch check it every day, so you hear about problems before a receiver or an auditor does.

This checklist covers email only, in our own words. It is not legal advice and not a full list of what the rules ask.