Guide · Email security
From no DMARC to p=reject, without breaking your email
Three DNS records decide whether criminals can send email that looks like it came from your business. This guide takes you from none of them to full protection in about six weeks, mostly waiting time.
The three records in one minute
- SPF
- A list of the servers allowed to send email for your domain.
- DKIM
- A digital signature your email provider adds to each message, proving it wasn't changed and really came from your systems.
- DMARC
- Your instruction to receiving servers: what to do with email that fails SPF and DKIM checks (nothing, junk it, or reject it), and where to send reports.
Step 1: List everything that sends email as you
Before changing anything, write down every system that sends from your domain: your mailbox provider (Microsoft 365, Google Workspace), website contact forms, invoicing and accounting software, newsletter tools, booking systems, CRM, and any printers or scanners that email. Each needs to pass SPF or DKIM, or DMARC will eventually block its mail.
Step 2: Publish one SPF record
Add a single TXT record at your domain root, for example v=spf1 include:spf.protection.outlook.com ~all for Microsoft 365. Add an include: for each service from step 1, using the value from that service's help pages. Keep it to one record and under 10 DNS lookups; the checker counts these for you.
Step 3: Switch on DKIM everywhere you can
In Microsoft 365 or Google Workspace, enable DKIM signing in the admin settings and publish the records they give you. Do the same for newsletter and invoicing tools that offer "domain authentication". DKIM is more reliable than SPF because it survives email forwarding.
Step 4: Publish DMARC in monitoring mode
Add a TXT record at _dmarc.yourdomain.co.uk:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.co.uk; fo=1
Nothing is blocked yet. Receivers start sending daily XML reports showing every server that sent email using your domain, and whether it passed.
Step 5: Read the reports for two to four weeks
The reports are machine-readable XML, which is hard going by hand. Look for your genuine services failing (fix them with SPF or DKIM) and unknown senders (usually spoofing, which is exactly what DMARC will stop).
Step 6: Move to quarantine, then reject
When all genuine mail passes, change p=none to p=quarantine. Failing mail now goes to spam. After another two weeks with no problems, change to p=reject, and failing mail is refused outright. That's full protection.
Step 7: Lock down domains that don't send email
Spare domains you own but don't use for email are easy targets. For each one publish v=spf1 -all and v=DMARC1; p=reject;.
Optional extras
- MTA-STS and TLS-RPT make other servers deliver to you only over encrypted connections, and report problems.
- BIMI shows your logo in some inboxes once DMARC is at quarantine or reject.
General guidance only. Test changes carefully: a wrong record can stop your email being delivered.