Built for agencies and B2B sales teams.

Start free →

Free DMARC Record Checker

Check your domain's published DMARC TXT record. Understand its policy, SPF and DKIM alignment settings, reporting destinations, and configuration warnings before changing DNS.

Reads the live TXT recordSeparates validity from strengthExplains alignment
DMARC CheckerFreeExample result
Do not enter _dmarc. We check the _dmarc host for you.
EXAMPLE

Example: DMARC policy found

v=DMARC1; p=none; rua=mailto:[email protected]; adkim=r; aspf=r
Host_dmarc.example.com
Policyp=none
Reportsrua set, ruf not set
Alignmentadkim=r (relaxed), aspf=r (relaxed)
This is a sample, not a result for your domain.
p=none requests no enforcement. It is commonly used while reviewing reports.
How it works

How to use the DMARC Checker

  1. 01

    Enter your domain

    Use a domain such as example.com. The checker looks up the DMARC TXT record at the matching _dmarc hostname, here _dmarc.example.com.

  2. 02

    Review the record

    Read the published policy, alignment settings, reporting destinations and any supported validation findings.

  3. 03

    Retry if incomplete

    If the lookup cannot be completed, retry before treating the result as a missing record.

What it checks

What the DMARC Checker checks

Published DMARC record

Reads the live TXT record and distinguishes a missing record, multiple records and an incomplete lookup, when the check reports them.

Requested policy

Whether the domain requests no enforcement, quarantine or reject. p=none requests no enforcement.

SPF and DKIM alignment

Shows the published adkim and aspf modes, not whether a message aligned.

Reporting destinations

Shows whether rua and ruf are configured.

Policies

Understanding DMARC policies

A published DMARC policy is a request to receiving servers, not an unconditional delivery guarantee.

PolicyWhat it requestsNotes
p=noneNo enforcementNo additional handling based on DMARC failure. Commonly used while reviewing authentication and reporting data. Aggregate reports need a rua destination.
p=quarantineSuspicious-mail treatmentReceivers are asked to treat messages failing DMARC as suspicious, such as placing them in a spam folder.
p=rejectRejectionReceivers are asked to reject messages that fail DMARC. They make their own final handling decisions.
Alignment and reports

SPF and DKIM alignment, and DMARC reports

DMARC checks whether at least one successful authentication mechanism is aligned with the visible From domain.

SPF and DKIM alignment

SPF alignment compares the authenticated SPF identity with the From domain. DKIM alignment compares the DKIM signing domain with it.

aspf and adkim

These tags set relaxed (r) or strict (s) alignment. Relaxed allows domains that share the same organizational domain. Strict requires an exact match.

rua and ruf

rua requests aggregate reports, which show which systems send as your domain. ruf requests message-specific failure reports, and support varies: some providers, including Gmail, do not send them. A reporting address does not guarantee every receiver sends reports.

Published configuration, not message results

A DNS-only DMARC checker can inspect published alignment settings. It cannot determine whether a particular email passed DMARC without message-level authentication data. Inspect real headers with the Email Header Analyzer.

Record tags

DMARC record tags and current standards

DMARC records use DNS TXT tag-value pairs.

TagMeaning
v=DMARC1DMARC version; required
p=Requested domain policy: none, quarantine or reject
rua=Aggregate reporting destinations
ruf=Message-specific failure reporting destinations
adkim=DKIM alignment mode
aspf=SPF alignment mode
sp=Policy for existing subdomains
np=Policy for non-existent subdomains
t=Testing-mode signal under RFC 9989

RFC 9989, published in May 2026, supersedes RFC 7489 and RFC 9091. Under it, a missing or invalid p tag in an otherwise valid policy record is treated as p=none when the record carries a valid reporting address (rua). Without one, receivers may apply no DMARC processing. An explicit p value is still recommended. The older pct, rf and ri tags are historic, and their presence does not by itself make a record invalid. This page shows the tags the check reports and does not claim to validate every RFC 9989 feature.

Step by step

A safer rollout

  1. 01

    Identify senders

    List every legitimate service that sends email using your domain.

  2. 02

    Configure and verify

    Set up and verify SPF and DKIM for each sending system.

  3. 03

    Monitor first

    Begin with a monitoring policy and review available aggregate reports. Resolve legitimate failures.

  4. 04

    Enforce on evidence

    Consider quarantine or reject only when the evidence supports enforcement. Not every domain should move straight to p=reject.

Common issues

Common problems and how to fix them

DMARC record not foundCritical

Confirm the record is published under the correct _dmarc hostname. A confirmed missing record is different from a DNS timeout or incomplete lookup.

Multiple DMARC policy recordsCritical

Multiple policy records at the same DNS name can prevent correct policy discovery. Review your DNS and publish one appropriate policy.

Monitoring without reportsInfo

A p=none policy with no rua address does not request aggregate reports. Add a reporting destination if you need visibility.

Unexpected alignment failuresReview

A published record does not prove messages authenticate correctly. Use SPF, DKIM and actual message headers or reports to investigate.

Subdomain policy confusionReview

Check whether an explicit subdomain policy applies or the parent policy is inherited. Advanced setups may use sp or np.

Incomplete DNS lookupInfo

Temporary DNS failures are shown as unknown or incomplete, not as a confirmed invalid or missing record.

What a DMARC checker cannot guarantee

Checking a DNS DMARC record does not prove that every outgoing email passes authentication. It also cannot guarantee protection against all forms of spoofing, successful inbox placement, or that every receiving server will follow the published policy.

Use cases

When to run this check

After DNS changes

Re-check the record when you edit authentication.

Before raising policy

Confirm alignment before moving to quarantine or reject.

Domain audits

Review client or acquired domains quickly.

FAQ

DMARC Checker FAQ

Still unsure? Read the DevBoxy blog or contact the team.

What is a DMARC checker?

A DMARC checker looks up a domain's published DMARC policy and helps explain its record, configuration settings, and supported validation findings.

Where is a DMARC record published?

Usually as a DNS TXT record at _dmarc.example.com for example.com. You enter the plain domain and the tool builds the hostname.

What is the difference between p=none, quarantine and reject?

These values express different handling preferences for mail failing DMARC. None requests no enforcement, quarantine requests suspicious-mail treatment, and reject requests rejection.

Does p=none automatically send DMARC reports?

No. Aggregate reporting needs an appropriate rua destination, and receivers must support and send the reports.

What do adkim and aspf mean?

They define strict or relaxed DKIM and SPF domain-alignment requirements.

Can a DNS checker confirm whether an email passes DMARC?

Not by DNS lookup alone. A message-level DMARC assessment requires authentication and alignment information for that email.

Do both SPF and DKIM need to pass?

No. A message can pass DMARC with one successful, aligned authentication mechanism. Using both provides additional authentication paths.

What happens if multiple DMARC records exist?

Multiple policy records at the same DNS name can prevent valid policy discovery. Review them and publish a single appropriate policy.

What is the difference between rua and ruf?

RUA requests aggregate reports. RUF requests message-specific failure reports, which some receivers do not support.

What is RFC 9989?

RFC 9989 is the updated IETF DMARC specification published in May 2026. It supersedes RFC 7489 and RFC 9091 and updates policy discovery and tag handling.

Why can a lookup return UNKNOWN?

The checker could not get a reliable answer, for example because of a timeout. That is different from a confirmed missing record, so retry before treating it as one.

Does a valid DMARC record guarantee inbox delivery?

No. Authentication is only one factor in email delivery and inbox placement.

When should I run the DMARC checker again?

After changes to DNS, sending services, SPF or DKIM setup, or when authentication issues appear.

Pair DNS checks with list verification.

Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.