DMARC checker

Check a domain's DMARC record, its policy and report addresses, with the SPF and DKIM it depends on.

A domain, URL or email address; for an email address only the part after @ is used.

More options

A DKIM selector to try first, such as s1.

A few free checks a day without an account. Sign in to use your credits.

Check many at once

Bulk checks aren't unlocked yet

Bulk checks unlock after your first credit purchase or plan. Single checks work as usual.

Sign up free

What a DMARC record does

DMARC is a TXT record at _dmarc under your domain. It tells receiving mail servers two things: what to do with mail that claims to be from you but fails both SPF and DKIM in alignment, and where to send reports about the mail they see. A record looks like v=DMARC1; p=reject; rua=mailto:dmarc@example.com.

This page runs the full email check and puts the DMARC section first, with its own verdict, so you can see your policy, where the record was found and every report address at a glance. SPF and DKIM follow, because DMARC passes only when one of them passes for your domain.

The policy, step by step

The p tag sets the policy, and there are three steps:

  • none monitors. Failing mail is delivered as normal, and you get reports. It is the right first step and the wrong place to stay.
  • quarantine asks receivers to put failing mail in spam.
  • reject asks receivers to refuse failing mail outright. It is the setting that actually stops people forging your domain.

The pct tag lets you apply quarantine or reject to part of the failing mail while you roll it out, and sp sets a separate policy for subdomains. We flag a policy that only monitors, a percentage below 100 and a subdomain policy of none next to an enforcing main policy, since each one lets forged mail through.

Where we look

We read _dmarc under the name you checked. If a subdomain has no record of its own, we read the main domain's, as receivers do, and show which policy applies to the name you asked about. Two DMARC records at the same name make receivers ignore both, so we flag that too.

Reports and who may receive them

Aggregate reports, set with rua, arrive daily as XML files listing every server that sent mail as your domain and whether SPF and DKIM passed. They are how you find forgotten senders before you tighten the policy. Failure reports, set with ruf, are rarely sent nowadays.

When a report address is on another domain, that domain must publish a record agreeing to receive your reports, or receivers skip it. We check up to four external report domains and show which have agreed, so you know your reports are actually arriving.

Reading the result

The DMARC section opens with a one-line verdict in plain words, such as "mail that fails DMARC is rejected", so you know at a glance whether the policy protects you. Below it you'll find the record itself with a copy button, where it was found, the policy that applies to the name you checked, the subdomain policy, alignment, and the list of report addresses with whether each one has agreed to receive your reports. Problems are listed under the whole result as findings, worst first, and each one links to a step-by-step guide for the common DNS hosts.

The grade covers the whole email setup, not just DMARC, so a strong policy with a missing SPF record still loses points. That is deliberate: DMARC can only pass when SPF or DKIM does.

Changing your policy

Use Change this policy in the DMARC builder under the result. It opens the DMARC builder with your current settings filled in, shows the record for each rollout stage, and lists the authorization record any external report address needs.

After you publish a change, run this check again once the old record's TTL has passed, usually within an hour. Then keep reading the reports: a new sending service that isn't set up for SPF or DKIM shows up there long before anyone complains about missing mail.

If you only want the SPF part, the SPF checker shows that section first, and the full email check shows everything in the usual order.

Questions

My subdomain has no DMARC record. Is that a problem?
Not usually. Receivers fall back to the main domain's record and apply its subdomain policy (sp, or p when sp is missing). We do the same and show where the record was found.
How long should I stay on p=none?
Long enough to see every service that sends as your domain in the reports, usually two to four weeks. Then move to quarantine and, after a few quiet weeks, to reject.
Why does a report address need to agree?
So nobody can point your reports at a stranger's mailbox. Before sending reports to another domain, receivers look for a record there that says it accepts them, and most skip the address when it is missing.
Is this a separate, cheaper check?
No. It runs the full email check with the DMARC section first, because DMARC only works when SPF or DKIM pass. Through the API it costs 2 credits; in the browser you get a few free checks a day.