DMARC record explained: syntax, tags and examples
A DMARC record is a DNS TXT record published at _dmarc on your domain (for example _dmarc.example.com). It starts with v=DMARC1 and tells receiving mail servers what you'd like them to do with mail that claims to come from your domain but fails DMARC, and where to send reports about it. A typical first record looks like this: v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com.
That one line is the whole record. The rest of this article explains where it lives, how the syntax works, what each tag means, and what real records look like at each stage. If you want the step-by-step for publishing one, use our DMARC setup page. How DMARC uses the record to judge mail is in What is DMARC and how it works.
What is a DMARC record, in practice?
Your SPF and DKIM records say which servers and signing keys may send for you. A DMARC record sits on top of them. It asks receivers to check that SPF or DKIM passed for a domain that aligns with the address in the visible From header, and it states your policy for mail where neither does.
A few things the DMARC record doesn't do:
- It doesn't authenticate anything by itself. Without working SPF and DKIM for every sender, it only tells you who is failing.
- Its policy is a request. Receivers make the final call.
- A
p=nonerecord doesn't change how mail is handled. It's for monitoring, and you only get reports if you includerua.
Where the DMARC TXT record lives
| Field | Value |
|---|---|
| Type | TXT |
| Name / Host | _dmarc (the full name is _dmarc.example.com) |
| Value | v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com |
The record never goes at the root of your domain. It goes at the _dmarc name. Many DNS hosts want only _dmarc in the host field and add your domain automatically. If you type the full name into one of those, you end up with _dmarc.example.com.example.com, and receivers never find the record. Check how your DNS host handles names before you save. If your DNS is on Cloudflare, see Add SPF, DKIM and DMARC records in Cloudflare DNS.
You publish the record at your DNS host, not inside your mail platform. Neither the Google Admin console nor Microsoft 365 has a place to manage DMARC records for your custom domains. Platform specifics are in DMARC for Microsoft 365 and DMARC for Google Workspace.
There must be exactly one DMARC record at that name. If a receiver finds more than one, it discards all of them, and your domain behaves as if it had no DMARC record at all. When you change reporting vendors or policies, edit the existing record instead of adding a new one.
DMARC record format and syntax
A DMARC record is a list of tag=value pairs separated by semicolons:
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com
The rules that matter:
v=DMARC1comes first. It must be the first tag and must be written exactly like that. If it's missing, misspelled (v=dmarc1), or not first, receivers ignore the whole record.- Put
psecond. Onlyvhas a fixed position, butvthenpis the safest order. - Always include
p. The current DMARC standard lists it as recommended rather than required, and it's unsettled how a record withoutpshould be handled. Don't leave that to chance. - Unknown tag names are ignored. A misspelled tag name won't break the record, but it won't do anything either.
- Spaces after semicolons are fine. A trailing semicolon is fine too.
- Plain text only. Curly quotes or stray characters pasted from a word processor or chat tool can make the record unreadable.
- Long values can be split. Some DNS hosts break long TXT values into several quoted strings. Receivers join them back together in order, so that's not a second record.
DMARC tags at a glance
| Tag | What it sets | Default if left out |
|---|---|---|
v |
Version. Always DMARC1, always first. |
none (required) |
p |
Policy for failing mail: none, quarantine, or reject |
always include it |
rua |
Where aggregate reports go (mailto: addresses, comma-separated) |
no aggregate reports |
ruf |
Where failure reports go | no failure reports |
sp |
Policy for subdomains that exist | same as p |
np |
Policy for subdomains that don't exist in DNS | sp, or p if no sp |
adkim |
DKIM alignment: r relaxed or s strict |
r |
aspf |
SPF alignment: r relaxed or s strict |
r |
fo |
When to generate failure reports (needs ruf) |
0 |
t |
Testing flag: t=y asks receivers to apply your policy one level more gently |
n |
psd |
Public suffix flag, for registries and similar | u |
Most domains only need v, p, and rua. Add the others when you have a reason. Every tag, its values, and its edge cases are covered in DMARC tags explained.
A note on rua: the value has to start with mailto:. A bare address won't work. If the reporting address is on a different domain from the one publishing the record (common when a reporting service collects your reports), that other domain has to publish an authorization record, or receivers won't send to it. See rua, ruf, and report authorization.
DMARC record examples
All examples use example.com. Replace the domain and reporting address with your own.
Monitoring: p=none
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
This is the starting point. Mail is handled as before, and receivers that send reports start sending them, normally within about a day. Use a shared mailbox or a reporting service for rua, not a personal inbox, because report volume can be high.
Have SPF and DKIM working for your senders first (How to write an SPF record, DKIM selectors and DNS records), and give new SPF and DKIM records about 48 hours before you add DMARC.
Quarantine
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com
You're asking receivers to treat failing mail as suspicious. What that looks like differs between receivers. See What happens to failing mail under each policy. Move here only after your reports show every legitimate source passing with alignment.
Reject
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com
You're telling receivers that failing mail is clearly unauthorized. This is a per-domain decision, not a default. A domain at p=reject needs aligned DKIM signing on its mail, not SPF alone, and a domain used for everyday staff email shouldn't use p=reject as its end state. Readiness checks are in When you are ready for p=reject, and the staged route is in A safe rollout: p=none to quarantine to reject.
Different policy for subdomains: sp
v=DMARC1; p=quarantine; sp=reject; rua=mailto:dmarc-reports@example.com
A record on the organizational domain also covers subdomains that don't publish their own record. Here, example.com is at quarantine and its subdomains are at reject. A subdomain that publishes its own record, such as _dmarc.news.example.com, uses that record instead:
_dmarc.news.example.com TXT "v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com"
sp only works in the organizational domain's record. If you care about names that don't exist in DNS, set np explicitly so the fallback doesn't depend on how a receiver reads the record. Inheritance and np are covered in Subdomain policy (sp).
Strict alignment: adkim and aspf
v=DMARC1; p=quarantine; adkim=s; aspf=s; rua=mailto:dmarc-reports@example.com
Strict alignment needs an exact domain match. With the relaxed default, a DKIM signature from mail.example.com aligns with a From address at example.com; with adkim=s, it doesn't. Many third-party senders sign or bounce from a subdomain, so don't copy strict settings from an example until you've checked every sender. Relaxed is typically enough. See Relaxed vs strict alignment and Identifier alignment for SPF and DKIM.
More than one report address
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com,mailto:dmarc@reports.example.net
Separate addresses with a comma, each with its own mailto:. The second address is on another domain, so reports.example.net needs an authorization record.
A domain that never sends mail
v=DMARC1; p=reject;
For a parked or registered-only domain that sends no mail, p=reject is a reasonable record, paired with the SPF record v=spf1 -all and no DKIM records. The caution about going to reject is about domains that send mail, not parked ones. Adding rua is still useful if you want to see who is spoofing the domain.
An old record you should clean up
v=DMARC1; p=quarantine; pct=100; ri=86400; rua=mailto:dmarc-reports@example.com
pct, ri, and rf are historic. The current DMARC standard removed them, but you'll still see them in older guides and some provider examples. Remove them. Taking out pct=100 doesn't lower your policy, because leaving pct out always meant 100. How to phase in enforcement without pct is in pct is historic.
Common DMARC record mistakes
- The domain added twice in the host field, giving
_dmarc.example.com.example.com. - Two DMARC records at
_dmarc, often left behind after switching vendors. Both are discarded. v=DMARC1not first, or typed in lower case.ruawithoutmailto:, or an external report address with no authorization record.- Jumping to
p=rejectbefore reports show every legitimate sender aligned. - Publishing DMARC before DKIM signing is turned on. Google Workspace and Microsoft 365 custom domains don't sign with your domain until you enable it.
sp=noneunder an enforcedp, which leaves subdomains open.t=yleft in place after testing.
Check the record
After saving, query it from a command line:
dig TXT _dmarc.example.com
nslookup -type=TXT _dmarc.example.com
You should see exactly one answer, starting with v=DMARC1. If you see two, or none, fix that before anything else.
What comes next
Once the record is published, the work is in the reports: find every source sending as your domain, fix the ones that fail alignment, and then move from p=none toward enforcement. BIMI comes after that. It needs your domain at quarantine or reject, with subdomains covered too. Supporting inboxes may then show your logo; BIMI doesn't change delivery. See What is BIMI and why DMARC comes first.
Free DMARC account
Turn raw DMARC reports into a readable dashboard
Point your rua address to our platform and read the results by sender and source instead of opening XML files.
- Results grouped by sending source
- SPF, DKIM and alignment results per sender
- The original XML reports are still there to download
FAQ
Where do I add a DMARC record?
At your DNS host, as a TXT record named _dmarc on your domain.
What's a safe first DMARC record?
v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com, with your own domain and reporting address.
Can I have two DMARC records?
No. If a receiver finds more than one at _dmarc, it discards all of them.
Do I need a DMARC record for every subdomain?
Not usually. The record on your main domain covers subdomains that don't have their own. Use sp or a subdomain record only when a subdomain needs a different policy.
Should I include pct=100?
No. The current standard removed pct. Leaving it out means the policy applies in full.