954-539-5678Free audit
Menu

Cybersecurity · Email security

Set up DMARC the safe way, from p=none to p=reject

A step-by-step guide to SPF, DKIM and DMARC for Microsoft 365 and Google Workspace, including how to read reports and when to tighten the policy.

List every service that sends mail

Monitor first, then quarantine

Reach p=reject without lost mail

Get your free Technology Health Assessment

30 minutes of data collection, your report the next day, yours to keep with no obligation. Or pick a time now. Or call 954-539-5678.

The short answer

To set up DMARC, publish a DNS TXT record at _dmarc.yourdomain.com with a value such as v=DMARC1; p=none; rua=mailto:[email protected]. Before you do, make sure every service that sends mail as your domain passes SPF or DKIM with your domain. Then read the daily aggregate reports, fix any legitimate sender that fails, and tighten the policy in stages: p=none, then p=quarantine, then p=reject. Microsoft’s own guidance recommends exactly this gradual rollout so you do not block real mail.

Done in that order, most small businesses can reach p=reject in a few weeks to a few months without anyone noticing, except the people trying to spoof you.

What SPF, DKIM and DMARC each do

  • SPF lists the servers allowed to send mail for your domain. It is one TXT record at the root of your domain.
  • DKIM adds a cryptographic signature to each message. Receivers check it against a public key in your DNS.
  • DMARC ties them together. It checks that the domain that passed SPF or DKIM aligns with the From address people see, tells receivers what to do when a message fails, and sends you reports.

A message passes DMARC if either SPF or DKIM passes and aligns. That is why a newsletter tool can pass SPF with its own domain and still fail DMARC for yours.

Why it matters in 2026

Google requires anyone sending more than 5,000 messages a day to Gmail users to have SPF, DKIM and a DMARC record with at least p=none, plus alignment. Microsoft announced similar requirements for high-volume senders to Outlook.com, Hotmail and Live addresses starting in May 2025. Even if you send far less, DMARC at enforcement is what stops criminals from sending invoices that appear to come from your exact domain to your customers and vendors.

Step 1: list everything that sends as your domain

Most DMARC problems come from senders nobody remembered. Check for:

  • Microsoft 365 or Google Workspace
  • Marketing platforms such as Mailchimp, Klaviyo or HubSpot
  • Your CRM, help desk and e-signature tools
  • Accounting and invoicing software that emails invoices
  • Your website’s contact forms and online store
  • Scanners, copiers and line-of-business apps that send alerts

Step 2: fix SPF

You may have only one SPF record per domain. A typical Microsoft 365 record looks like v=spf1 include:spf.protection.outlook.com -all, and Google Workspace uses include:_spf.google.com. Add an include for each other service that sends from your domain’s envelope address.

  • Stay under SPF’s limit of 10 DNS lookups. Each include counts, and nested includes count too.
  • Remove services you no longer use.
  • Put bulk mail on a subdomain, such as news.yourdomain.com, so its reputation does not affect staff email. Microsoft recommends this.

Step 3: turn on DKIM everywhere

  • Microsoft 365: in the Defender portal, open the DKIM settings for your custom domain, publish the two CNAME records it shows (selector1 and selector2) at your DNS host, then enable signing.
  • Google Workspace: in the Admin console, generate a DKIM key (2048-bit if your DNS host allows it), publish the TXT record, then click Start authentication.
  • Other senders: each marketing, CRM or invoicing platform has a domain authentication page. Complete it so the platform signs with your domain, not its own.

DKIM matters more than SPF for DMARC because it survives forwarding, which breaks SPF.

Step 4: publish DMARC in monitor mode

At your DNS host, add a TXT record with the host name _dmarc and a value like:

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

In GoDaddy, for example, open your domain’s DNS records, choose Add, select TXT, enter _dmarc as the name and paste the value. Other hosts work the same way. Have only one _dmarc record. Use a shared mailbox or a DMARC reporting service for the rua address, not someone’s inbox. Skip the ruf (forensic) tag at first; Microsoft notes many receivers do not send those reports and they can be noisy.

Is your email domain easy to spoof today? Our free Technology Health Assessment takes about 30 minutes of data collection. The next day you get a plain-language report on your cybersecurity and IT operations, including email security, with a short list of next steps in order. It is yours to keep, with no obligation. Book your assessment.

Step 5: read the reports

Aggregate reports arrive as compressed XML files, typically once a day from each receiver. A reporting tool turns them into a table of sending sources. For each source, ask three questions:

  1. Is this sender ours? Unknown sources with all failures are usually spoofing. That is DMARC doing its job.
  2. Does SPF or DKIM pass? If neither passes for a legitimate tool, add it to SPF or set up DKIM.
  3. Does it align? A classic pattern Microsoft highlights is SPF passing for the vendor’s domain while alignment fails. Fix it by having the vendor sign DKIM with your domain or use your domain for the bounce address.

Expect some failures from forwarded mail and mailing lists. Those are normal. Review reports weekly during rollout, then monthly once stable.

Step 6: move to quarantine, then reject

When every legitimate source passes and aligns for a few weeks, change the policy to p=quarantine. You can ramp with the pct tag, for example pct=10, then 25, 50 and 100, to apply the policy to a growing share of failing mail. Watch reports and listen for users who say a partner did not get a message.

After a stable period at quarantine, change to p=reject. Receivers that honor it will refuse spoofed messages outright. Microsoft suggests starting with low-volume subdomains and doing the main domain last.

Do not forget these

  • Parked domains. Domains you own but never send from should have v=DMARC1; p=reject; and an SPF record of v=spf1 -all.
  • Subdomains. A DMARC record covers subdomains unless they have their own. Use the sp tag if you need a different policy.
  • Your onmicrosoft.com domain. If you use Microsoft 365, add a DMARC record for it in the admin center.
  • New tools. Make domain authentication part of setting up any service that sends email.

Common mistakes that break mail

  • Two SPF records, which makes SPF fail entirely
  • Jumping straight to p=reject without reading reports
  • Forgetting the invoicing or payroll system that emails clients
  • Leaving DKIM off in Microsoft 365 for a custom domain
  • Strict alignment settings (aspf=s or adkim=s) that fail subdomain senders
  • Sending reports to a single person’s mailbox, where they pile up unread

If mail does start bouncing after a policy change, step back one stage, find the failing source in the reports, fix it and move forward again. A one-level rollback costs nothing.

Email security, including authentication, is part of JLB USA’s cybersecurity services. If you use Microsoft 365, pair this with the controls in our guide to Microsoft 365 security settings for small businesses.

Keep reading

Book it now

Pick a time for your 30 minutes

Choose a slot that suits you. We’ll confirm by email, collect the data with you on the call, and send your report the next day. It’s free, and the report is yours to keep with no obligation.

Prefer to talk first? Call 954-539-5678, or send the form and we’ll contact you.

Questions we hear

What is a good starting DMARC record?

Start with v=DMARC1; p=none; rua=mailto:[email protected] published as a TXT record at _dmarc.yourdomain.com. It changes nothing about delivery but starts sending you daily aggregate reports.

How long should I stay at p=none?

Long enough to see every legitimate sender pass and align, usually a few weeks of clean reports. Microsoft recommends a gradual rollout through p=none and p=quarantine before p=reject, rather than a fixed number of days.

Do I need DMARC if I send fewer than 5,000 emails a day?

Google’s DMARC requirement applies to bulk senders, but any business benefits. DMARC at quarantine or reject stops criminals from sending messages that appear to come from your exact domain.

Why does DMARC fail when SPF passes?

Usually because of alignment. A third-party tool may pass SPF using its own domain, which does not match your From address. Have the tool sign DKIM with your domain or use your domain for its bounce address.

How do I add a DMARC record in GoDaddy?

Open your domain’s DNS records, choose Add, select TXT, enter _dmarc as the name, paste your DMARC value and save. Make sure only one _dmarc record exists.

Related services

Want to know where your business stands?

Pick a time for my free assessmentCall 954-539-5678