The email protocol was originally designed so that anyone can send a message with any sender address. This is exactly what invoice fraud and phishing exploit: the message appears to come from the company's own domain. The authentication records SPF, DKIM and DMARC are the way to show recipients which messages are genuine.
Authentication also affects whether the company's own messages are delivered. The large email providers have tightened their requirements, and without authentication, messages increasingly end up in spam or are rejected.
Why is this a maintenance issue?
Email authentication belongs to website maintenance for three reasons:
- The records are in the domain's DNS, in the same place as the website's records.
- Website forms, online shop order confirmations and password reset messages are sent in the domain's name.
- During a server change or DNS move, the records are easily lost if they are not moved along.
The three records in brief
SPF (Sender Policy Framework)
SPF is a TXT record that lists the servers and services allowed to send mail in the domain's name.
v=spf1 include:_spf.mailprovider.example include:newsletterservice.example -all
The -all at the end means that messages from other senders fail the check. The softer ~all marks them as suspicious. An SPF record may contain at most ten mechanisms that require a DNS lookup (such as include), and a domain may have only one SPF record.
DKIM (DomainKeys Identified Mail)
DKIM adds a digital signature to outgoing messages. The recipient verifies the signature using a public key published in the domain's DNS. The key is published as a TXT or CNAME record at selector._domainkey.company.com. Every service that sends mail in the domain's name needs its own DKIM key.
DMARC (Domain-based Message Authentication, Reporting and Conformance)
DMARC ties SPF and DKIM to the visible sender address and tells the recipient what to do if the check fails. It also asks recipients to send reports.
v=DMARC1; p=none; rua=mailto:dmarc-reports@company.com
The policy options are:
| Policy | Effect |
|---|---|
p=none |
No effect on delivery, reporting only |
p=quarantine |
Failed messages go to the spam folder |
p=reject |
Failed messages are rejected |
Requirements of the large providers
In February 2024, Gmail and Yahoo introduced requirements under which bulk senders, meaning those sending more than 5,000 messages a day to them, must use SPF, DKIM and DMARC and offer an easy way to unsubscribe from newsletters. All senders are required to use at least SPF or DKIM. Microsoft announced similar requirements for its Outlook services in 2025. Even if a small business does not exceed the thresholds, authentication improves deliverability with every provider.
Deployment step by step
- Inventory the senders: the company's email service, website forms, the online shop, the newsletter service, the CRM, and invoicing and booking systems.
- Build the SPF record so that it includes all the senders, and check the number of lookups.
- Turn on DKIM in every sending service and publish the keys in DNS.
- Publish DMARC with
p=noneand a reporting address. - Follow the reports for 2–4 weeks. The reports are in XML format, so use a reporting service to read them.
- Fix the missing senders and tighten the policy first to
p=quarantineand finally top=reject.
The most common mistakes
- Two SPF records. When a new service is taken into use, its instructions say to add an SPF record, and the domain ends up with two. This breaks SPF. Merge them into a single record.
- Too many include lookups. More than ten lookups cause an error.
- The form sends through the server. WordPress's default sending uses the server's own mail function, which is not authenticated. Use an SMTP plugin or a sending service.
- DMARC stays at p=none permanently. Reporting is a good start, but only a stricter policy protects the domain from spoofing.
- Records are lost in a server change. When the name servers change, all TXT records must be moved along. Read more in Domain, DNS and SSL.
Checklist
- Does the domain have exactly one SPF record that includes all senders?
- Do all sending services sign messages with DKIM?
- Is DMARC in use, and are the reports read?
- Has the policy been tightened to quarantine or reject?
- Are messages from the website's forms sent through an authenticated service?
- Have strict records been set for domains that send no mail?
Frequently asked questions
How can I tell whether my domain has SPF, DKIM and DMARC?
The records are publicly visible in DNS. You can check them with testing tools from the National Cyber Security Centre Finland or email providers, for example, or from the command line with nslookup or dig by looking up the domain's TXT records and the address _dmarc.yourdomain.com.
Why do messages from my website's form go to spam?
Often the form sends the message through the web server using a sender address that the domain's SPF record does not allow, and the message is not signed with DKIM. The fix is to send form messages through an SMTP service or email provider that is included in SPF and signs the messages.
Can DMARC be set straight to reject?
It is not a good idea. If some service sends mail in the domain's name without proper authentication, reject mode blocks its messages. Start with p=none, follow the reports for a few weeks, fix the missing senders and tighten the policy in stages.
Does a domain that sends no email need these records?
Yes. For a domain that sends no mail, set a strict SPF record v=spf1 -all and a DMARC policy of p=reject. That way nobody can send scam messages in the domain's name.