Read any DMARC record the way a receiving mail server does.
Enter a domain. The checker fetches the live record, validates every tag, works out the policy that actually applies, and tells you whether your report addresses are authorized to receive anything.
Thirty characters of DNS, and five ways to get them wrong.
A DMARC record is short. Receivers are strict about it anyway: one misplaced tag and the whole record is ignored.
- The record itself
- The TXT record at _dmarc.yourdomain, exactly as published. If there are two, the checker says so, because RFC 7489 tells receivers to discard both.
- Every tag, explained
- v, p, sp, pct, adkim, aspf, rua, ruf, fo, and ri, each validated and translated into a sentence. Tags you left out are shown with the default that applies in their absence.
- The effective policy
- What receivers will do, as opposed to what the record appears to say. A subdomain with no record of its own inherits the parent’s
sporp; apctunder 100 softens the rest. See none vs quarantine vs reject. - Alignment mode
- Relaxed or strict, for DKIM and SPF separately. Strict alignment breaks mail signed from a subdomain, which surprises people. Alignment explained has the cases.
- External report authorization
- If rua or ruf points at another domain, that domain must publish a small TXT record agreeing to receive your reports. The checker looks it up. Without it, many receivers send nothing.
- A recommended next step
- One sentence on what to do now, based on where the policy stands. The longer version is how to reach p=reject without losing legitimate mail.
The record is an instruction. Receivers are free to follow it.
DMARC does one modest thing. It lets the owner of a domain publish a request: when mail claims to be from us and cannot prove it, here is what we would like you to do, and here is where to send the paperwork. The receiving server does the enforcing. SpoofKiller does not block mail and neither does the record; the record only makes blocking possible.
That is why the policy line matters more than everything after it. p=none asks for reports and no action, which is the correct first step and a poor permanent address. p=quarantine sends failures to spam. p=reject refuses them at the door. If you are new to all this, start with what DMARC is and how it works.
A valid record with a strict policy is still only half of a working setup. DMARC passes when SPF or DKIM passes and the domain it passed for matches the From address. So after this, check the SPF record and the DKIM keys. And if the record has a rua address, somebody should be reading what arrives there. That part can be automated.

The mistakes this checker catches.
The record is at the wrong name
It belongs at _dmarc.yourdomain.com. Published at the root, or at _dmarc.yourdomain.com.yourdomain.com because the DNS host appended the domain a second time, it does nothing. The checker will report no record.
Two DMARC records
Receivers that find more than one record treat the domain as having none. Keep one. If a vendor asked you to add a record, add their address to the existing rua tag, separated by a comma.
p= is not the second tag, or is missing
The record must begin v=DMARC1; p=... in that order. A record with reporting addresses and no policy is not a policy.
Reports go to a domain that never agreed to them
The destination domain publishes a TXT record at
yourdomain.com._report._dmarc.destination.comwith the valuev=DMARC1. Reporting services do this for their own addresses.The domain is enforced and the subdomains are not
sp=none on an enforced domain leaves every subdomain, including ones that do not exist, open to forgery. Remove sp=none once your subdomain senders authenticate.
No rua address
A policy without reports is a policy published blind. Add an aggregate address, and send it somewhere that turns XML into sentences. Reporting setup takes a few minutes.
How to check a DMARC record
Look up, validate, and interpret a domain's DMARC policy.
- 1
Enter the domain
Use the domain from the From address of your mail. Enter a subdomain to see the policy it inherits.
- 2
Read the effective policy
The first row of the result shows the policy receivers apply, the protection level, and the subdomain policy.
- 3
Review each tag
The tag table marks valid, invalid, unknown, and duplicated tags and explains each in a sentence.
- 4
Act on the findings
Fix anything marked critical or high, publish the corrected record, and run the check again.
Questions about this tool
Straight answers. If yours is not here, ask us and a person will reply.
Not sure what your record should say?
Tell us the domain and what sends mail for it. We will reply with the record we would publish and the order to do it in.
- A person reads every message
- No sales sequence, no list rental
- Reply within one business day
You have the instruction. Now read the replies.
A free account gives your domain a reporting address and turns the XML that receivers send into a readable account of what is being sent in your name.
Related tools and guides
- DocsDMARC Reporting SetupAdd your unique reporting address to the rua tag and confirm that reports arrive.Read
- DocsEnforcement ReadinessWhat the readiness status measures and how to move safely toward p=reject.Read
- DocsProtection ScoreThe categories, weights, and limits of SpoofKiller's 0 to 100 domain score.Read
- SpoofKillerFeaturesDMARC analytics, sender identification, spoofing detection, DNS change monitoring, blacklist checks, and reports.Read
- FeatureDMARC MonitoringTurn raw DMARC aggregate reports into a plain account of who sends mail as your domain, what passes, what fails, and what to fix first.Read
- FeatureEmail Spoofing DetectionRules that separate likely impersonation from forwarding and misconfiguration, with a confidence score and the evidence behind it.Read
