Short answer: SPF, DKIM and DMARC are three DNS records that prove email from your domain really came from you. SPF lists the services allowed to send as your domain, DKIM adds a digital signature to every message, and DMARC tells receiving servers what to do with mail that fails those checks and sends you reports about it. Most small businesses can set all three up in Microsoft 365 or Google Workspace in an afternoon of DNS work, and anyone sending large volumes to Gmail, Yahoo or Outlook.com addresses is now required to have them.
Without these records, anyone can send an email that shows your domain in the From line. That is how fake invoices, "updated bank details" requests and gift card scams reach your customers and vendors looking like they came from you. These records also help your real email land in the inbox instead of spam.
What are SPF, DKIM and DMARC?
| Record | What it does | Where it lives | Example |
|---|---|---|---|
| SPF | Lists the servers and services allowed to send email for your domain | One TXT record on your domain | v=spf1 include:spf.protection.outlook.com -all |
| DKIM | Signs each outgoing message so the receiver can confirm it wasn't forged or changed | Microsoft 365: two CNAME records (selector1._domainkey and selector2._domainkey). Google Workspace: a TXT record, usually google._domainkey |
Values are generated for you in the admin portal |
| DMARC | Checks that SPF or DKIM passed and matches the domain in the From line, sets a policy for failures, and sends reports | TXT record at _dmarc |
v=DMARC1; p=none; rua=mailto:dmarc@yourdomain.com |
The key idea in DMARC is alignment. A message passes DMARC only if SPF or DKIM passes for the same domain that the recipient sees in the From address. That is what stops someone from passing SPF with their own domain while pretending to be yours.
Step 1: List everything that sends email as your domain
Before you touch DNS, make a list. Most small businesses have more senders than they think:
- Microsoft 365 or Google Workspace (your normal mailboxes)
- Your website's contact forms
- Newsletter or marketing email platforms
- CRM, invoicing, accounting and payroll software that emails customers
- Help desk or scheduling tools
- Copiers and scanners that send scan-to-email
- Phone systems that send voicemail to email
Anything missing from this list will start failing once DMARC is enforced, so this step matters more than any other.
How do you set up SPF, DKIM and DMARC in Microsoft 365?
- SPF. There's no SPF setting inside Microsoft 365. You add or edit one TXT record at your DNS host. Microsoft's records use
include:spf.protection.outlook.com, and you add aninclude:for each other service on your list. Microsoft's examples end with-all. - DKIM. Custom domains aren't signed with your own domain until you turn this on. In the Microsoft Defender portal, open the Email authentication settings page (security.microsoft.com/authentication) and select the DKIM tab. Choose your domain, copy the two CNAME values Microsoft shows you, create them at your DNS host, then return and turn on Sign messages for this domain with DKIM signatures. Microsoft's current CNAME targets end in
dkim.mail.microsoft, so always copy the exact values from your own portal instead of an older guide. DNS changes can take anywhere from a few minutes to 48 hours to show up. - DMARC. Add a TXT record with the host name
_dmarcand start withp=noneplus a reporting address (more on that below).
While you're in the admin portals, it's worth checking the rest of your Microsoft 365 security settings too.
How do you set them up in Google Workspace?
- SPF. If Google Workspace is your only sender, Google's recommended record is
v=spf1 include:_spf.google.com ~all. Add aninclude:for each other service you listed. - DKIM. In the Google Admin console, go to Apps, then Google Workspace, then Gmail, then Authenticate email. Generate a key (Google recommends 2048-bit if your DNS host supports it), add it as a TXT record at your DNS host, and wait. Google says it can take up to 48 hours to start working. Then go back and click Start authentication. The status should change to "Authenticating email with DKIM."
- DMARC. Google recommends that SPF and DKIM be authenticating for at least 48 hours before you turn on DMARC. Then add the
_dmarcTXT record starting atp=none.
What do Google, Yahoo and Microsoft require from senders?
As of November 2026, the large mailbox providers publish these rules for mail sent to their personal accounts:
| Gmail (Google) | Yahoo | |
|---|---|---|
| Who counts as a bulk sender | Close to 5,000 or more messages a day to personal Gmail accounts, counted across your whole domain. Once you hit it, the status is permanent | Any "significant volume." Yahoo doesn't publish a number |
| Authentication for bulk senders | SPF and DKIM, plus DMARC (p=none is allowed), with the From domain aligned to SPF or DKIM | SPF and DKIM, plus a DMARC policy of at least p=none that passes, with alignment |
| Unsubscribe | One-click unsubscribe for marketing and subscribed mail, plus a visible unsubscribe link | One-click unsubscribe plus a visible link, and unsubscribes honored within 2 days |
| Spam complaint rate | Below 0.3%, and Google advises staying under 0.1% | Below 0.3% |
Google also requires every sender, no matter how small, to have SPF or DKIM, valid forward and reverse DNS, and TLS encryption. Google says it began ramping up enforcement in November 2025, including temporary and permanent rejections of non-compliant mail.
Microsoft applies similar rules to domains sending more than 5,000 messages a day to Outlook.com, Hotmail.com and Live.com addresses: SPF and DKIM must pass, and DMARC must be at least p=none and aligned. Microsoft began enforcing these rules in May 2025 and has said that non-compliant mail is rejected rather than sent to junk.
Even if your office never comes close to 5,000 messages a day, your newsletter platform might, and these rules are the clearest signal of where email is headed.
What are the most common mistakes?
- Two SPF records. Only one SPF record is allowed per domain. Two cause SPF to fail with a permanent error. Combine them into one.
- Too many lookups. SPF fails if checking it takes more than 10 DNS lookups. Every
include:adds at least one, so stacking services can break it. - Forgetting a sender. The invoicing tool or website form nobody remembered is the most common cause of DMARC failures.
- Third-party tools that aren't aligned. Many services pass SPF using their own domain, which doesn't count for DMARC. Set up the service's custom DKIM for your domain so it aligns.
- Jumping straight to p=reject. You can block your own invoices and password resets.
- Never reading the reports. A DMARC record at p=none with no one reviewing reports protects nothing.
- Ignoring unused domains. Microsoft recommends that domains you own but never send mail from publish SPF and DMARC records saying no mail should ever come from them, so scammers can't use them either.
How do you move DMARC from p=none to quarantine and reject?
p=none is monitoring mode. Mail that fails still gets delivered, but you start receiving reports. The goal, as Microsoft puts it, is to reach p=reject without blocking good mail along the way.
- Monitor. Publish
p=nonewith anrua=address. Reports arrive as XML files, so most businesses use a DMARC reporting service to turn them into something readable. Microsoft suggests reviewing them weekly during rollout and monthly once things are stable. - Fix every legitimate sender. Each source in the reports should either pass with alignment or be identified as fake.
- Move to quarantine. Change to
p=quarantine. Failing mail goes to spam or junk. Some admins use thepct=tag to apply the policy to part of failing mail first. - Move to reject. When reports show only spoofed mail failing, change to
p=reject. Failing mail is refused outright. - Keep watching. Every new tool that sends email goes through the same check before you turn it on.
How long this takes depends on how many senders you have. A business that only uses Microsoft 365 can move quickly; one with five marketing and billing tools should plan on several weeks of reports.
FAQ
Will DMARC stop all phishing?
No. It stops people from sending mail that uses your exact domain. Lookalike domains (like a swapped letter) still get through, so staff training and knowing what to do after clicking a phishing link still matter.
Should SPF end in ~all or -all?
Google recommends ~all (soft fail) and Microsoft's examples use -all (hard fail). Once DMARC is enforced, DMARC does most of the work, so the bigger priority is getting DKIM and alignment right.
Do I need DMARC if we only send normal office email?
Yes. It's the only one of the three that lets you tell other mail servers to reject fakes, and the reports show you who is sending as your domain.
How long do DNS changes take?
Usually minutes, but both Microsoft and Google note it can take up to 48 hours.
Get your email authentication checked
TechCore can review your SPF, DKIM and DMARC records as part of our network security services, and our help desk can walk through your DNS records remotely for businesses anywhere in the US. Request a free IT assessment and we'll check what's published on your domain today and what it would take to get to p=reject safely.



