[{"data":1,"prerenderedAt":42},["ShallowReactive",2],{"$f231jo1vtc3iye":3},{"title":4,"seoTitle":5,"description":6,"route":7,"kind":8,"toolKey":9,"intro":10,"indexable":11,"sections":12,"related":39},"DMARC Checker","DMARC Checker | nslookup.online","Inspect published DMARC DNS policies, RFC 9989 discovery paths, policy fields and configuration issues without claiming message authentication results.","\u002Fdmarc-checker\u002F","tool","dmarc","Inspect a published policy and the DNS path used to discover it.",true,[13,20,26,33],{"id":14,"title":15,"paragraphs":16,"code":19},"read-answer","Check a DNS policy, not an email message",[17,18],"Enter the author domain itself, without _dmarc or an email address. The tool queries _dmarc at that name and, if necessary, follows the RFC 9989 DNS tree-walk rules to discover an inherited policy.","DMARC authentication also depends on SPF or DKIM results and identifier alignment for an actual message. This form has none of that message context and never returns a message-level DMARC pass or fail.","_dmarc.example.com. 300 IN TXT \"v=DMARC1; p=none\"\n\nDOCUMENTATION EXAMPLE — not a live DNS response",{"id":21,"title":22,"paragraphs":23},"discovery","Current policy discovery",[24,25],"This implementation targets RFC 9989, published in May 2026, rather than relying exclusively on the superseded RFC 7489 public-suffix-list method. It retains queried owners and selected policy records as evidence.","The tree walk is bounded, respects psd boundary tags and does not guess an organizational domain from the last two labels. Subdomain policy selection distinguishes an existing name from NXDOMAIN. A transient error makes discovery incomplete.",{"id":27,"title":28,"paragraphs":29},"policy","Policy intent and configuration findings",[30,31,32],"none is monitoring intent, not a syntax failure. quarantine and reject request handling of messages that fail DMARC, but the receiving system’s actual action is not measured here.","Duplicate candidates, duplicate tags and malformed values are reported. Unknown tags are retained and ignored rather than automatically rejected. Legacy pct is not applied as an enforcement percentage under RFC 9989.","If policy fields are invalid but a syntactically valid aggregate-report URI exists, the RFC 9989 monitoring fallback is explained. Finding a record is not a blanket green security certificate.",{"id":34,"title":35,"paragraphs":36},"questions","What remains outside this check",[37,38],"External reporting-destination authorization, report delivery, DKIM keys, message identifier alignment and real receiving-system behavior are not checked. Report URIs are never requested, and no test email is sent.","Use the displayed raw records and discovery path when reviewing a finding. For a production mail change, validate with your mail platform and the current standard, then monitor actual authentication reports.",[40,41],"\u002F","\u002Fguides\u002Fnslookup-command\u002F",1792661399017]