Is your DMARC policy ready for your next send?

Check the public DMARC record, policy posture, and alignment caveats before a campaign, migration, or provider review.

01$0Free scan

Check the public sender-auth records mailbox providers expect.

02$0Shareable action plan

Keep one URL with evidence, owner steps, and decisions.

03$49$49 fix plan

Add human review, provider context, and verification steps.

Optional. Most first scans can run with just the domain.

Checks Gmail, Yahoo, and Microsoft sender requirementsPublic DNS onlyNo mailbox login needed

Example result72/100Needs attention

Review DMARC policy strength before a high-volume send.

Public DNS evidence: DMARC/SPF/DKIM status and caveats are visible before you pay.
Owner-ready next step: The audit adds provider context and a verification checklist.

Get the exact fix plan for your domain.$49 readiness audit: prioritized owner actions, DNS evidence, and verification checks.

Get my $49 fix plan View sample

Sender readiness cockpitExample action plan

Public DNS workspace

Overall sender readiness

72/100

Needs attention

Sample output: one warning and one fail mean this domain is not campaign-ready yet.

DMARCPass

SPFPass

DKIMPass

MXPass

BIMIWarning

MTA-STSFail

Fix workspace preview

The scan becomes a focused work surface: evidence, owner action, verification, and the paid context a public lookup cannot infer.

HighDMARC

Review DMARC policy strength before a high-volume send.

Evidence: Evidence: a monitoring-only policy can satisfy visibility needs, but enforcement requires aligned legitimate senders.
Verify after change: Re-scan _dmarc after DNS propagation and confirm aligned SPF or DKIM senders before enforcement.
Paid audit adds: Policy sequence, starter record review, alignment questions, and enforcement caveats.

Get my fix plan

What this checker reviews after the scan

The scan looks for a DMARC TXT record at _dmarc.yourdomain.com, reads the policy tag, and highlights reporting tags when present. It does not inspect private inbox placement, complaint rates, or every sending platform that may use your domain.

Google and Yahoo both describe DMARC as part of their bulk sender requirements. Microsoft has also published DMARC guidance for Microsoft 365 domains and announced Outlook.com high-volume sender authentication requirements.

DMARC FAQ

Is p=none enough?

It can satisfy some initial requirements, but it is a monitoring policy. Review aggregate reports and move carefully with your DNS or email administrator before increasing enforcement.

Does DMARC guarantee inbox placement?

No. DMARC is an authentication and policy signal. Mailbox providers also consider reputation, user engagement, complaints, content, volume, and other signals.

Why does alignment matter?

DMARC depends on the visible From domain aligning with the domain that passes SPF or DKIM. Misalignment can make otherwise-authenticated mail fail DMARC.