On this page
  1. The three DMARC policy values
  2. What receivers actually do with each policy
  3. Subdomains: sp and np
  4. Testing a policy: t=y and the old pct tag
  5. What a policy of reject means for forwarding and mailing lists
  6. What large domains publish in their DMARC records
  7. Which DMARC policy to use
  8. Check your DMARC policy
  9. Sources

The policy in a Domain-based Message Authentication, Reporting, and Conformance (DMARC) (opens in a new tab) record is its p tag, and it tells receivers what you want done with mail that fails DMARC: p=none asks for nothing, p=quarantine asks receivers to treat the mail as suspicious, and p=reject asks them to refuse it (RFC 9989 section 4.7 (opens in a new tab)). The receiver still makes the final call (RFC 9989 section 5.4 (opens in a new tab)). Start at none with a reporting address, and once your real senders pass Sender Policy Framework (SPF) or DomainKeys Identified Mail (DKIM) (opens in a new tab) aligned with your domain, move to quarantine, then reject, as the DMARC generator recommends.

The three DMARC policy values

Each value expresses the domain owner's view of mail that fails DMARC (RFC 9989 section 4.7 (opens in a new tab)). Microsoft's DMARC configuration page (opens in a new tab) adds what each value typically leads to.

Policy What the domain owner says What usually happens
p=none No expression of preference No suggested action; the receiver's other email protection decides
p=quarantine The mail is suspicious, though it may be valid Accepted but marked: quarantined as spam, delivered to Junk, or delivered with an identifier added
p=reject The failure clearly shows the use of the domain is not valid Rejected, and typically discarded

A record without a p tag is treated as if it said p=none. Under p=none, receivers must not change how they already handle mail (RFC 9989 section 5.4 (opens in a new tab)), so publishing it lets you receive reports without affecting delivery. The DMARC generator builds one record per stage:

v=DMARC1; p=none; rua=mailto:dmarc-reports@example.com
v=DMARC1; p=quarantine; rua=mailto:dmarc-reports@example.com
v=DMARC1; p=reject; rua=mailto:dmarc-reports@example.com

The policy only tells other mail servers how to treat email that claims to come from your domain and fails DMARC. For every other tag in the record, see DMARC record tags.

Check your domain now

See the SPF, DKIM and DMARC records your domain publishes and what to fix first. Free, no account needed.

What receivers actually do with each policy

A policy is a request. The final handling of any message is a matter of the receiver's local policy, and receivers may accept mail that fails DMARC even when the policy is reject (RFC 9989 section 5.4 (opens in a new tab)).

Microsoft publishes its own handling (opens in a new tab) for inbound mail that fails DMARC when "Honor DMARC record policy" is on: under p=quarantine the message goes to the Junk Email folder (configurable to quarantine), and under p=reject it is rejected during SMTP, the Simple Mail Transfer Protocol (opens in a new tab), with 550 5.7.1.

Google's rollout page (opens in a new tab) describes the same split: under quarantine, messages that do not pass go to the recipient's spam folder; under reject, they are rejected by receiving servers and never delivered. If you see one of these outcomes on your own mail, DMARC fail explains how to read dmarc=fail in the Authentication-Results header and how to fix SPF and DKIM alignment.

Subdomains: sp and np

p covers your domain and, unless you say otherwise, its subdomains. Two optional tags change that (RFC 9989 section 4.7 (opens in a new tab)):

  • sp sets the policy for existing subdomains of your organizational domain, not for the domain itself.
  • np sets the policy for non-existent subdomains.

If sp and np are both absent, the p policy applies to subdomains. If only np is absent, non-existent subdomains get the sp policy when there is one, and the p policy when there is not. Microsoft (opens in a new tab) puts it this way: the DMARC record for a domain covers all subdomains, including nonexistent ones, that do not have their own DMARC record. An sp tag in a record published on a subdomain is ignored, because of how receivers discover the policy.

A record can ask for a stricter policy on subdomains than on the domain itself, for example v=DMARC1; p=quarantine; sp=reject; rua=mailto:dmarc-reports@example.com. Without sp, subdomains follow p, as the DMARC generator notes. The np tag was imported into DMARC from RFC 9091 (RFC 9989 appendix C.5 (opens in a new tab)).

Testing a policy: t=y and the old pct tag

RFC 9989 adds a test mode. With t=y, the receiver is asked not to apply the policy as written: a quarantine policy is handled as none, and a reject policy as quarantine (RFC 9989 section 4.7 (opens in a new tab)). The tag does not change DMARC reports and has no effect on a policy of none.

The pct tag asked receivers to apply the policy to a percentage of mail, but operational experience showed it was usually not applied accurately unless the value was 0 or 100 (RFC 9989 appendix A.6 (opens in a new tab)), and RFC 9989 lists pct among the tags it removed, with t as the replacement for some of its functionality (appendix C.5 (opens in a new tab)). Google's rollout page (opens in a new tab) still shows a quarantine record with pct=5 and suggests raising the percentage over time, so you will meet both approaches.

What a policy of reject means for forwarding and mailing lists

p=reject can cause problems for indirect mail flows: alumni forwarders, role-based aliases and mailing lists (RFC 9989 section 7.4 (opens in a new tab)). When mail relayed by a forwarder or a role-based alias reaches the final mailbox, it will most likely fail SPF unless the relay rewrites the envelope sender, while DKIM signatures generally remain valid in these relay situations. Mailing lists are treated separately below.

That leads to two rules in the same section. A domain that publishes p=reject must not rely on SPF alone and must sign its mail with DKIM. A domain whose users post to mailing lists should not publish p=reject, and should look at its aggregate reports under p=none for at least a month, then p=quarantine for an equally long period, before deciding. The DMARC alignment guide explains what alignment compares, with six worked SPF and DKIM examples.

What large domains publish in their DMARC records

The table shows the TXT records at _dmarc.paypal.com, _dmarc.apple.com, _dmarc.github.com and _dmarc.amazon.com. TXT records are a type of Domain Name System (DNS) (opens in a new tab) record in text format.

Domain _dmarc TXT record
paypal.com v=DMARC1; p=reject; rua=mailto:d@rua.agari.com,mailto:dmarc_agg@vali.email; ruf=mailto:d@ruf.agari.com,mailto:MTc4Mzcw@ruf.vali.email
apple.com v=DMARC1; p=quarantine; sp=reject; rua=mailto:d@rua.agari.com; ruf=mailto:d@ruf.agari.com;
github.com v=DMARC1; p=quarantine; sp=reject; pct=100; rua=mailto:dmarc@github.com; ruf=mailto:dmarc@github.com; fo=1
amazon.com v=DMARC1;p=quarantine;pct=100;rua=mailto:report@dmarc.amazon.com;ruf=mailto:report@dmarc.amazon.com

apple.com and github.com ask receivers to quarantine failing mail for the domain itself and to reject it for subdomains. Treat these as examples of what is in use, not as a template.

Which DMARC policy to use

Start with p=none and a rua reporting address (RFC 9989 section 5.1.4 (opens in a new tab)). For the policy itself, p=none is enough for bulk senders: Gmail's sender guidelines (opens in a new tab) allow an enforcement policy of none, and Yahoo's best practices (opens in a new tab) ask for a valid DMARC policy with at least p=none. The policy is not the whole requirement. Gmail's guidelines also list setting up SPF and DKIM for your domain and, for direct email, require the domain in the From header to be aligned with either the SPF domain or the DKIM domain. Yahoo's requirements for bulk senders ask for both SPF and DKIM, the same From alignment, and a DMARC pass.

Then read the reports. A legitimate mail stream that fails because its authenticated identifiers are unaligned or missing has to be fixed before you publish an enforcing policy (RFC 9989 section 5.1.6 (opens in a new tab)), and depending on how often you send, that can take many months of reports (section 5.1.7 (opens in a new tab)). Google's rollout page (opens in a new tab) sets a floor: at least a week of reports with no issues before moving to quarantine for a small percentage of messages. The report analyzer shows which sources sent as your domain and whether SPF and DKIM aligned; forwarding, mailing lists and forgotten tools show up there as sources you did not expect.

Move to quarantine, then reject, as the reports stay clean. For domains whose users send routine email, RFC 9989 section 7.4 (opens in a new tab) warns that p=reject is likely to create significant interoperability issues. How to set up DMARC walks through it step by step, DMARC reports gives the four questions to ask every report, and if a checker shows the DMARC policy not enabled warning, that guide explains what it means and whether p=none affects delivery.

Check your DMARC policy

The free DemiSignal check needs no account and only reads the public DNS records of the domain you enter. For DMARC it flags a missing record, a policy of none, no reporting address, a policy that covers only part of your email, and subdomains left at none. A DNS finding shows how your domain is set up, not where a particular message landed.

Sources

Tools for this

Frequently asked questions

Does p=none protect my domain?

It asks receivers for no DMARC-specific action, so mail that fails DMARC is handled as it was before; its value is the aggregate reports that show who sends as your domain.

What happens to email under a DMARC policy of reject?

The receiver is asked to refuse mail that fails DMARC; when its Honor DMARC record policy setting is on, Microsoft rejects it during SMTP with 550 5.7.1, but every receiver makes the final decision under its own local policy.

Do subdomains need their own DMARC record?

No. Without sp or np, the p policy also applies to subdomains, and sp and np let you set a different policy for existing and non-existent subdomains.

Check your domain now

See the SPF, DKIM and DMARC records your domain publishes and what to fix first. Free, no account needed.