DMARC posture
DMARC posture is derived from public DNS-published DMARC records and describes visible mail-authentication policy evidence.
Why it is observed
DMARC is a visible mail-governance signal
Why it matters
DMARC presence and policy provide public context for how a domain signals handling expectations for mail that does not align with authentication checks.
What visible change may mean
A change may reflect policy tuning, staged rollout, provider migration, DNS administration, cleanup or accidental removal.
Interpretation limits
Visible DMARC is not complete mail assurance
DMARC presence, posture and policy tags describe visible public configuration. They do not establish enforcement effectiveness, alignment quality, reporting effectiveness, organisational maturity or compliance.
What .auDO observes
DMARC records and derived posture
.auDO preserves public DMARC record evidence and derives a bounded posture from that observed evidence. Within mail-posture/v1, the DMARC component distinguishes not_observed, valid, multiple, malformed and indeterminate evidence states. The individual signal remains separate from the aggregate Mail trust finding.
Technical fields
Common retained observations
DMARC presence change
Where to use this evidence
Use DMARC as a single signal or within Mail trust posture
The DMARC State page owns observed DMARC publication. Mail trust posture is the analytical owner for combined MX, SPF and DMARC aggregate findings.
Related concept
Why DMARC matters
Related signals