SPF, DKIM and DMARC Explained. Stop Criminals Sending Email in Your Name
Three DNS records decide whether your email is trusted, and whether someone else can pretend to be you. Most small businesses have them wrong.
Email was designed without much thought for identity, which is why a criminal can send a message that appears to come from your domain. Three standards, set up as records in your domain's DNS, help receiving mail servers decide whether a message really came from you. Together they protect your customers from fake invoices in your name, and they help your genuine email reach the inbox rather than the spam folder.
SPF, or Sender Policy Framework, is a list of the servers allowed to send email for your domain. A receiving server checks the sending address against that list. A common mistake is having more than one SPF record, or listing too many services, because SPF has a limit of ten DNS lookups and a record that exceeds it can fail. Every service that sends email for you, such as your marketing tool or invoicing system, should be accounted for.
DKIM, or DomainKeys Identified Mail, adds a digital signature to each message. The receiving server uses a public key published in your DNS to check that the message was really signed by your domain and not altered on the way. In Microsoft 365, DKIM is not fully active for a custom domain until you publish the required records and enable signing in the Defender portal. Other services that send as you need their own DKIM set up too.
DMARC, or Domain based Message Authentication, Reporting and Conformance, ties the two together. It tells receivers what to do when a message fails the checks, and it sends you reports about who is sending email using your domain. There are three policies: none, which monitors only, quarantine, which sends failures to spam, and reject, which blocks them. Reject gives the strongest protection against spoofing of your exact domain.
Do not jump straight to reject. Start with a policy of none and a reporting address, and read the reports for a few weeks to find every legitimate sender. Fix the ones that fail, then move to quarantine, and finally to reject once you are confident. Switching to reject too early can block your own invoices. There is also a commercial reason to do this. Google and Yahoo introduced requirements in 2024 for senders of large volumes of email, including authentication, so poorly configured domains risk delivery problems. You can check your records with free online tools, but a mistake in DNS can stop email, so take care.
Dragonfly IT can audit your SPF, DKIM and DMARC setup and take you to a safe reject policy. Ask us for a check.
