Skip to content

Free DMARC checker

Check your domain's DMARC record, understand its policy and see what needs attention.

Reads public DNS only. Nothing is sent to your mail servers. What happens to the domain you enter

Example report

example.com
  • 1 Low
  • 1 Information
  • DMARC is in monitoring modeLow

    The DMARC policy is p=none, which reports on failing mail but does not stop it.

    Next step

    Once reports show your legitimate mail passing, move to p=quarantine and then p=reject.

    View fix guide

  • DMARC reports are not requestedInformation

    The DMARC record does not ask for aggregate reports (rua), so nobody hears about mail that fails.

    Next step

    Add rua=mailto: with an address or a DMARC reporting service.

    View fix guide

What the DMARC check looks at

  • The record

    Find the record at _dmarc, or the organisational record that covers a subdomain.

  • The policy

    See whether failing mail is rejected, quarantined or only reported.

  • Coverage

    Spot testing mode, or a pct below 100, relaxing the policy.

  • Reporting

    Check that aggregate reports are requested, so failures reach you.

Optional tags such as adkim, aspf, ruf and fo are shown with what they mean but are not judged.

Understand the issue and your next step

Each finding explains what we found, why it matters and what you can change. Start with the issues that need attention, then open the evidence when you want the detail.

  1. Enter your domain
  2. Review the findings
  3. Follow the fix guides
Example finding

DMARC is in monitoring modeLow

The DMARC policy is p=none, which reports on failures but does not stop them.

v=DMARC1; p=none

Common DMARC issues you can put right

  • DMARC is in monitoring modeLow

    Your policy can help you understand who sends mail for your domain, but it does not ask receivers to quarantine or reject messages that fail DMARC. Review legitimate senders before changing enforcement.

    Read the fix guide

  • No DMARC policyMedium

    Without a record, each receiver decides for itself what to do with mail forged in your name. Publish a policy that asks for reports first, and read them before you enforce.

    Read the fix guide

  • DMARC reports are not requestedInformation

    A policy without a rua address still works, but nobody hears about mail that fails. Ask for aggregate reports to see who sends as your domain.

    Read the fix guide

  • DMARC is not fully enforcedInformation

    The DMARC record relaxes its own policy: t=y (testing) asks receivers to apply the next milder policy, or pct below 100 asks them to apply it to only part of failing mail.

    Read the fix guide

  • DMARC record has errorsMedium

    The DMARC record could not be parsed.

    Read the fix guide

Keep watch after you've fixed it

Ironfang Security rechecks a verified domain every week or every day and tells you what changed: new findings, fixes and certificates nearing expiry.

Free during the preview. Domain verification required.

  1. NewIssue detected
  2. FixedConfirmed by recheck
  3. ReopenedDetected again

How the check works

  • The TXT record at _dmarc.<domain>, and for a subdomain without one, the record at its organisational domain, which then applies to it.
  • Whether there is exactly one DMARC record and whether it parses: v=DMARC1 first, then a valid p= policy and, if present, a valid sp= policy.
  • The policy that applies: none, quarantine or reject, with the subdomain policy where one is set.
  • Whether the record relaxes its own policy: t=y (testing, from RFC 9989) or a pct below 100 (from RFC 7489, which RFC 9989 replaced in May 2026 and which receivers that follow it ignore).
  • Whether aggregate reports are requested with a rua=mailto: address.

Reading a result

A DMARC record tells receivers what the owner of a domain wants done with mail that claims to come from it but fails both SPF and DKIM alignment. Without one, each receiver decides for itself, and mail forged in your name is judged only on its other signals.

p=none asks receivers to deliver failing mail as normal and only report it. It is the right place to start, while reports show which services send for you, but it protects nothing. p=quarantine asks for failing mail to be treated as suspicious, usually sent to spam, and p=reject asks for it to be refused.

A passing result means a valid record with an enforcing policy for all mail and reporting switched on. A finding names the one thing to change, and Ironfang's check reference explains why it matters.

What it does not do

  • The check reads public DNS through public resolvers. It does not see your mail flow, so it cannot tell whether legitimate senders already pass SPF and DKIM alignment; aggregate reports tell you that before you enforce.
  • It does not send or receive email and does not test how a particular receiver applies the policy.
  • Optional tags such as adkim, aspf, ruf and fo are shown with what they mean but are not judged.

What happens to the domain you enter

The check runs from Ironfang Security's published scanner address with the same low-impact limits as a scan. Nothing you enter is stored or logged. A result is reused for five minutes, and a certificate log search for an hour, so a repeat check is quick and the domain is not checked again.

Guides

A few things worth knowing

What does p=none mean?
It asks receivers to deliver mail that fails DMARC as normal and send you reports about it. Use it while you find every service that sends as your domain, then move to quarantine and reject.
Does a subdomain need its own DMARC record?
No. A subdomain without a record is covered by its organisational domain's record, using the sp= policy if it sets one and p= otherwise. A subdomain that sends differently can have its own.
Will moving to p=reject stop my own mail?
Only mail that fails both SPF and DKIM alignment. Read the aggregate reports first: any legitimate service that fails needs SPF or DKIM set up for your domain before you enforce.