SPF, DKIM, and DMARC are three short settings on your domain that prove email from your business really comes from your business. They live in your domain’s DNS, the behind-the-scenes settings that point your domain at your website and your email. You never see them when you send a message, but every inbox you send to checks them.

Think of sending email like delivering a letter to a guarded building. SPF is the guest list of who’s allowed to deliver for you. DKIM is a wax seal that shows the letter wasn’t opened or changed on the way. DMARC is your note to the guard saying what to do with anything that fails.

Why inboxes now expect them

Anyone can type any “from” address into an email. That’s how most phishing works. To fight it, the big inbox providers have tightened their rules. Since 2024, Google and Yahoo have required anyone sending to their users to authenticate their mail, and large senders (Google’s line is around 5,000 messages a day to Gmail addresses) need all three records, plus easy one-click unsubscribe on marketing email. Microsoft has since brought in similar rules for high-volume senders to Outlook.com.

Even if you’re nowhere near those numbers, mail without authentication is far more likely to be filtered as spam or turned away. And your business probably sends through more services than you realize: your mailboxes, your website forms, your invoicing or booking software, and your newsletter.

SPF: who’s allowed to send

SPF (Sender Policy Framework) is a single text record listing the services allowed to send email for your domain, like your email provider and your newsletter platform. A receiving server checks the sending server against that list.

  • Your domain can have only one SPF record. Every service is added to that same record. A second SPF record doesn’t add anything; it breaks both.
  • There’s a limit to how many lookups an SPF record can trigger (10), so a long list of services can quietly start failing.

DKIM: a tamper-proof signature

DKIM (DomainKeys Identified Mail) adds a digital signature to each message. The sending service signs it with a private key, and you publish the matching public key in your DNS. The receiving server uses it to confirm the message came from an approved sender and wasn’t altered along the way.

Each service that sends for you has its own DKIM key, so each one needs setting up. Google Workspace and Microsoft 365 both need you to switch on DKIM for your own domain, and it’s an easy step to miss during setup.

DMARC: the policy and the reports

DMARC (Domain-based Message Authentication, Reporting, and Conformance) ties the other two together. It checks that the domain people actually see in the “from” line matches a domain that passed SPF or DKIM, and it tells inboxes what to do when a message fails:

  • none: deliver as normal, just report back. This is monitoring only.
  • quarantine: treat it as suspicious, usually by sending it to spam.
  • reject: refuse it outright.

DMARC can also ask the big providers to send you regular reports showing who is sending email using your domain. The sensible path is to start at none, use the reports to make sure every legitimate service passes, then tighten the policy. Jumping straight to reject can block your own invoices, form notifications, or newsletters.

Do you need them?

If you send any email from your own domain, yes. At a minimum, you want SPF and DKIM set up for your email provider and for every other service that sends as you, plus a DMARC record. If you only use a free address like gmail.com, you can’t set these up at all, because you don’t control that domain. That’s one of the main reasons to move to email on your own domain.

How to check yours

  1. Send an email from your business address to a Gmail account.
  2. Open the message in Gmail, click the three-dot menu, and choose Show original.
  3. Near the top you’ll see results for SPF, DKIM, and DMARC. You want PASS on all three.
  4. Do the same for each service that sends as you. Submit your website’s contact form, send yourself a test newsletter, and so on.

Free lookup tools such as MXToolbox will also show which records your domain has published and flag obvious problems.

Why we don’t give you a copy-paste record

The right records depend entirely on which services send email for your domain. A generic SPF record can leave out a service you rely on, a second SPF record breaks the first, and a strict DMARC policy published too early can block your own mail. Before you change anything, note down or screenshot your existing DNS records so you can put them back. If you’re not sure which services send as you, find out first. That’s most of the work.

Related guides: Free email vs. business email: what changes when you use your own domain · Why aren't my website's form emails arriving?

If you’re a GORGEOUS client, open a ticket and we’ll check and set up your records for you. Not a client yet? Get in touch.

Still stuck?

Two easy ways to reach us: open a ticket and a real person on our team picks it up, or click "Help & Support" right inside your dashboard.

Open a ticket