DMARC Checker
Read your DMARC record tag by tag and see what it asks receivers to do with forged mail.

More checks
Subject: Updated bank details
| Receiver | What its documentation says |
|---|
This email passes DMARC, so no DMARC policy applies to it.
The DNS lookups were blocked
Try another network, or turn off the blocker for this page.
Everything this checker flags
Each problem the check can report about DMARC, and why it matters. Where a guide explains the fix, the row links to it.
A record sits at a name that repeats your domain
Your DNS panel probably added your domain after a name that already ended in it. Receivers do not look up the doubled name, so they never read this record.
DMARC is set to reject
Receivers that check DMARC are told to reject mail that fakes your domain.
No DMARC policy applies to your domain
Receivers get no instruction for mail that fakes your domain. Anyone can send email that shows your domain in the From line.
Your domain has more than one DMARC record
Receivers discard every DMARC record when they find more than one, so your domain is left with no DMARC policy.
The DMARC record of your domain is malformed
A DMARC record must start with v=DMARC1, written exactly like that, and name each tag once. Receivers ignore a record that breaks either rule, so it does not protect your domain.
The DMARC policy is missing or has an invalid value
The only values p, sp and np accept are none, quarantine and reject. With a rua address receivers fall back to none, and without one they skip DMARC for your domain.
DMARC does not stop mail that fakes your domain
The policy in force is none, so receivers get no instruction to block forged mail. Anyone can send email as your domain.
DMARC is set to quarantine instead of reject
The policy in force is quarantine, so receivers are asked to treat forged mail as suspicious, for example by putting it in the spam folder. Only p=reject, without t=y or pct, asks them to refuse it.
DMARC is in testing mode (t=y)
With t=y, receivers are asked to apply one level less than your policy: reject becomes quarantine, and quarantine becomes none.
DMARC applies to only part of the mail (pct below 100)
RFC 9989 removed pct, but receivers that still follow RFC 7489 are asked to apply your policy to the share of failing mail that pct sets, and one level less to the rest.
DMARC leaves subdomains of your domain open
The policy for subdomains that exist is the sp= value, and for subdomains that do not exist it is the np= value. Where it is none, anyone can send email as a subdomain of your domain.
Your DMARC record asks for no reports
Without rua, receivers send no aggregate reports, so you cannot see who sends mail as your domain or whether your own mail passes.
The other domain has not agreed to receive reports for your domain
Reports to another domain arrive only if that domain accepts them for you. The other domain publishes no record that does, so receivers ignore that address.
Your DMARC record asks for failure reports (ruf)
Failure reports can carry parts of real messages and personal data. Most receivers refuse to send them.
Your DMARC record has a tag that looks like a typo
Receivers ignore tags they do not know, so this part of the record has no effect.
Receivers may apply two different DMARC policies to your domain
Receivers that follow RFC 9989 take the policy from one name, which gives one policy. Receivers that still use the Public Suffix List take it from another name, which gives a different one. This check counts the weaker one.