NetToolsPAKISTAN

DMARC Record Checker

Check your domain’s DMARC (Domain-based Message Authentication, Reporting, and Conformance) record to understand how receiving email servers are asked to handle messages that fail email authentication.

A DMARC record is published in your domain’s DNS settings. It works with SPF and DKIM to help domain owners identify unauthorized email use and reduce domain spoofing.

EMAIL AUTHENTICATION · DNS

Check a domain's DMARC record

Look up the public DNS TXT record, read the policy, and spot configuration issues. No account required.

Enter a domain only. We query _dmarc.yourdomain.com, not a website URL.

DNS results may be cached for up to 5 minutes. This is an independent utility and is not an official PTCL or email-provider service.

How to Check a DMARC Record

Once the checker is available, you will be able to:

  1. Enter your domain name, such as example.com.
  2. Select Check DMARC to request a DNS lookup.
  3. View the published DMARC TXT record.
  4. Review the configured policy and reporting addresses.
  5. Check any configuration warnings before making changes to your DNS settings.

DMARC records are normally published as TXT records at _dmarc.example.com, where example.com represents your domain.

What Is a DMARC Record?

DMARC is an email authentication standard that lets domain owners publish instructions for receiving email servers.

It builds on two authentication methods:

  • SPF (Sender Policy Framework): Helps verify whether a sending server is authorized by a domain.
  • DKIM (DomainKeys Identified Mail): Uses a cryptographic signature to help verify that a message was signed by the relevant domain and has not been altered in ways that break the signature.

DMARC also checks whether an authenticated domain aligns with the domain displayed in the message’s From address.

An email can pass DMARC when at least one of SPF or DKIM passes with the required domain alignment.

Understanding DMARC Policies

The p tag specifies the domain owner’s requested policy for messages that fail DMARC authentication.

PolicyMeaning
p=noneRequest no special delivery action; useful for monitoring
p=quarantineRequest that failing messages be treated as suspicious
p=rejectRequest rejection of messages that fail DMARC

Receiving email providers ultimately control message handling. Publishing a policy does not guarantee every receiving server will behave identically.

For most organizations, monitoring legitimate email traffic before introducing stricter policies helps avoid disrupting business email.

Example of a DMARC DNS Record

A basic example is:

v=DMARC1; p=none; rua=mailto:dmarc@example.com

Here is what each part means:

  • v=DMARC1 identifies the record as a DMARC policy.
  • p=none requests monitoring without a special delivery action for failing messages.
  • rua=mailto:dmarc@example.com specifies an address for aggregate authentication reports.

The example is illustrative, not a DNS record configured for your domain. Replace the reporting address with one you control or one supplied by your DMARC reporting service.

Common DMARC Record Settings

DMARC records can contain several settings that influence authentication policy and reporting.

TagPurpose
vDMARC protocol version
pPolicy for the domain
ruaAggregate reporting destinations
rufMessage-specific failure reporting destinations
spPolicy for existing subdomains
npPolicy for non-existent subdomains
adkimDKIM domain alignment mode
aspfSPF domain alignment mode
tDMARC policy test mode
psdPublic suffix domain designation

The current DMARC specification is RFC 9989, published in May 2026. Older examples may contain legacy tags such as pct, ri, or rf, which were removed from the updated specification.

Common DMARC Configuration Problems

No DMARC Record Found

The requested DNS name may not have a published DMARC TXT record.

Check the DNS hostname, confirm that the record has been saved, and allow for DNS caching after changes.

For subdomains, the absence of a direct DMARC record does not necessarily mean that no policy applies. A policy published at a parent or organizational domain may apply under DMARC’s policy discovery rules.

Multiple DMARC Records

Publishing multiple DMARC policy records at the same DNS name can prevent receivers from reliably applying the intended policy.

Combine the required settings into one valid policy record rather than publishing competing records.

Invalid DMARC Syntax

Incorrect tag names, unsupported values, malformed reporting addresses, or an invalid version identifier can interfere with DMARC processing.

The record should begin with v=DMARC1, followed by properly separated tag-value pairs.

DMARC Policy Is Too Strict

Switching directly to p=reject without checking all legitimate email services can cause genuine messages to be rejected.

Review the services sending email for your domain, configure SPF and DKIM alignment, and examine DMARC reports before applying stronger enforcement.

DMARC Reports Are Not Arriving

Receiving servers do not necessarily send every type of requested report. Reporting also depends on supported reporting mechanisms, valid destinations, and authorization requirements for third-party report receivers.

Confirm your reporting address and the receiving service’s configuration.

Why DMARC Matters for Pakistani Businesses and Website Owners

A professional email address associated with a business domain can be misused in impersonation attempts.

Whether you manage an online store, educational website, company email service, or WordPress website in Pakistan, DMARC can help you monitor authentication results and express a handling policy for unauthorized messages.

It is especially useful when multiple services send email on behalf of the same domain, including business mailboxes, order notifications, contact forms, and newsletters.

However, DMARC is not a complete anti-phishing solution. It does not prevent every deceptive email, block lookalike domains, or guarantee that legitimate emails will reach the inbox.

What Should You Do After Checking Your DMARC Record?

If no suitable DMARC policy is configured, first identify all legitimate services that send mail using your domain.

Next, verify their SPF and DKIM configuration and confirm that at least one method achieves DMARC alignment.

Use aggregate reports to identify authentication problems before moving toward stricter enforcement, where appropriate.

A DNS record lookup shows published configuration. It cannot establish whether every email sent from your domain successfully passes DMARC. That requires examining actual authentication results or suitable reports.

Technical reference: IETF RFC 9989 – Domain-Based Message Authentication, Reporting, and Conformance.