Crashcart Start your free trial

Business email and domains

How to set up DMARC for a small business

DMARC is a DNS record that tells other mail servers what to do with email that puts your domain in the From line but fails the SPF and DKIM checks. DMARC setup for a small business is four moves: turn on DKIM in Microsoft 365 or Google Workspace, confirm your SPF record, publish a _dmarc TXT record at p=none with an address for reports, then move to p=quarantine and p=reject once the reports show all your real mail passing. Plan on a few weeks, most of it waiting and reading reports. Only p=reject asks receivers to refuse mail that fakes your domain.

The full name is Domain-based Message Authentication, Reporting, and Conformance, defined in RFC 9989, which replaced RFC 7489 in May 2026. Of everything in email security for small businesses, it decides whether a stranger can send your clients an invoice from your address.

What DMARC does

Every email carries two sender addresses, the From address your client sees and a hidden envelope address that servers use for delivery. SPF lists the servers allowed to send for your domain and checks the hidden address. DKIM signs each message with a key published in your DNS. Neither checks the From line.

DMARC does. A message passes when SPF or DKIM passes for a domain that matches the From domain, which the standard calls alignment (section 3.2.10). When both fail, your record tells the receiver to take no action, treat the message as suspicious, or reject it (section 4.7). If your own mail doesn't pass for your domain, a reject policy blocks it, which is why DKIM comes first.

How many small businesses have DMARC set up

On October 14, 2026, we looked up the public DNS records of 316 small tax and accounting firms in Alabama, Tennessee and Georgia, a list we built for our own sales research. They are firms with 3 to 12 preparers in the IRS's public list of PTIN holders that list a website, without franchises or national firms. We checked each domain's mail server (MX), SPF and DMARC records, and DKIM keys at the default names Microsoft 365 and Google Workspace use.

262 of the domains receive email. Of those 262:

  • 122 (47%) had no DMARC record. 110 of them had SPF, so someone did the first step and stopped.
  • 73 (28%) were at p=none, and 35 of those had no report address, so the record does nothing.
  • 4 had broken records. Three published two DMARC records, which RFC 9989 tells receivers to discard (section 4.10), and one had no policy.
  • 63 (24%) were at quarantine or reject, 26 of them at reject.

That leaves 199 of 262 (76%) with nothing telling receivers to act on mail that fakes their domain.

Mail provider (from the MX record) Domains No DMARC p=none Quarantine or reject DKIM key found
Microsoft 365 117 48 27 40 58
Google Workspace 39 26 11 2 10
Filtering service or other host 106 48 35 21 not checked

Broken records count only in the totals. Microsoft 365 uses the same DKIM record names everywhere, so 58 is exact; Google allows other names, so 10 is a minimum. Half the Microsoft 365 firms had no DKIM records, which they need before enforcing DMARC.

Check what your domain has now

This is free from any Windows or Mac computer. Open Command Prompt or Terminal and run these, with your domain in place of example.com:

nslookup -type=TXT _dmarc.example.com
nslookup -type=TXT example.com

The first, from Microsoft's DMARC guide, shows your DMARC record. In the second, the line starting v=spf1 is SPF. Look for these problems:

  • No line starting v=DMARC1 means no DMARC.
  • p=none with no rua= means no policy and no reports.
  • Two v=DMARC1 records make receivers skip DMARC. Delete one.
  • Two v=spf1 records make SPF fail with a permanent error, per Microsoft. Merge them.

Turn on DKIM first

Microsoft says no DKIM signing happens for mail from your own domain until you set it up. In Microsoft 365:

  1. In the Defender portal at security.microsoft.com, go to Email & collaboration, Policies & rules, Threat policies, Email authentication settings, and open the DKIM tab.
  2. Try to turn on the toggle in your domain's row. An error lists the records you need; select OK.
  3. Click the row and copy the two CNAME records under Publish CNAMEs, named selector1._domainkey and selector2._domainkey.
  4. Add both at your DNS host, wait a few minutes or longer, then turn on Sign messages for this domain with DKIM signatures.

In Google Workspace, as a super administrator:

  1. In the Admin console, go to Apps, Google Workspace, Gmail, Authenticate email.
  2. Select your domain, then Generate New Record. Pick a 2048-bit key if your DNS host supports it and keep the selector google.
  3. Add the TXT record it shows, named google._domainkey, at your DNS host.
  4. Click Start authentication. Google says it can take up to 48 hours to work.

Keep one SPF record per domain. Microsoft's standard is v=spf1 include:spf.protection.outlook.com -all, and Google's is v=spf1 include:_spf.google.com ~all. Google says to wait 48 hours after SPF and DKIM before adding DMARC.

A DMARC record example

Start with this, sending reports to a mailbox or group you create only for them:

v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
Tag What it does At the start
v=DMARC1 Marks the record as DMARC. Must come first. Required
p What to do with failing mail: none (no action), quarantine (treat as suspicious, usually the spam folder) or reject (refuse it) none
rua Where daily summary reports go, written as mailto: Your report mailbox
pct Percent of failing mail the policy applies to. RFC 9989 removed it, but Microsoft and Google still honor it. Use only while ramping up
sp Policy for subdomains. Defaults to p. Leave out

These follow RFC 9989 section 4.7 and Google's tag list. Skip ruf; Microsoft 365 doesn't send those reports and Gmail ignores the tag.

Add the TXT record at your DNS host

Your DNS host is usually the company where you bought the domain, sometimes your web host. nslookup -type=NS example.com lists your nameservers, and their names usually show the company. If nobody knows who controls the domain, settle that first; it's part of running IT in a small office without an IT person.

  1. Sign in at the DNS host and open the domain's DNS settings.
  2. Add a TXT record with host or name _dmarc and your record as the value.
  3. Save, wait, and run the nslookup command again. Google warns that some hosts add your domain to the name automatically, so check where the record landed.

Read the reports at p=none

Google says reports usually arrive once a day from each mail system that received mail from your domain. Each is an XML file listing sending IP addresses, message counts, and whether SPF and DKIM passed and aligned. Microsoft and Google both suggest a DMARC reporting service to turn the XML into tables.

You're looking for three things:

  • Your provider's servers passing DKIM, aligned. That's your everyday mail.
  • A service you use that fails. SPF passing with alignment failing is what Microsoft calls the classic alignment problem.
  • Unknown sources, all failing. That's mail faking you.

Google's rollout guidance is at least a week at p=none. I'd wait through one full billing cycle, so the monthly invoice run shows up.

Find every service that sends as you

The usual ones are invoicing software that emails from your address, a newsletter tool, a client portal or e-signature tool, and the website's contact form. Look in each one's settings or help pages for domain authentication or DKIM, and add the records it gives you.

DKIM with your domain is the fix. Microsoft's troubleshooting table says a service that passes SPF for its own domain still fails DMARC until it signs with your domain or sends with your domain as the envelope sender. Adding its include: to SPF often isn't enough.

Contact forms are the usual surprise. Many send from the web host's server with your address in the From line, and that server isn't in your SPF record or signing with your key. Have whoever built the site send form mail through your Microsoft 365 or Google account instead.

Move from quarantine to reject

When the reports show all your real mail passing, tighten the policy in steps. RFC 9989 dropped the pct tag and added t=y, a test mode that asks receivers to apply one step milder policy than the one you publish. Microsoft's and Google's rollout guides still use pct, and their receivers honor it, so the steps below follow them:

  1. Change to p=quarantine with a small pct. Google's example is v=DMARC1; p=quarantine; pct=5; rua=mailto:dmarc@example.com, and it suggests about 10% for a small organization.
  2. Raise pct in steps. Microsoft uses 10, 25, 50, 75 and 100. Check the reports and ask staff whether anything went missing.
  3. Change to p=reject and drop pct, since 100 is the default. Keep rua.

Microsoft's stated goal is p=reject on every domain. A reject policy breaks quietly when someone signs up for a new service that sends as you, so keep reading reports, weekly during rollout and monthly after, as Microsoft suggests. Crashcart checks the email domain of each office it runs every week and tells the owner in one line when DMARC is missing or still at p=none, with the exact record for whoever manages the domain.

Do Google and Yahoo require DMARC?

Only for bulk senders. Since February 1, 2024, Google requires anyone sending close to 5,000 or more messages a day to personal Gmail accounts to have SPF, DKIM and DMARC, with p=none allowed. Its FAQ says the count is per domain, subdomains included, and mail to Google Workspace accounts isn't covered. Every sender to Gmail needs SPF or DKIM.

Yahoo has had matching bulk-sender rules since February 2024 for Yahoo-hosted addresses, AOL included, but names no volume. A small office's own mail is far below 5,000 a day. A newsletter sent from your domain to a big list could cross it.

Troubleshooting

Why do my emails go to spam?

Failed authentication is the cause you can fix in DNS. Open a message that landed in spam, view its original headers, and find the Authentication-Results line. If it shows dmarc=fail, see whether spf= or dkim= failed and fix that sender. If all three pass, the cause is elsewhere.

Why does our own email bounce after we set p=reject?

A service you use isn't aligned. Go back to p=quarantine or p=none, find it in the reports, set up DKIM for your domain there, then step back up.

Why am I not getting any DMARC reports?

Check that the record has rua=mailto: with a working address. A report address at another domain needs an authorizing record there, per Microsoft; reporting services set that up.

Do I need DMARC on a domain we don't use for email?

Yes. Microsoft recommends v=DMARC1; p=reject; and the SPF record v=spf1 -all, with no DKIM, for a domain that sends no mail. In our sample, 53 domains had no MX record, so they receive no email, and 51 of those had no DMARC record. Microsoft 365 customers who don't send from their onmicrosoft.com domain should add the same DMARC record to it in the admin center under Settings, Domains.

Does DMARC stop fake emails from lookalike domains?

No. DMARC covers your domain and its subdomains. A lookalike domain someone else registered has its own DNS. If a client or staff member acted on one, follow what to do after clicking a phishing link.

More in this topic

Crashcart runs IT and security for small offices for $35 a computer a month. Start a 14-day free trial.