Check your domain.

Free DNS check · No signup · See sample results

Public DNS only. Sender inventory, report coverage and real external tests are required before changing policy.

Example only. Illustrative records for a demonstration domain. No DNS lookup has been performed.

example.org

p=none

DNS checked 22 Nov 2026, 23:30 UTC

Published
Monitorp=none
Quarantinep=quarantine
Rejectp=reject

DMARC record

Published

_dmarc.example.org · TXT

v=DMARC1; p=none; rua=mailto:reports@example.org; adkim=r; aspf=r
Policy
none
DKIM alignment
r
SPF alignment
r
Reports
mailto:reports@example.org

Reporting & SPF

Public DNS
Aggregate reportingConfigured in DNS

reports@example.org

Published destination only. Check actual report arrival, destination authorisation where required, and reporting coverage.

SPF at example.orgPublished
v=spf1 include:_spf.example.org -all
MX records1 found

Public DNS cannot establish that real messages pass SPF/DKIM alignment. DKIM requires known selectors or message headers.

Findings

  • Info
    Monitoring policy

    p=none collects evidence but does not request blocking.

  • Info
    Reporting address published

    The DNS record names a report destination; receipt and correct processing need separate verification.

Your next action

Confirm reports are arriving, then classify senders

Complete the sending-platform inventory and investigate low-volume, forwarded and unknown sources before any enforcement decision.

Go to this step

Your implementation checklist

Use this to track the work. The Missing Manual explains each step in full.

0 of 24 checks recorded in this browser

01Prepare
02Discover
03Configure platforms
04Confirm readiness
05Introduce quarantine
06Full quarantine
07Move to reject
08Monitor and maintain

Manual checklist. Ticking an item does not verify readiness or authorise a policy change. Keep your supporting evidence and obtain the necessary change approval. Progress is stored only in this browser.