Stop criminals sending email as you: SPF, DKIM and DMARC explained
Email was designed in a more trusting age. Out of the box, nothing stops someone sending a message that says it's from accounts@yourcompany.com. Three settings fix that, and most small businesses have at least one of them missing or switched off.
Fake invoices, "urgent" payment requests and changed bank details are among the most expensive crimes businesses face. Many of them start with an email that appears to come from a real supplier, customer or boss. SPF, DKIM and DMARC make it much harder for criminals to use your domain to do that.
SPF: who is allowed to send
SPF (Sender Policy Framework) is a short public list, stored in your domain's DNS, of the services allowed to send email for you. For example, your email provider, your newsletter tool and your invoicing system. When an email arrives claiming to be from you, the receiving server checks whether it came from somewhere on that list.
The most common mistake is forgetting a service, so genuine emails from your invoicing or booking system start failing. The second is listing so many services that the record breaks a technical limit and stops working at all.
DKIM: a tamper-proof signature
DKIM (DomainKeys Identified Mail) adds a digital signature to every email you send. The receiving server checks it against a public key in your DNS. If the signature is valid, the email really came from an authorised sender and wasn't changed on the way. Each service that sends email for you needs DKIM set up separately.
DMARC: what to do when checks fail
SPF and DKIM on their own only produce a pass or fail. DMARC tells receiving servers what to do with email that fails: deliver it anyway, put it in spam, or reject it. It also sends you reports showing who is sending email using your domain, which is often an eye-opener.
DMARC has three levels:
- p=none: monitor only. Nothing is blocked, but you get reports
- p=quarantine: failing email goes to spam
- p=reject: failing email is refused. This is the goal
Many businesses set up DMARC at p=none and never move on. That gives you reports but no protection.
How to switch them on without breaking anything
- List every service that sends email using your domain. Ask your team. Newsletters, CRM, invoicing, booking and support tools are easy to forget
- Set up SPF to include all of them, and DKIM for each one
- Publish DMARC at p=none, with an address to receive reports
- Read the reports for two to four weeks and fix any genuine service that's failing
- Move to p=quarantine, check again, then move to p=reject
- Don't forget domains you own but don't send email from. Give them a strict policy too, so criminals can't use them either
It also helps your genuine email arrive
Large email providers, including Google, Yahoo and Microsoft, now expect organisations that send email in volume to have SPF, DKIM and DMARC in place, and messages without them are more likely to land in spam. Getting these settings right protects your customers and helps your own emails get through.
Want it done for you? Our Email Security service sets up SPF, DKIM and DMARC, watches the reports, and moves you safely to full protection. From $290 per domain.