Email was designed decades ago without any built-in way to prove who sent a message. That's why spam and phishing are so common. SPF, DKIM and DMARC are the standards that fix this. They let your domain vouch for the emails sent in its name.
Since 2024, Gmail and Yahoo require proper authentication from bulk senders, and they've become stricter for everyone else too. If yours isn't set up, more of your mail ends up in spam or rejected outright.
SPF: who is allowed to send
Sender Policy Framework is a DNS record that lists the services allowed to send email for your domain. If you use Google Workspace for your inbox, Mailchimp for newsletters and your website sends contact form notifications through a service like Postmark, all three need to be included.
Common SPF problems:
- More than one SPF record. You're only allowed one. Multiple records break SPF entirely.
- Missing services. A new marketing or invoicing tool sends mail but isn't listed.
- Too many lookups. SPF has a limit of 10 DNS lookups. Long records with many services can exceed it.
DKIM: a tamper-proof signature
DomainKeys Identified Mail adds a digital signature to each email. The receiving server checks that signature against a public key in your DNS. If it matches, the message really came from an authorized sender and wasn't changed along the way.
Each sending service (your email provider, newsletter tool, CRM, help desk) provides its own DKIM records to add. Turn it on in every tool that sends as your domain.
DMARC: the policy that ties it together
DMARC tells receiving servers what to do when a message fails SPF and DKIM checks, and sends you reports about who is sending mail as your domain.
A DMARC record has a policy:
p=none: just monitor and reportp=quarantine: send failing mail to spamp=reject: block failing mail entirely
The safe path is to start at none, read the reports for a few weeks to find any legitimate senders you missed, fix them, then move to quarantine and eventually reject. Jumping straight to reject can block your own invoices or newsletters.
How to check yours
- Run our Email Health Check for a plain-English read on all three records
- Send a test email to a Gmail account, open it, choose "Show original" and look for PASS next to SPF, DKIM and DMARC
- Use an online checker for your domain's DMARC and SPF records (MXToolbox and similar tools)
- Read your DMARC reports, or use a reporting service that turns them into readable summaries
Other things that hurt deliverability
- Sending from a personal email address (like a Gmail address) through a marketing tool. Use your own domain.
- Mismatched "from" addresses. The domain in the from address should match the one that's authenticated.
- No unsubscribe link in marketing email. Gmail and Yahoo also require one-click unsubscribe for bulk senders.
- High complaint rates. Only email people who asked to hear from you.
- Purchased lists. They damage your sender reputation quickly.
When to revisit
Any time you add a tool that sends email for you, check SPF and DKIM. Common culprits include new CRMs, booking tools, invoicing apps, website form services and help desks.
Want it handled?
This is one of the most common fixes we make for new clients, and one of the most satisfying, because it often solves months of "did you get my email?" in an afternoon. It's included in our hosting and care work, and we check it during every Business Tech Tune-Up.
