DMARC Checker
Read the public DMARC policy record without sending mail or accessing a mailbox.
Run DMARC Checker
Public targets only. No credentials, changes or anonymous active security testing.
What this check does
- Public _dmarc TXT lookup
- DMARC record presence
- Published policy text
What it does not prove
- No aggregate-report history
- No proof of actual SPF/DKIM alignment
- No guaranteed inbox delivery
Interpret the returned state
PASS means the endpoint returned evidence within its named boundary. REVIEW, WARN and FAIL must be read alongside that evidence; they are not automatically vulnerabilities. UNKNOWN means the observation could not establish the answer.
Why it matters
A published policy is one input to a receiver’s authentication decision. Monitoring and enforcement have different purposes; p=none is not automatically a vulnerability.
Common review questions
- No DMARC record is visible.
- An unexpected policy should be reviewed against the authorised mail configuration.
- Moving straight to reject without alignment evidence can block legitimate mail.
Interpret policy before changing enforcement
Record the policy and hostname observed. A missing record is a review question, not permission to alter DNS.
Compare the policy with your rollout plan. A monitoring policy can be intentional while teams investigate mail streams.
Use authorised mail and report evidence before increasing enforcement. A public TXT lookup cannot tell whether every real sender aligns.
Read the related technical guide →When a fuller review would help
ZENQIX can combine relevant observations, explain priorities and recommend next steps. No automatic remediation, penetration test or complete-security guarantee is included.
Explore Website AssuranceFrom ₹4,999