Email

SPF, DKIM and DMARC

SPF, DKIM and DMARC are DNS-based standards that let a receiving mail server check an email really comes from the domain it claims, and decide what to do when it does not.

Also called: email authentication, SPF record, DKIM, DMARC, email spoofing protection

Anyone can type any address into the From line of an email. The three standards below are how receiving servers separate real mail from forged mail. They work together, and mailbox providers increasingly expect all three.

SPF: who may send

Sender Policy Framework is a DNS record that lists the servers allowed to send mail for a domain. The receiving server looks at the connecting server and checks it against the list.

DKIM: was it changed

DomainKeys Identified Mail adds a digital signature to each message. The signing key’s public half is published in DNS, so the receiver can verify the signature and know the message came from the domain and was not altered on the way.

DMARC: what to do about failures

DMARC ties the other two to the visible From domain and sets a policy: do nothing, quarantine or reject mail that fails. It also lets a domain owner receive reports of who is sending mail in their name, which is how you notice abuse.

The common mistake

SPF and DKIM can pass for another domain than the one in the From address. DMARC requires alignment, meaning the authenticated domain has to match the From domain. A service that signs with its own domain instead of yours may pass SPF and DKIM and still fail DMARC.

In StaticForm

To send notification emails from forms@yourdomain.com, add the domain in Settings > Integrations > Email Domains. StaticForm generates DKIM CNAME records, which you publish at your DNS provider; the mail is sent through Amazon SES, so the domain’s DKIM signature is aligned with your From address. You can also set a custom MAIL FROM subdomain and add a DMARC record for better deliverability, then recheck the status and send a test email. See email deliverability for how this fits together.

Learn more