You send a quote to a new client and it lands in their spam folder. Or a customer asks about a strange invoice "from you" that you never sent. Both problems trace back to the same question: can email providers confirm that messages using your domain really come from you? Three DNS settings, SPF, DKIM and DMARC, answer it.
Email was designed decades ago without a built-in way to check the sender. Anyone can type any address into the From line, much like anyone can write any return address on an envelope. Spammers and scammers rely on this.
So the big mailbox providers look for proof. Messages from domains that can't be verified are more likely to go to spam or be rejected. Gmail and Yahoo tightened their rules in 2024, and senders of large volumes are now expected to have all three records in place. Even if you send only a handful of emails a day, setting them up is worth it.
SPF, short for Sender Policy Framework, is a TXT record in your domain's DNS that lists the services allowed to send email for your domain. When a message arrives, the receiving server checks whether it came from a sender on that list.
A typical SPF record looks something like v=spf1 include:mail.example-provider.com ~all. Each include names an approved sender, and the ending tells receivers how to treat everything else.
Two rules trip people up:
DKIM, or DomainKeys Identified Mail, adds a digital signature to each outgoing message. Your email service signs with a private key, and you publish the matching public key in your DNS. The receiving server uses that public key to confirm two things: the message was sent by a service you authorized, and it wasn't altered along the way.
You don't create DKIM keys yourself. Your email or newsletter provider generates them and gives you records to add, usually as TXT or CNAME records under a name that includes a short label called a selector. Each sending service gets its own.
SPF and DKIM provide evidence. DMARC, short for Domain-based Message Authentication, Reporting and Conformance, tells receivers what to do with that evidence. It also checks alignment, meaning the domain that passed SPF or DKIM must match the domain in the From address your customers actually see.
A DMARC record is a TXT record at _dmarc.yourdomain.com, and it sets a policy:
A starting record might read v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com. The rua address receives summary reports showing who is sending mail as your domain and whether it passes.
Start with p=none. Read the reports for a few weeks to find every legitimate service sending as you, fix any that fail, then move to quarantine and eventually reject. Jumping straight to reject can block your own invoices.
This is the step most often missed. Your domain may send email from more places than you think:
Each one needs to pass SPF or DKIM in a way that aligns with your domain, and ideally both. Most of these services have a help page about authenticating your domain, with the exact records to add.
Send an email from each service to a personal Gmail address, open it, and choose "Show original" from the message menu. Gmail shows whether SPF, DKIM and DMARC passed. Anything marked fail, or missing, needs attention.
Authentication gets you through the door; good habits keep you there. Email only people who asked to hear from you, include a clear unsubscribe link in marketing mail, never buy lists, and remove addresses that bounce. Your checklist: one SPF record, DKIM for every sender, DMARC starting at p=none, and a monthly look at the reports.