
Setting up DMARC means publishing one TXT record named _dmarc on your domain, then spending a few weeks reading reports before you turn on enforcement. The record most businesses should start with is v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com. It doesn’t change how any mail is delivered. It asks receivers to send you daily reports showing every server that sent mail using your domain and whether that mail passed.
Once the reports show all your real senders passing, you change p=none to p=quarantine, then to p=reject. That’s when DMARC starts protecting you: mail forged in your name goes to spam or bounces.
The part that takes time is making SPF or DKIM pass for your domain on every service that sends as you. Skip that and enforcement blocks your own invoices and newsletters.
The short version
- Make sure SPF and DKIM are set up for your domain; Google says to wait 48 hours after doing so.
- Create a shared mailbox or group to receive reports, such as dmarc-reports@yourdomain.
- Publish a TXT record with host
_dmarcand valuev=DMARC1; p=none; rua=mailto:plus that address. - Read the aggregate reports for at least a week and fix every legitimate sender that fails.
- Move to
p=quarantine, watch the reports again, then top=reject. - Give domains you never send from
v=DMARC1; p=reject;straight away.
Before you start: SPF, DKIM and alignment
DMARC doesn’t authenticate anything itself. It looks at the SPF and DKIM results and asks one more question: does the domain that passed match the domain in the From address the reader sees? That match is called alignment, and a message passes DMARC if either SPF or DKIM passes and aligns.
- SPF alignment compares the envelope sender (the return-path, shown as
smtp.mailfromin headers) with the From domain. - DKIM alignment compares the signing domain (the
d=value, shown asheader.d) with the From domain.
By default alignment is relaxed, meaning subdomains of the same domain count as a match. Microsoft’s examples show how that plays out:
| From address | Domain that passed | Relaxed (default) | Strict |
|---|---|---|---|
| user@example.com | example.com | Aligned | Aligned |
| user@example.com | bounces.example.com | Aligned | Not aligned |
| user@example.com | example.onmicrosoft.com | Not aligned | Not aligned |
| user@example.com | a vendor’s own domain | Not aligned | Not aligned |
The third row catches a lot of Microsoft 365 tenants. Until you turn on DKIM for your custom domain, Microsoft signs with your onmicrosoft.com domain, which doesn’t align. Your mail can still pass DMARC through SPF, but forwarding breaks SPF, and then nothing aligns. Turn on DKIM first. If SPF isn’t in place yet, start with our SPF record setup guide.
Step 1: create the record
Set up a reports mailbox
Reports arrive as compressed XML attachments, often one per receiving company per day. Microsoft and Google both say to send them to a shared mailbox or a group rather than someone’s personal inbox, because the volume adds up fast. If you’ll use a DMARC reporting service, it gives you its own rua address instead.
If reports go to an address on a different domain, that other domain must publish a record authorizing it, or receivers won’t send them. For example.com reporting to an address at example.net, example.net needs a TXT record at example.com._report._dmarc with the value v=DMARC1;. Reporting services normally handle this for you.
Publish it
- Export or screenshot your DNS zone first so you can undo the change.
- Add a TXT record with the host
_dmarc. Many DNS hosts add your domain to the end automatically; check the saved record doesn’t read_dmarc.example.com.example.com. - Value:
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com - Make sure there’s only one
_dmarcTXT record. Microsoft lists duplicates and syntax errors as causes ofdmarc=permerror. - Check it with
nslookup -type=TXT _dmarc.example.comor a free DMARC checker.
The tags worth knowing
| Tag | What it does | Typical value |
|---|---|---|
v | Version; must be first | DMARC1 |
p | Policy for mail that fails | none, then quarantine, then reject |
rua | Where aggregate reports go | mailto: address |
sp | Separate policy for subdomains; if left out they follow p | Usually omitted |
adkim / aspf | Relaxed (r, default) or strict (s) alignment | Leave relaxed unless you have a reason |
ruf | Per-message failure reports | Optional; Gmail doesn’t support it and Microsoft 365 doesn’t send them |
pct | Apply the policy to only part of failing mail | See the note on the 2026 standard below |
Step 2: read the reports
Raw reports are hard to read by eye. A DMARC reporting service, free or paid, turns them into a list of sending sources with pass and fail counts. Microsoft notes that not every receiver sends reports, so expect partial coverage. Whatever tool you use, you’re looking for the gap between authenticated and aligned.
| What the report shows | What it means | What to do |
|---|---|---|
| Microsoft 365 or Google servers, aligned pass | Your staff mail is fine | Nothing |
| A service you recognize, SPF pass but not aligned | It sends from its own bounce domain | Set up DKIM with your domain at that service, or a custom return-path on your domain |
| A service you recognize, DKIM pass but not aligned | It signs with its own domain | Turn on custom-domain DKIM in that service’s settings |
| A service you recognize, SPF and DKIM both fail | It was never authorized | Add it to SPF if the vendor says to, and set up its DKIM |
| Mailing list or forwarding servers, failing | Forwarding changed the message or the path | Usually normal; DKIM on your own mail helps it survive forwarding |
| Unknown IPs, high volume, all failing | Someone is sending as your domain | This is what enforcement will stop |
Google suggests a week at p=none is usually enough for daily reports to cover all your mail. In a small office, also think about mail that only goes out monthly or quarterly, such as statements or tax-season letters, and make sure you’ve seen it pass before you enforce.
Step 3: move to quarantine, then reject
- Quarantine. Change the record to
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com. Receivers now put failing mail in spam. Keep reading reports; the failures you see should only be forgeries and forwarding. - Reject. When quarantine has run cleanly, change
p=quarantinetop=reject. Failing mail is refused outright. - Keep the reports on. New tools get added all the time. The reports are how you find out before customers stop getting invoices.
Microsoft suggests starting enforcement on low-volume subdomains and leaving the main domain until last. For a typical small business with one domain, that simply means: don’t rush the main domain.
A note on pct and the 2026 standard
For years, the usual advice was to ramp up with pct, applying quarantine to, say, 10% of failing mail first; Google’s rollout guide still uses 10% as an example starting point for a small organization. In 2026 the IETF published RFC 9989, which replaces the original DMARC specification (RFC 7489), drops pct, adds a t=y test flag, and makes the np tag (a policy for subdomains that don’t exist) part of the standard. Existing v=DMARC1 records keep working, and receivers won’t all switch at once. For a small domain, the simplest path is to skip partial percentages: go straight from none to quarantine once reports are clean.
Rather have a technician sort it out?
If your DMARC reports are full of senders you don’t recognize, a technician can connect remotely with your permission, sort the legitimate services from the spoofers and plan your move to enforcement. A GoProIT technician can connect remotely, with your permission, and fix it while you watch. $59 per fix, Mon–Fri 8am–8pm ET.
Subdomains, parked domains and onmicrosoft.com
- Subdomains inherit. Unlike SPF and DKIM, the DMARC record on example.com covers every subdomain without its own record, including ones that don’t exist. To give a newsletter subdomain a gentler policy while you set it up, publish a separate
_dmarc.newsrecord. Each sending subdomain still needs its own SPF and DKIM. - Parked domains. For domains you own but never send from, Microsoft recommends
v=DMARC1; p=reject;with no report address needed, together with an SPF record ofv=spf1 -all. - The onmicrosoft.com domain. Microsoft maintains its SPF and DKIM, but you add its DMARC record yourself in the Microsoft 365 admin center: Settings > Domains, select the onmicrosoft.com domain, open DNS records and choose Add record, with type TXT, name
_dmarcand a value such asv=DMARC1; p=rejectif you don’t send from it. - Google Workspace. There’s nothing to switch on in the Admin console. DMARC is set entirely at your DNS host.
What enforcement can break
Most surprises after moving to quarantine or reject come from a few predictable places:
- Website forms that send “from” your address through the web host’s server.
- Copiers and line-of-business apps sending directly from the office without signing.
- Forwarding and mailing lists that change the subject or add a footer, which breaks DKIM.
- Your own outbound mail in Microsoft 365. Microsoft routes outbound messages that fail DMARC at the destination through its high-risk delivery pool when your policy is quarantine or reject. Good alignment avoids that.
On the receiving side, Microsoft 365 acts on other domains’ DMARC policies through the Honor DMARC record policy when the message is detected as spoof setting in anti-phishing policies. If a legitimate sender you need is failing, Microsoft prefers marking a forwarding service as a trusted ARC sealer over blanket allow rules.
If your customers report bounces after a change, our guides to the 550 5.7.26 bounce and emails going to spam help you trace which sender broke.
When to get help
DMARC is low risk at p=none and high stakes at p=reject. Get a second pair of eyes before enforcing if:
- The reports show sources nobody in the office can identify.
- A key service can’t sign with your domain and you need a subdomain plan.
- You’ve had a spoofing or invoice-fraud incident and need enforcement quickly but safely.
- Nobody has access to the DNS host, or records were lost in a website move.
If you’d rather not do it yourself, publishing the starter record and reviewing the first reports is a typical $59 remote fix. Taking a domain all the way to p=reject, along with SPF, DKIM and MFA, is what our email security and 2FA setup covers, and our Microsoft 365 management keeps it maintained as you add tools.
Common questions
What is a good DMARC record to start with?
Start with v=DMARC1; p=none; rua=mailto: followed by an address you control, published as a TXT record at _dmarc on your domain. It enforces nothing, so no mail is affected, but receivers send daily reports about who sends as your domain. Leave alignment at the relaxed default and skip forensic reports until you need them.
Will setting up DMARC stop my emails being delivered?
Not at p=none, which only asks for reports. Delivery changes when you move to quarantine or reject. Then any service that sends as your domain without aligned SPF or DKIM gets its mail sent to spam or refused. That is why you read reports first and fix every legitimate sender before you enforce.
How long should I stay at p=none?
Google suggests one week of daily reports is usually enough to see all your mail streams before moving to quarantine. Many small businesses wait a little longer, so monthly statements and occasional mailings show up in the reports too. There’s no benefit to staying at none forever: it gives you visibility but no protection against spoofing.
What is the difference between quarantine and reject?
With p=quarantine, receivers accept mail that fails DMARC but treat it as suspicious, usually by putting it in the spam or junk folder. With p=reject, they refuse it during delivery, so it never reaches the recipient and the sender gets a bounce. Quarantine is a safer intermediate step; reject gives the strongest protection against forged mail.
Do I need a DMARC record for every subdomain?
No. Subdomains automatically follow the DMARC record on the parent domain unless they publish their own. You only add a separate subdomain record when it needs a different policy, for example a newsletter subdomain you’re still testing. Each subdomain that sends mail still needs its own SPF record and DKIM, because those are not inherited.
Is DMARC required for small businesses?
Gmail and Microsoft only require DMARC from bulk senders, around 5,000 or more messages a day to their consumer accounts, and they accept p=none. Smaller senders aren’t required to have it, but both companies recommend it. A monitoring record costs nothing, and reaching quarantine or reject is the main defense against criminals sending fake invoices in your name.