Why email authentication matters
Since 2024, Gmail and Yahoo require bulk senders to authenticate their mail, and every major provider uses these records to decide between the inbox, the spam folder and outright rejection. They also stop strangers sending phishing in your name. For a startup, that means signup confirmations, password resets and launch emails reaching people.
The three records
- SPF (a TXT record on your domain) lists the servers allowed to send as you:
v=spf1 include:_spf.google.com include:sendgrid.net ~all. Keep to one SPF record, and keep it under 10 DNS lookups. Eachinclude,a,mxandredirectcosts one, and so do the includes inside them. Over 10, SPF fails for everyone. - DKIM signs each message with a key published at
selector._domainkey.yourdomain.com. Your email provider gives you the record. Use 2048-bit keys where you can. - DMARC (a TXT record at
_dmarc.yourdomain.com) tells receivers what to do when a message fails SPF and DKIM alignment, and where to send reports:v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com.
A safe rollout
- Publish SPF and turn on DKIM with every service that sends for you: your mailbox provider, newsletter tool, transactional email and CRM.
- Add DMARC with
p=noneand aruaaddress. Read the reports for two to four weeks to find senders you forgot. - Move to
p=quarantine, thenp=rejectonce legitimate mail passes.
Domains that never send mail
Lock them down so nobody can spoof them: v=spf1 -all and v=DMARC1; p=reject.
BIMI is the optional last step. It shows your logo next to messages in Gmail and Apple Mail, and needs DMARC at quarantine or reject first.
See every raw record with the DNS lookup.