DMARC Record Lookup Tool

Enter your domain to check your DMARC record configuration and find issues affecting your email authentication.

What Is a DMARC Record?

DMARC stands for Domain-based Message Authentication, Reporting and Conformance. It is an email authentication protocol built on top of SPF and DKIM. DMARC lets domain owners publish a policy in DNS telling receiving mail servers what to do with messages failing authentication.

A DMARC record is published as a TXT record in your DNS at _dmarc.yourdomain.com. The record contains tags defining your enforcement policy, where reports get sent, alignment requirements, and other settings. Without a DMARC record, receivers have no instructions from you and treat unauthenticated mail from your domain inconsistently.

When a receiving server gets an email claiming to be from your domain, it checks SPF and DKIM. DMARC then verifies alignment between the From header domain and the domains authenticated by SPF and DKIM. If both fail, the receiving server follows your policy: do nothing (none), send to spam (quarantine), or reject the message entirely (reject).

DMARC Tag Reference

Each DMARC record is made up of tags separated by semicolons. The table below explains every tag you will find in a DMARC record.

TagDescription
vDMARC version. Always set to v=DMARC1.
pPolicy for the organizational domain. Accepts none, quarantine, or reject.
ruaWhere aggregate reports are sent, as mailto: addresses separated by commas. Addresses on another domain need an authorization record on that domain.
rufWhere failure (forensic) reports are sent, as mailto: addresses. Many receivers do not send these.
spSubdomain policy. Inherits the p tag value if omitted.
npPolicy for subdomains that do not exist in DNS. Defined in RFC 9989. Inherits sp if omitted.
adkimDKIM alignment mode. Strict (s) requires an exact domain match. Relaxed (r) allows organizational domain match. Default is r.
aspfSPF alignment mode. Strict (s) requires an exact domain match. Relaxed (r) allows organizational domain match. Default is r.
foFailure reporting options. 0 (default) asks for a report when both SPF and DKIM fail to align. 1 asks for a report when either one fails. d and s ask for reports on DKIM or SPF failures.
rfRemoved in RFC 9989. Format for failure reports; only afrf was defined.
pctRemoved in RFC 9989 (May 2026) because receivers applied it inconsistently. Under RFC 7489 it was the percentage of failing mail the policy applies to. Use t=y for testing.
riRemoved in RFC 9989. Requested interval in seconds between aggregate reports; RFC 7489 default 86400.
tTest mode, new in RFC 9989. t=y asks receivers to apply one policy level lower than published.

Why Check Your DMARC Record?

Prevent email spoofing

A missing or misconfigured DMARC record lets attackers spoof your domain. Checking your record confirms your policy is active and enforced.

Catch configuration errors

Typos, missing tags, and invalid values break your DMARC setup. A lookup tool surfaces these problems so you fix them before they affect mail delivery.

Avoid deliverability problems

Incorrect DMARC settings cause legitimate emails to land in spam or get rejected. Verifying your record protects your sender reputation and keeps your messages reaching the inbox.

Meet compliance requirements

Regulations and industry standards increasingly require DMARC enforcement. Checking your record helps you stay compliant with policies from governments, financial institutions, and email providers.

DMARC Best Practices

1

Start with p=none

Begin with a monitoring policy (p=none) to collect data about your email traffic. You learn which services send on your behalf before you enforce restrictions. Move to quarantine or reject only after you confirm all legitimate senders pass authentication.

2

Add reporting addresses

Include a rua tag so you receive aggregate reports. A ruf tag asks for failure reports, though many receivers do not send them. Without these, you have no visibility into which senders are passing or failing authentication. Reports are the foundation for moving toward enforcement.

3

Configure subdomain policies

Use the sp tag to set a policy for subdomains. Attackers often target subdomains because they are overlooked. Set sp=reject to block unauthorized mail from subdomains unless they have their own DMARC records.

4

Align both SPF and DKIM

DMARC passes when at least one authentication method aligns. Configuring both gives you a fallback if one fails. SPF breaks on forwarded mail, and DKIM breaks when relay servers modify the message. Having both active gives you consistent coverage.

5

Step up one policy level at a time

RFC 9989 removed pct. For domains whose users post to mailing lists, it asks for at least a month at p=none, then as long at p=quarantine, comparing aggregate reports before p=reject. t=y softens a new policy by one level while you watch.

Frequently Asked Questions

Protect your domain from email spoofing

DMARC+ monitors your DMARC reports, identifies unauthorized senders, and guides you to full enforcement.

Request a 14-Day Trial