Read a DMARC test policy in a saved DNS answer
Admin ·
When reviewing a DMARC policy change, read the requested policy and test-mode flag together. A saved answer establishes what was observed at one owner. Its effects on particular messages depend on other evidence.
Read the saved domain, subdomain and test policy
Load example and check the record. The saved owner is _dmarc.dispatch.example.test. Its HTTP-style DNS JSON contains a complete NOERROR response, one TXT answer with two character-strings, and a TTL of 300 seconds.
v=DMARC1 identifies the record. p=reject declares the requested domain policy, sp=quarantine covers existing subdomains and np=reject covers non-existent subdomains when this record applies.
t=y lowers the requested assessment by one level under RFC 9989. Expect quarantine for the domain, none for existing subdomains and quarantine for non-existent subdomains. Change t=y to t=n and check again to see the declared values without the test-mode adjustment.
Check alignment, reporting and historic tags
adkim=s requests strict DKIM alignment. The absent aspf tag uses relaxed SPF alignment. rua contains a destination for aggregate reports. A separate reporting domain can require authorization.
The example includes pct=25. RFC 9989 lists pct, ri and rf as historic. The older RFC 7489 defined sampling with pct. A percentage value and current t=y have different meanings.
RFC 9989 DMARC policy and DNS discoveryRFC 7489 former DMARC policy format and sampling
Read the missing-policy fallback with a reporting URI
Switch Input format to TXT records and paste v=DMARC1; rua=mailto:aggregate@reports.example.test. Under the fallback in RFC 9989 section 4.10.1, the report shows p=none behavior when a valid reporting URI is present.
Remove rua and check the difference. A record without valid policy values and without a valid aggregate reporting URI cannot use that fallback. For an actual message, identify the applicable owner first using DNS Tree Walk evidence.
The JSON report includes the saved source and the parsed reporting addresses. Check both before sharing a report.
Common questions
What does a captured AD flag prove?
The report shows the value supplied by the saved resolver. The tool does not perform DNSSEC validation.
Does t=y stop aggregate reporting?
Under RFC 9989, test mode changes the requested assessment for failures. Reporting rules still use the reporting tags.