Free DMARC lookup

Free DMARC checker and DMARC domain lookup

Run a free DMARC lookup to fetch the live TXT record for any domain, inspect policy tags, and review warnings before enforcement, migrations, or deliverability changes. Use it as a fast DMARC checker when you need the real record, not just documentation.

Run a free lookup

Fetch the live DMARC record for a domain

Enter the root domain. The lookup checks the live TXT value at _dmarc, surfaces warnings, and highlights the policy and reporting tags that matter most.

Best fit

Use this before policy changes and during auth incidents

DMARC lookups are most useful when the live policy matters right now: before tightening enforcement, after DNS edits, or while investigating why a sender path is no longer trusted.

Check the record before moving from p=none to enforcement
Verify live DNS after provider or DNS migrations
Confirm aggregate reporting tags before relying on report data

Upgrade path

Move from one lookup to ongoing sender-domain monitoring

One-shot DMARC lookups are useful for triage. Production teams usually need recurring verification, history, and a shared view of auth drift across domains.

Monitor DMARC, SPF, and DKIM together
Track changes over time instead of relying on manual spot checks
Route sender-auth issues to owners before campaign windows

Open auth monitoring

Key details

Primary use

Live DMARC lookup

Inspect the exact DMARC TXT value currently visible in public DNS.

Policy signal

p= mode

See whether the domain is still monitoring-only or actually enforcing.

Reporting

rua + tags

Confirm aggregate report routes and alignment settings before tightening policy.

Output

Record + issues

Get the raw record, parse warnings, and a practical launch verdict in one view.

When to use this tool

See the live record

Confirm what receivers can actually read from DNS before assuming a change is in place.

Review enforcement posture

Spot whether the domain is still on p=none or already moving toward quarantine or reject.

Catch setup mistakes fast

Warnings and parse issues surface before policy changes create deliverability or spoofing confusion.

What this returns

A DMARC lookup should answer more than whether a record exists

The useful output is the combination of live DNS visibility, policy details, report destinations, and warnings that tell a team whether the record is ready for the next enforcement step.

Record

Live TXT value

Review the exact DMARC string receivers will evaluate.

Policy

p=none or reject

Check whether the domain is only observing or actually enforcing.

Reports

rua coverage

Confirm aggregate-report routing before relying on DMARC reporting workflows.

Warnings

Parse issues

Catch malformed tags or weak rollout choices before they create confusion later.

Operational use

Best used as a release and policy-change checkpoint

Searchers usually want a DMARC lookup because the policy is changing or because trust is already in question. Treat this as a release-control step, not a passive reference page.

Before enforcement

Confirm tags, reporting routes, and live visibility before moving from monitoring-only toward quarantine or reject.

After DNS changes

Re-run the lookup after migrations so the team knows the expected policy is actually visible to mailbox providers.

During spoofing or alignment incidents

Use the live record as the first shared source of truth before chasing downstream alignment or provider-specific symptoms.

Related tools

DMARC checker

Get the broader DMARC policy and alignment workflow when you need context beyond the raw lookup.

Open tool

DMARC record validator

Validate required tags when you want a pass-fail checklist for the published record.

Open tool

DMARC record generator

Generate a clean DMARC record when the current one needs to be rebuilt.

Open tool

Email header analyzer

Confirm real messages show the DMARC verdict and alignment outcomes you expect.

Open tool

FAQ

What is the difference between a DMARC checker and a DMARC lookup?

A DMARC lookup fetches the live DNS record and shows the exact value, warnings, and parse results. A broader DMARC checker workflow also helps interpret policy mode, reporting setup, and sender-alignment implications.

When should teams run a DMARC lookup?

Run it before and after DNS changes, before tightening enforcement, and during deliverability or spoofing incidents when you need to confirm the live policy quickly.

Does a valid DMARC record mean enforcement is strong?

Not always. A record can be syntactically valid while still using a monitoring-only policy such as p=none. Teams should review both validity and enforcement posture.

What should I do after a failed DMARC lookup?

Fix syntax first, confirm the record is published at _dmarc.yourdomain, then re-run the lookup after propagation. If spoofing or alignment issues continue, pair this with SPF, DKIM, and header analysis.