DMARC: Record, Policy and Alignment
DMARC tells receivers what to do with email that fails SPF and DKIM for your From domain. See a DMARC record, p=none vs quarantine vs reject, and fixes.
DMARC (Domain-based Message Authentication, Reporting and Conformance) is a DNS record that connects SPF and DKIM to the From address people see. It tells receiving servers what to do with mail that claims to come from your domain but fails both checks, and asks them to send you reports about who is sending as you. The record lives at _dmarc under your domain. The current standard is RFC 9989, which replaced RFC 7489 in May 2026.
How DMARC works
The receiving server reads the domain in the message’s From header. That’s the domain DMARC protects.
It looks up the DMARC record at
_dmarcunder that domain. If there isn’t one, it walks up to the parent domain, so_dmarc.acme.comcoversmail.acme.comunless the subdomain has a record of its own.It checks SPF and DKIM. The message passes DMARC if at least one of them passes for a domain that aligns with the From domain.
If neither aligned check passes, the receiver applies your policy in
p=. The policy is a request: receivers can still make their own call (RFC 9989, section 5.4).Receivers that send reports mail a summary, usually once a day, to the address in
rua=.
DMARC alignment
Alignment is what makes DMARC more than SPF and DKIM on their own. SPF passes for the Return-Path domain and DKIM for the d= domain in the signature, and either one can belong to your email service instead of you. DMARC only counts a pass for a domain that matches the From domain.
Relaxed alignment, the default, accepts any domain under the same organizational domain, so a DKIM signature for mail.acme.com aligns with a From address on acme.com. Strict alignment (adkim=s or aspf=s) needs an exact match. RFC 9989 notes that nearly all domain owners find relaxed alignment enough.
Passing domain | From domain | Relaxed | Strict |
|---|---|---|---|
|
| Aligned | Aligned |
|
| Aligned | Not aligned |
|
| Aligned | Not aligned |
|
| Not aligned | Not aligned |
DMARC record example and tags
Here is a DMARC record for acme.com that asks receivers to quarantine failing mail and send reports.
Tags are separated by semicolons. Only v=DMARC1 is required, and it has to come first. A record without p= is read as p=none, and receivers skip tags they don’t recognize.
Policy | What you ask receivers to do | When to use it |
|---|---|---|
| Deliver failing mail as usual, and report it | While you find every service that sends as you |
| Treat failing mail as suspicious, usually the spam folder | Once reports show your own mail passing |
| Refuse failing mail | Once quarantine has run without surprises |
A few other tags are worth knowing. sp= sets a policy for subdomains, and np=, new in RFC 9989, sets one for subdomains that don’t exist, which spoofers like to make up. t=y marks a policy as a test and replaces the old pct= tag, which RFC 9989 removed. ruf= asks for a report on each failing message, which many large mailbox providers don’t send.
From p=none to p=reject
Publish
p=nonewith arua=address. Mail is delivered as before, and reports start arriving within a day or two.Read the reports for two to four weeks. Each row is a sending server with its SPF and DKIM results. Find every service that sends as you, and fix the ones that don’t align, usually by setting up DKIM for your domain in that service. The raw reports are XML files, so a DMARC report tool makes them much easier to read.
Move to
p=quarantineonce your own mail passes.Move to
p=rejectafter a few more weeks of clean reports, typically one to three months after you started.
If Loops is the only service sending as your domain, you can move faster, because there’s no forgotten sender to break. Google and Yahoo require a DMARC record from bulk senders, and p=none meets that requirement. BIMI, which shows your logo in supporting inboxes, needs p=quarantine or p=reject. A checker that says “DMARC policy not enabled” is flagging p=none, and the DMARC record generator explains that warning and builds the record for each step.
Common DMARC errors
Two records at
_dmarc. When a receiver finds more than one DMARC record at the same name, it discards all of them, so the domain acts as if it had no policy. Merge them into one.The record is at the wrong host. It’s a TXT record at
_dmarc.acme.com, not at the root. In most DNS editors the host is_dmarc, without your domain.Moving to reject too early. A service you forgot, such as billing or support, starts getting blocked. Read the reports first.
SPF and DKIM pass, but DMARC fails. Neither passing domain aligns with the From domain. Most often the service signs DKIM with its own domain.
A subdomain record weakens the root. A record at
_dmarc.mail.acme.comreplaces the root policy for mail.acme.com. If the root saysp=rejectand the subdomain saysp=none, the subdomain is unprotected.No reports. Without
rua=, receivers send nothing. A report mailbox on a different domain also has to authorize the reports with a DNS record of its own.Syntax slips.
v=DMARC1not first, commas instead of semicolons, curly quotes pasted from a document, or apct=tag left over from an old guide. A record that doesn’t start withv=DMARC1is ignored.
To see what’s published, look your domain up in the email DNS checker. It follows the record up to the parent domain the way a receiver does. If SPF is the part that fails, the SPF record checker counts its lookups and lists every include.
What Loops sets up for your domain
When you add a sending domain in Loops, such as mail.acme.com, the Settings → Domain page lists a DMARC record with the SPF, DKIM and MX records: a TXT record at _dmarc.mail.acme.com with v=DMARC1; p=none;. Copy it into your DNS provider, or import the zone file Loops gives you, then click Verify Records.
With the records in place, mail sent through Loops passes DMARC on both checks. DKIM signs with your sending domain, an exact match for the From domain. SPF passes for envelope.mail.acme.com, which aligns under relaxed alignment because both names end in acme.com. Keep adkim and aspf relaxed, the default, so the envelope subdomain counts.
If _dmarc.acme.com already has a record, you don’t need the Loops one. The root record covers the sending subdomain. Add it only if you want a different policy for mail.acme.com, and remember that it then replaces your root policy for that subdomain.
The steps for each DNS provider are in Setting up your domain, and DMARC and DKIM setup covers the recommended path from p=none to p=reject. For everything beyond authentication, see the email deliverability guide.
FAQ
What is DMARC?
DMARC (Domain-based Message Authentication, Reporting and Conformance) is a DNS record that connects SPF and DKIM to the From address. It tells receiving servers what to do with mail that fails both checks for your domain, and asks them to send you reports.
What does a DMARC record look like?
It’s a TXT record at _dmarc under your domain, such as _dmarc.acme.com. A simple one reads v=DMARC1; p=none; followed by a rua= tag with the mailbox for reports. v=DMARC1 has to come first.
What is the difference between p=none, p=quarantine and p=reject?p=none asks receivers to deliver failing mail as usual and only report it. p=quarantine asks them to treat it as suspicious, which usually means the spam folder. p=reject asks them to refuse it. Receivers can still apply their own rules.
Is p=none enough?
It meets Google’s and Yahoo’s requirement that bulk senders publish a DMARC record, and it gets you reports. It doesn’t stop anyone from spoofing your domain. Move to p=quarantine and then p=reject once the reports show your own mail passing.
Why does DMARC fail when SPF and DKIM pass?
Because neither passed for your From domain. SPF can pass for a service’s own Return-Path domain, and DKIM can pass for a service’s own signing domain. DMARC only counts a pass that aligns with the From domain, so set up DKIM for your domain in each service.
Does a DMARC record at the root domain cover subdomains?
Yes. A record at _dmarc.acme.com covers mail.acme.com and every other subdomain that doesn’t have a record of its own. A subdomain record replaces the root policy for that subdomain, and the sp= tag sets a separate policy for subdomains.
Do I need a DMARC record to send with Loops?
Loops gives you one during domain setup: v=DMARC1; p=none; at _dmarc under your sending domain. If your root domain already has a DMARC record, it covers the sending subdomain, and you only need the Loops record if you want a different policy there.
Related: SPF, DKIM, Email authentication, Email deliverability best practices, BIMI, Inbox placement, Bounce rate, Phishing.