Compliance
What the rules ask of your email
Mailbox providers, card schemes and EU law all ask for the same basics: SPF, DKIM and DMARC. Pick the rules that apply to you, see the checklist and check your domain against it. Free, no account needed.
- Gmail and Yahoo Gmail and Yahoo bulk sender requirements: checklist Since February 2024, Gmail and Yahoo require SPF, DKIM, DMARC and one-click unsubscribe from bulk senders. Check your domain against every rule. Everyone sending to Gmail and Yahoo addresses; stricter rules from about 5,000 messages a day.
- Outlook.com Outlook.com sender requirements (May 2025): checklist Since May 2025, Outlook.com rejects mail from high-volume senders without SPF, DKIM and DMARC. Check your domain against Microsoft's rules. Domains sending more than 5,000 messages a day to Outlook.com, Hotmail and Live addresses.
- PCI DSS 4.0 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. Every organisation that stores, processes or transmits payment card data.
- NIS2 NIS2 email security checklist NIS2 asks for cyber hygiene, secured communications and encryption. For email that means SPF, DKIM, an enforced DMARC policy and encrypted delivery. Essential and important entities in the EU, in sectors from energy and health to digital services and manufacturing.
One setup covers all of them
The lists overlap. Gmail, Yahoo and Outlook.com want SPF, DKIM and a DMARC record so they can trust your mail. PCI DSS and NIS2 go a step further: they want protection against phishing, which in practice means a DMARC policy that makes receivers refuse mail that fakes your domain.
The safe route is the same for everyone: publish DMARC with p=none, read the reports until every service
that sends for you passes, then move to p=reject.
How to move to reject safely.