SPF, DKIM and DMARC explained simply
What SPF, DKIM and DMARC records actually do, why your emails land in spam without them, and how to set them up correctly.
The team behind Manuel Mail
If your business emails keep landing in spam — or worse, get rejected — the cause is almost always three small DNS records you haven't set up: SPF, DKIM and DMARC. They take ten minutes to configure and they're the difference between 'trusted sender' and 'probably phishing'. Here's what each one actually does.
The problem they solve
Email has no built-in identity check — anyone can type any 'From' address into a spam tool. So receivers (Gmail, Outlook, Yahoo) verify senders using DNS records published on the sender's domain. Without those records, your legitimate mail looks exactly like a forged one.
SPF — who's allowed to send
SPF (Sender Policy Framework) is a DNS TXT record listing which servers may send mail for your domain. It answers the question 'is this email actually from your mail server, or did a spammer fake your address?' A typical record looks like v=spf1 mx -all — meaning 'only my MX hosts may send, everything else is fake'.
The common mistake: multiple SPF records or too many lookups. There's exactly one SPF record per domain — merge everything into it.
DKIM — a cryptographic signature
DKIM (DomainKeys Identified Mail) adds an encrypted signature to every outgoing email, verified against a public key published in your DNS. Even if someone intercepts the mail, they can't forge the signature — so receivers know it genuinely came from your server and wasn't altered in transit.
Your mail provider generates the key pair and gives you the DNS record to publish — usually a TXT record under a selector like manuel._domainkey.
DMARC — the policy layer
DMARC (Domain-based Message Authentication) ties SPF and DKIM together and tells receivers what to do when they fail: monitor only (p=none), quarantine suspicious mail (p=quarantine), or reject forgeries outright (p=reject). It also sends you reports showing who's sending mail claiming to be you — including the spammers impersonating your domain.
How to set them up
Get the records from your mail provider
A hosted provider like Manuel Mail generates the full zone file — SPF, DKIM public key, DMARC policy — when you add your domain.
Publish them in DNS
Paste each record into your DNS host (registrar or Cloudflare). Cloudflare users can push them automatically.
Verify
Send a test email to a Gmail address — check headers for spf=pass, dkim=pass, dmarc=pass. Most providers also run a DNS check you can trigger.
Watch DMARC reports
After a few weeks, tighten the policy from p=none to p=quarantine then p=reject once you trust the alignment.
Why this matters for Kenyan businesses
Business email in Kenya runs on the same global receivers as everywhere else — Gmail and Outlook apply the same authentication checks to a Nairobi supplier as to a US bank. The businesses whose quotes and invoices actually reach the inbox are the ones with these records published. It's ten minutes of DNS work for a permanent deliverability upgrade.
Manuel Mail generates all three records automatically when you add a domain — publish them once and your mail carries proper authentication from the first send.