Publish the record under the sending domain

DMARC uses a TXT record at a DNS name beginning with _dmarc. For the example domain yoursite.com, that name is _dmarc.yoursite.com.

The example below shows the syntax; it isn't ready to use for your domain. Replace the example reporting address with one you control or your reporting service supplies.

DMARC email record is missing, weak or broken

Read an example DMARC record

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

Know what each DMARC tag controls

TagPurpose
vIdentifies the DMARC version. v=DMARC1 must come first.
pSays how you'd like receivers to handle mail that fails DMARC. RFC 9989 recommends including it; an otherwise valid record without p is treated as p=none.
spSets the policy for existing subdomains when the organizational domain's record applies.
npSets the policy for nonexistent subdomains. Without it, receivers use the applicable sp or p policy.
adkimChooses relaxed or strict alignment for DKIM. The default is relaxed.
aspfChooses relaxed or strict alignment for SPF. Relaxed is the default here too.
ruaLists destinations for aggregate reports. A mailto destination is an email address for those reports.
rufRequests message-specific failure reports at the listed destinations. These are separate from aggregate reports.
foSelects the conditions for requested failure reports. It has no effect without ruf.
tSignals policy test mode. The default is n; y asks for less strict handling of failures under an enforcement policy.
psdHelps identify a public suffix domain or organizational domain during policy discovery. Its values are y, n and u, with u as the default.

Connect a passing result to the visible sender

  • DMARC needs a passing SPF or DKIM result whose authenticated domain aligns with the From domain. Relaxed alignment accepts domains within the same organizational domain. Strict alignment requires the domains to match exactly.

  • That's why mail can authenticate with a provider's unrelated domain and still fail DMARC for your own From domain. RFC 9989 explains the alignment rules.

Send aggregate reports to a working destination

  • Receivers that send aggregate reports use the destinations in rua. If a destination belongs to a different domain, that domain must authorize the reports through DNS. Publishing an address doesn't confirm that its mailbox or reporting service is ready.

  • External report destinations are explained in RFC 9990.

Frequently asked questions

Can a valid DNS record prove that a message passes DMARC?

No. A receiver has to check the message's authentication and alignment. A DNS record describes the policy to use; it isn't the result for each message you send.

Why do older examples contain ri and rf?

RFC 9989 removed those tags. ri requested a reporting interval, and rf selected a failure-report format. Use the updated standard when interpreting older examples.