Guides · Setting up

SPF, DKIM and DMARC in plain words

Three DNS records decide whether mail from your domain is trusted or treated as a forgery. What each one does, how they fit together, and what to check.

Setting up3 min read

Email was designed in a more trusting time. Nothing in the original protocol stops anyone from writing a message that claims to come from your address. Three later additions, all published in your domain’s DNS, let receiving servers tell real mail from forgeries: SPF, DKIM and DMARC.

You only need to care about them if you use your own domain for email. If you do, getting them right is what keeps your mail out of other people’s spam folders.

SPF: who may send

Sender Policy Framework is a list of the servers allowed to send mail for your domain. It is a single text record in DNS, starting with v=spf1.

When a server receives a message, it looks at the domain in the message’s return address, fetches that domain’s SPF record, and checks whether the sending server is on the list.

SPF has two well-known weak spots. It checks the hidden return address, not the From address you see. And it breaks when mail is forwarded, because the forwarding server is not on your list.

DKIM: a signature on the message

DomainKeys Identified Mail adds a cryptographic signature to every message you send. The signature covers the important headers and the body. The public key to check it is published in your DNS, under a name called a selector.

A valid signature proves two things: the message was signed by a server holding your domain’s key, and the signed parts have not changed on the way. Unlike SPF, DKIM survives ordinary forwarding.

DMARC: what to do when checks fail

Domain-based Message Authentication, Reporting and Conformance ties the two together and adds a rule. A message passes DMARC when SPF or DKIM passes and the domain they checked matches the domain in the visible From address. That match, called alignment, is what stops a forger from passing SPF on their own domain while showing yours.

Your DMARC record, at _dmarc.yourdomain, also says what receivers should do with mail that fails:

  • p=none: monitor failures without requesting quarantine or rejection. Start here.
  • p=quarantine: treat it as suspicious, usually the spam folder.
  • p=reject: refuse it.

The reports are the useful part early on. They show every server sending mail as your domain, so you can find the legitimate ones you forgot before you tighten the policy.

How they fit together

  • MX records say where mail to your domain is delivered.
  • SPF and DKIM prove mail from your domain is genuine.
  • DMARC says how strict receivers should be and asks them to report back.
  • MTA-STS asks other servers to use encrypted connections when delivering to you.

A short checklist

  1. Publish one SPF record that lists every service sending as your domain.
  2. Turn on DKIM signing at every one of those services.
  3. Publish DMARC with p=none and read the reports for a few weeks.
  4. Move to quarantine, then reject, once only legitimate mail shows up.

In Kistrl

When you add your own domain in Settings, then Domains, Kistrl adds the DNS records for you in one click at Cloudflare, GoDaddy or IONOS, and shows you how to add them step by step at any other provider. It then checks them automatically. Sending from the domain becomes active once the remaining DNS checks pass. See Custom domains and Move your mail to Kistrl.

Your domain, with a deliberate cutover.

Add your domain, publish the records your own account shows, and move receiving over only when everything is ready.

  1. Prove ownership.

    Add the exact ownership record supplied by your own account.

  2. Check sending records.

    Use the SPF, DKIM and DMARC values shown for the domain, not values copied from a screenshot.

  3. Switch receiving last.

    Change MX records when the account says Ready to receive. Keep the old mailbox available during the change.

Custom domainsBring a domain you own. At Cloudflare, GoDaddy or IONOS, Kistrl sets up the DNS records in one click. At any other provider, it shows each record and walks you through adding it. Kistrl then checks them and tells you when it is ready to receive.Put it into practice

Bring your domain, or take a Kistrl address.

Pick a username and it becomes your Kistrl address. No card needed.