Published DMARC record
Reads the live TXT record and distinguishes a missing record, multiple records and an incomplete lookup, when the check reports them.
Built for agencies and B2B sales teams.Built for lead generation agencies and B2B sales teams. Manage contacts, automate email sequences, and handle replies in one workspace.
Start free →Check your domain's published DMARC TXT record. Understand its policy, SPF and DKIM alignment settings, reporting destinations, and configuration warnings before changing DNS.
Example: DMARC policy found
Use a domain such as example.com. The checker looks up the DMARC TXT record at the matching _dmarc hostname, here _dmarc.example.com.
Read the published policy, alignment settings, reporting destinations and any supported validation findings.
If the lookup cannot be completed, retry before treating the result as a missing record.
Reads the live TXT record and distinguishes a missing record, multiple records and an incomplete lookup, when the check reports them.
Whether the domain requests no enforcement, quarantine or reject. p=none requests no enforcement.
Shows the published adkim and aspf modes, not whether a message aligned.
Shows whether rua and ruf are configured.
A published DMARC policy is a request to receiving servers, not an unconditional delivery guarantee.
| Policy | What it requests | Notes |
|---|---|---|
| p=none | No enforcement | No additional handling based on DMARC failure. Commonly used while reviewing authentication and reporting data. Aggregate reports need a rua destination. |
| p=quarantine | Suspicious-mail treatment | Receivers are asked to treat messages failing DMARC as suspicious, such as placing them in a spam folder. |
| p=reject | Rejection | Receivers are asked to reject messages that fail DMARC. They make their own final handling decisions. |
DMARC checks whether at least one successful authentication mechanism is aligned with the visible From domain.
SPF alignment compares the authenticated SPF identity with the From domain. DKIM alignment compares the DKIM signing domain with it.
These tags set relaxed (r) or strict (s) alignment. Relaxed allows domains that share the same organizational domain. Strict requires an exact match.
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.
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.
List every legitimate service that sends email using your domain.
Set up and verify SPF and DKIM for each sending system.
Begin with a monitoring policy and review available aggregate reports. Resolve legitimate failures.
Consider quarantine or reject only when the evidence supports enforcement. Not every domain should move straight to p=reject.
Confirm the record is published under the correct _dmarc hostname. A confirmed missing record is different from a DNS timeout or incomplete lookup.
Multiple policy records at the same DNS name can prevent correct policy discovery. Review your DNS and publish one appropriate policy.
A p=none policy with no rua address does not request aggregate reports. Add a reporting destination if you need visibility.
A published record does not prove messages authenticate correctly. Use SPF, DKIM and actual message headers or reports to investigate.
Check whether an explicit subdomain policy applies or the parent policy is inherited. Advanced setups may use sp or np.
Temporary DNS failures are shown as unknown or incomplete, not as a confirmed invalid or missing record.
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.
Re-check the record when you edit authentication.
Confirm alignment before moving to quarantine or reject.
Review client or acquired domains quickly.
A DMARC checker looks up a domain's published DMARC policy and helps explain its record, configuration settings, and supported validation findings.
Usually as a DNS TXT record at _dmarc.example.com for example.com. You enter the plain domain and the tool builds the hostname.
These values express different handling preferences for mail failing DMARC. None requests no enforcement, quarantine requests suspicious-mail treatment, and reject requests rejection.
No. Aggregate reporting needs an appropriate rua destination, and receivers must support and send the reports.
They define strict or relaxed DKIM and SPF domain-alignment requirements.
Not by DNS lookup alone. A message-level DMARC assessment requires authentication and alignment information for that email.
No. A message can pass DMARC with one successful, aligned authentication mechanism. Using both provides additional authentication paths.
Multiple policy records at the same DNS name can prevent valid policy discovery. Review them and publish a single appropriate policy.
RUA requests aggregate reports. RUF requests message-specific failure reports, which some receivers do not support.
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.
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.
No. Authentication is only one factor in email delivery and inbox placement.
After changes to DNS, sending services, SPF or DKIM setup, or when authentication issues appear.
Healthy authentication protects your domain. Clean contacts protect your sender reputation. Cleaner outreach starts with better data.