Email security guides
Step-by-step guides to setting up SPF, DKIM and DMARC against current standards. Every claim is linked to its source.
From RFC 7489 to RFC 9989: what to change in your DMARC record
RFC 9989 (May 2026) is the new DMARC standard and obsoletes RFC 7489. If your record has
ri,rforpct=100, delete them; if you are testing withpct=0, keep it and addt=ynext to it. Close off non-existent subdomains withnp.DMARC from
p=nonetop=reject, step by stepp=nonemonitors but does not protect: forged mail is still delivered. RFC 9989 §5.1 describes confirming every legitimate sender with reports, then moving toquarantineandreject; you can test each step one level lower withpct=0; t=y.The SPF 10 DNS lookup limit: why it is exceeded and how to fix it
Under RFC 7208 an SPF evaluation may involve at most 10 terms that cause DNS lookups; beyond that the result is
permerrorand SPF does not work at all.include,a,mx,ptr,existsandredirectcount;ip4,ip6andalldo not.Setting up SPF, DKIM and DMARC for Microsoft 365
Microsoft 365 does not DKIM-sign mail from your custom domain by default: you need to publish two CNAME records and turn signing on. For SPF a single
include:spf.protection.outlook.comis enough; take DMARC fromp=nonetorejectin stages.Setting up SPF, DKIM and DMARC for Google Workspace
In Google Workspace a single
include:_spf.google.comis enough for SPF. You generate the DKIM key in the Admin console, publish it as agoogle._domainkeyTXT record and then start authentication. Turn DMARC on withp=noneat least 48 hours later.Gmail, Yahoo and Outlook bulk sender requirements
Anyone sending close to 5,000 or more messages a day to personal Gmail accounts is a bulk sender: SPF and DKIM, DMARC of at least
p=none, one-click unsubscribe and a spam rate below 0.3% are required. Yahoo and Outlook apply similar rules.Email header analyzer comparison: Mailskop, MxToolbox, Microsoft and Google
All four free header analyzers show delivery delays. Mailskop also draws the message’s route on a country map, parses the header in your browser, accepts .eml/.msg and re-verifies DKIM; MxToolbox and Google process the header on their servers.
Where was an email sent from? Tracing its route and IP location from the header
Where an email was sent from is written in the Received lines of its header: read from the bottom up, each line gives a hop and its IP. Mailskop’s header analyzer maps this route at country or region level and never makes up a location.
Email security measurement, September 2026: DMARC, SPF and DKIM across 21,197 domains
Last updated: