SPF, DKIM and DMARC are three records you add to your domain’s DNS. Together they prove that email claiming to come from your domain really does. Gmail, Yahoo and Outlook require all three from bulk senders, and they help every sender reach the inbox.
The short version
| Record | Question it answers | Where it lives |
|---|---|---|
| SPF | Is this server allowed to send for this domain? | TXT record on your domain |
| DKIM | Was this email really signed by this domain, and unchanged? | TXT record at selector._domainkey.yourdomain.com |
| DMARC | What should happen if SPF and DKIM do not match the From address? | TXT record at _dmarc.yourdomain.com |
SPF: who may send
SPF (Sender Policy Framework) is a list of the servers allowed to send email for your domain. The receiving server checks the sending server against it.
An SPF record looks like this:
v=spf1 include:_spf.google.com include:spf.example-esp.com ~all
v=spf1marks it as an SPF record.- Each
include:adds a provider you send through (your mailbox provider, your email marketing tool). ~allsays other servers are not authorised (a “soft fail”).
Common mistakes
- Two SPF records. A domain can have only one. If your email tool gives you a record and you already have one, merge the
include:parts into a single record. - Too many lookups. SPF allows at most 10 DNS lookups. Each
include:counts, and so do the includes inside it. Remove providers you no longer use.
SPF alone has a weakness: it checks the hidden “envelope” sender, not the From address people see. That is why DKIM and DMARC exist.
DKIM: a signature on every email
DKIM (DomainKeys Identified Mail) adds a digital signature to each email. Your email provider signs with a private key; the matching public key sits in your DNS. If the signature checks out, the receiver knows the email came from your domain and was not changed on the way.
A DKIM record is a TXT record at a name like mailer._domainkey.yourdomain.com:
v=DKIM1; k=rsa; p=MIIBIjANBgkqhkiG9w0BAQEFAAOCAQ8AMIIBCgKCAQEA...
Your email provider generates it; you copy it into your DNS. Each provider uses its own selector (the part before ._domainkey), so several services can sign for the same domain.
Common mistakes
- Adding the domain twice: some DNS providers add your domain to the name automatically, so
mailer._domainkey.yourdomain.combecomesmailer._domainkey.yourdomain.com.yourdomain.com. Enter onlymailer._domainkeyin that case. - Extra quotes: if your provider adds quotes around TXT values, paste the value without them.
- Long keys split badly: some DNS panels need long values split into strings. Your DNS provider’s help pages explain how.
In Robust Email, the DKIM record is shown under Sending › Sending domains when you add your domain, and it is the record that verifies the domain. Read Verify your domain.
DMARC: the policy that ties it together
DMARC (Domain-based Message Authentication, Reporting and Conformance) does two things:
- It requires alignment: the domain in the visible From address must match the domain that passed SPF or DKIM.
- It tells receivers what to do with mail that fails, and where to send reports.
A DMARC record is a TXT record at _dmarc.yourdomain.com:
v=DMARC1; p=none; rua=mailto:dmarc-reports@yourdomain.com
p=is the policy:none(only report),quarantine(send failures to spam) orreject(refuse them).rua=is where daily aggregate reports go.
Roll it out in three steps
- Monitor: publish
p=noneand read the reports for a few weeks. They show every service sending as your domain, including ones you forgot (invoicing tools, helpdesks, CRMs). - Fix: make sure each legitimate service passes SPF or DKIM with alignment.
- Enforce: move to
p=quarantine, thenp=reject. Spoofed email using your domain is then blocked.
Reports are XML files. A DMARC reporting service turns them into readable dashboards; several have free plans.
How they work together
When an email arrives:
- The receiver checks SPF against the sending server.
- It checks the DKIM signature against your public key.
- DMARC passes if either SPF or DKIM passes and its domain aligns with the From address.
- If DMARC fails, the receiver applies your policy.
For marketing email, DKIM is usually what makes DMARC pass, because the envelope sender often belongs to the sending service. That is why signing with your own domain matters.
Check your records
- Send an email to a Gmail address, open it, choose Show original, and look for
SPF: PASS,DKIM: PASSandDMARC: PASS. - Use your DNS provider’s lookup or a public DNS checker to see the records the world sees.
Next: the Gmail and Yahoo bulk sender rules and the deliverability checklist.