Skip to content
9+9PlusTech

SPF, DKIM and DMARC Explained: Set Up Business Email That Reaches the Inbox

If your emails land in spam or criminals can spoof your domain, these three DNS records are the fix. Here is what SPF, DKIM and DMARC do and how to set them up step by step.

9+
9Plus Tech Editorial Team
Updated November 18, 2026 · 4 min read
SPF, DKIM and DMARC Explained: Set Up Business Email That Reaches the Inbox

Using an email address on your own domain, such as [email protected], looks professional and builds trust. But email was designed decades ago with almost no security. Anyone can technically send a message that claims to come from your domain. Mailbox providers such as Gmail, Outlook and Yahoo now rely on three standards, called SPF, DKIM and DMARC, to tell genuine messages from fakes.

Key takeaways

  • SPF lists the servers allowed to send email for your domain; DKIM adds a digital signature to each message.
  • DMARC tells receivers what to do when a message fails those checks, and sends you reports.
  • Large mailbox providers now require these records for bulk senders, and they help every business reach the inbox.

If these records are missing or wrong, your invoices and newsletters may land in spam, and criminals can more easily send phishing emails pretending to be you. Setting them up takes less than an hour.

SPF: who is allowed to send

Sender Policy Framework (SPF) is a TXT record in your domain’s DNS that lists the servers and services allowed to send email for your domain. When a receiving server gets a message from your domain, it checks whether the sending server is on the list.

A typical SPF record looks like this:

Also readCloud Backup vs Cloud Storage: Why Dropbox Is Not a Backup

v=spf1 include:_spf.google.com include:sendgrid.net ~all

  • v=spf1 marks it as an SPF record.
  • Each include: adds a service that sends on your behalf, such as your email provider or newsletter tool. Your provider’s help pages tell you exactly what to include.
  • ~all means messages from other servers should be treated as suspicious. -all is stricter and means they should fail.

Two common mistakes: having more than one SPF record (you must have only one, combining all services), and exceeding the limit of 10 DNS lookups, which happens when too many services are included.

DKIM: a signature on every message

DomainKeys Identified Mail (DKIM) adds a cryptographic signature to the header of each email. The sending service signs the message with a private key, and you publish the matching public key in your DNS. Receivers check the signature to confirm that the message really came from an authorised sender and was not changed on the way.

You do not create DKIM keys by hand. Your email provider or sending service generates them and shows you a record to add, usually a TXT or CNAME record with a name like selector._domainkey.yourcompany.com. Each service that sends for you should have its own DKIM record.

DMARC: the policy and the reports

Domain-based Message Authentication, Reporting and Conformance (DMARC) ties SPF and DKIM together. It tells receiving servers what to do with messages that fail the checks and do not properly align with your domain, and asks them to send you reports.

A starting DMARC record, added as a TXT record at _dmarc.yourcompany.com, might look like this:

v=DMARC1; p=none; rua=mailto:[email protected]

The p value is the policy:

  • p=none: monitor only. Nothing is blocked, but you receive reports.
  • p=quarantine: failing messages go to spam.
  • p=reject: failing messages are refused.

Setting it up step by step

  1. List every service that sends email as your domain: your mailbox provider, website contact forms, newsletter platform, invoicing or CRM tools, help desk and so on.
  2. Create one SPF record that includes all of them.
  3. Turn on DKIM in each service and add the DNS records they provide.
  4. Add a DMARC record with p=none and a reporting address. A DMARC reporting service can turn the raw reports into readable dashboards.
  5. Review reports for a few weeks. Look for legitimate services that are failing and fix them.
  6. Tighten the policy to quarantine, then reject, once all genuine mail passes.
Domains that never send emailProtect parked or unused domains too. Publish an SPF record of v=spf1 -all and a DMARC policy of p=reject so criminals cannot use them for spoofing.

Why this matters more than ever

Google and Yahoo introduced stricter requirements for bulk senders in 2024, including SPF, DKIM, a DMARC record, easy unsubscribe for marketing email and low spam complaint rates. Microsoft announced similar rules for Outlook.com. Even if you only send a handful of emails a day, these records improve the chance that your messages reach the inbox.

How to check your setup

Send a test email to a Gmail address, open it, and choose “Show original”. You will see whether SPF, DKIM and DMARC passed. Free online DNS and email header checkers can also verify your records and point out errors.

Record Where it goes What it does
SPF TXT at your domain Lists allowed senders
DKIM TXT or CNAME at selector._domainkey Verifies a signature on each message
DMARC TXT at _dmarc Sets the policy and sends reports

Together, these three records protect your brand from impersonation and give your legitimate email the best chance of being delivered.

This article is independent, general information and is not legal, financial or security consulting advice. Product features and prices change often, so check the vendor's current documentation before you buy or change your systems.

Read nextProject Management Software: How to Choose the Right Tool for Your Team

More stories