Skip to content
DMARC Pulse

Learn

What is a DMARC record? Format, tags and example

What is a DMARC record? A TXT record at _dmarc that states your policy for mail failing DMARC and where reports go. Format, tags and samples.

What it is

A DMARC record is a TXT record (a text entry in DNS) that states how you want receiving mail servers to treat messages that use your domain in the From address and fail DMARC. It can also ask those servers for reports. So what is a DMARC record in practice? One line of text, published at the name _dmarc under your domain. For example.com, the full name is _dmarc.example.com.

The record expresses a preference. Under RFC 9989, the DMARC standard published in May 2026, each receiving server makes the final decision.

What is DMARC?

DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. It checks the domain people see in the From address and builds on two older standards. SPF lets a domain authorize the hosts that may use its name. DKIM adds a signature that the receiver validates with a public key from the signer's domain.

A message passes when SPF or DKIM validates a domain that aligns with the From domain. In the default relaxed mode, aligned means both share an organizational domain, usually the one you registered.

How receivers find the record

A receiver reads the domain in the From header and looks up _dmarc under it. If no valid record answers, it walks up the DNS tree. So _dmarc.example.com covers news.example.com when the subdomain has no record of its own.

DMARC record format and syntax

A DMARC record is a list of tag=value pairs separated by semicolons. v=DMARC1 must come first, in exactly that case, or receivers must ignore the whole record. Google's setup guide also says v and p must be listed first, so put p second. Receivers ignore tags they do not know.

The main tags:

Tag What it sets If you leave it out
v Version, always DMARC1 The record is ignored
p Policy for failing mail: none, quarantine or reject Counts as p=none if rua has a valid address; otherwise no DMARC processing. Google requires p
rua Where aggregate reports go No aggregate reports
ruf Where per-message failure reports go No failure reports
sp Policy for existing subdomains Subdomains use p
np Policy for subdomains that do not exist Uses sp, then p
adkim, aspf DKIM and SPF alignment: r relaxed or s strict r
t Test mode: y asks for a policy one level lower n

RFC 9989 replaced RFC 7489, adding np, psd and t and removing pct, rf and ri.

Example

This illustrative record starts DMARC in monitoring mode for example.com. Replace the domain and use a mailbox you control.

TXT
v=DMARC1; p=none; rua=mailto:dmarc@example.com

Create it as a TXT record named _dmarc at your DNS host. If _dmarc already holds a record, edit that one instead of adding a second.

  • p=none states no preference, and RFC 9989 says it must not change how receivers handle mail.
  • rua= asks for aggregate reports at that mailbox. RFC 9989 says receivers should send them at least once every 24 hours.

A stricter version changes only the policy:

TXT
v=DMARC1; p=quarantine; rua=mailto:dmarc@example.com

p=quarantine says you consider failing mail suspicious. Google describes it going to the recipient's spam folder.

Caution: do not start here. A legitimate sender that is not aligned yet can land in spam. Move up only after your reports show every legitimate sender passing.

Build your own with the DMARC generator, or follow how to set up DMARC.

Common mistakes

  • Publishing two records at one name. Receivers discard them all. Merge them into one. Caution: merging makes the policy active again, so check p= before you save.
  • Leaving out mailto:. Google says each rua address must include it. Separate several addresses with commas.
  • Sending reports to another domain without authorization. If the report address sits in a different organizational domain, that domain must publish a TXT record such as example.com._report._dmarc.reports.example.net containing v=DMARC1. Otherwise receivers ignore the address.
  • Treating p=none as protection. It asks for no action, so spoofed mail gets no policy from your record.
  • Jumping straight to p=reject. Caution: failing mail can be refused outright, including mail forwarded by others or sent by a service you forgot. Start at p=none and fix each legitimate sender your reports reveal. Google suggests at least a week there. RFC 9989 says domains whose users may post to mailing lists should not publish p=reject; if they still want it, they should first spend at least a month at p=none and as long at p=quarantine. Any domain using p=reject must sign with DKIM. See how to choose a policy.

Check it now

Look up and validate a DMARC record

Frequently asked questions

Where do I add a DMARC record?
At your DNS host, as a TXT record named _dmarc under your domain. For example.com, the full name is _dmarc.example.com. Some hosts add the domain for you, so check the saved name afterwards.
Is a DMARC record required?
The standard leaves it to you: a domain that publishes no record does not take part. Mailbox providers set their own rules. Gmail requires DMARC from senders of more than 5,000 messages a day to Gmail accounts and accepts a policy of none. Yahoo requires bulk senders to publish at least p=none.
What happens if my domain has no DMARC record?
If no record is found for the domain or further up the DNS tree (its organizational domain or public suffix), receivers must not apply DMARC to its mail, and you get no aggregate reports. Each receiver's own filtering still decides what happens to the message. To fix it, see no DMARC record found.
Can a domain have more than one DMARC record?
Not at the same name. When a lookup returns more than one, receivers discard them all. A subdomain can publish its own record, and that record then applies to the subdomain in place of the parent's.
Does a DMARC record stop spoofing?
Only exact use of your domain in the From address, and only when your policy asks for action and the receiver honors it. RFC 9989 says DMARC does not address look-alike domains or abuse of the display name. With p=none, receivers handle failing mail as they did before.
Is the pct tag still valid?
RFC 9989 removed pct, and IANA lists it as historic. The RFC reports that values other than 0 and 100 were usually not applied accurately. The new t tag takes over part of its role: t=y asks receivers to apply a policy one level below the published one. Google's and Microsoft's help pages still describe pct.

Sources consulted

RFC 9989 §4.1: DMARC Basics
checked 2026-11-08

Related pages

Keep it healthy

Know the moment something breaks

Point your DMARC reports to DMARC Pulse and see who sends email as your domain, what fails and why — with a calm alert when anything changes.

Free plan: 1 domain, no credit card.