2RFC 7489, "Domain-based Message Authentication, Reporting, and Conformance (DMARC)", March 2015
3Source of RFC: INDEPENDENT
4See Also: RFC 7489 w/ inline errata
9Publication Format(s) : TEXT
10Reported By: John Levine
11Date Reported: 2018-07-25
12Verifier Name: Adrian Farrel
13Date Verified: 2018-07-26
15Section 7.1, B.2.1, B.2.3, B.2.4 says:
18In particular, the "v=DMARC1" tag is
20comes back containing a tag of "v=DMARC1",
22containing at least "v=DMARC1"
26The version of DMARC being used is "DMARC1" ("v=DMARC1")
30with the value "=DMARC1".
32 % dig +short TXT example.com._report._dmarc.thirdparty.example.net
35 example.com._report._dmarc IN TXT "v=DMARC1"
39 o The version of DMARC being used is "DMARC1" ("v=DMARC1")
44In particular, the "v=DMARC1;" tag is
46comes back containing a tag of "v=DMARC1;",
48containing at least "v=DMARC1;"
52The version of DMARC being used is "DMARC1" ("v=DMARC1;")
56with the value "v=DMARC1;".
58 % dig +short TXT example.com._report._dmarc.thirdparty.example.net
61 example.com._report._dmarc IN TXT "v=DMARC1;"
65 o The version of DMARC being used is "DMARC1" ("v=DMARC1;")
70The ABNF of dmarc-record in section 6.4 says that there has to be a semicolon after v=DMARC1, but several of the examples for the _report._dmarc record are missing the semicolon.