DMARC Record Lookup

Check if a domain has DMARC configured and analyze its email security settings. This tool helps you understand how other domains protect their email infrastructure.

How to Use

1. Enter the domain name you want to check (e.g., example.com)

2. Click "Lookup DMARC Record" to fetch the domain's DMARC configuration

3. Review the results to understand the domain's email security policies

4. Use the information to assess the domain's email security stance

Other tools: SPF Record Generator | SPF Record Lookup | SPF Record Verification | DKIM Record Verification | DMARC Record Generator | DKIM Record Generator | DKIM Record Lookup | DMARC Record Verification

DMARC Record Lookup

Enter a domain name to check its DMARC record and analyze its email security configuration.

Verify Protection

Check if domains you receive email from have proper DMARC protection in place.

Analyze Policies

Understand how other organizations configure their DMARC policies and reporting.

Learn Best Practices

See real-world examples of DMARC implementation and learn from them.

Understanding DMARC Lookup Results

Common DMARC Tags

v=DMARC1

The DMARC version tag. Always set to DMARC1.

p=

The policy for handling failed messages (none/quarantine/reject).

rua=

Email addresses that receive aggregate reports.

ruf=

Email addresses that receive forensic reports.

pct=

Percentage of messages subject to filtering.

sp=

Policy for subdomains of the organization.

What to Look For

Policy Strength

Look at the 'p=' tag to understand how strictly the domain handles email authentication:

  • 'p=none' indicates monitoring only
  • 'p=quarantine' means suspicious emails go to spam
  • 'p=reject' shows the strongest protection

Implementation Stage

The 'pct=' value shows how many emails are subject to the policy:

  • Lower percentages suggest testing phase
  • 100% indicates full implementation
  • Missing percentage defaults to 100%

Note: The absence of a DMARC record doesn't necessarily mean the domain is unsafe, but it does indicate that the domain owner hasn't implemented this additional layer of email security.