Free tool
Free SPF & DMARC Checker
Check a domain’s SPF and DMARC records — who is allowed to send for the domain, and what receivers are asked to do with mail that fails — with two free DNS lookups at the domain itself and _dmarc.<domain>.
dns lookup · no account · no credits
Enter a domain
example.com, or a URL you paste.
Check DMARC
One TXT query at _dmarc.<domain>.
Read the record
Policy, reporting tags and alignment.
The domain is sent to MultiValidator’s DNS lookup endpoint, which queries the TXT record at _dmarc.<domain> for DMARC and at the domain itself for SPF. No API key, no account, no credits.
What is DMARC?
DMARC stands for Domain-based Message Authentication, Reporting, and Conformance. It is an email authentication policy mechanism: it gives a domain owner a place to publish what they would like receivers to do with mail that claims to come from their domain, and where to send reports about it.
It works alongside SPF and DKIM rather than replacing them: those two authenticate a sending source, and DMARC adds the domain-level alignment check, the published policy and the reporting preference. It is one part of an email configuration, not a complete defence — no single record prevents every spoofed or fraudulent message.
What is a DMARC record?
DMARC policy is published as a DNS TXT record under a reserved name: the label _dmarc in front of the domain. For example.com that is _dmarc.example.com — which is exactly the name this checker queries.
The record itself is a semicolon-separated list of tags. It has to begin with v=DMARC1, the version tag, and for a policy record it carries a policy tag such as p=none. Everything else — subdomain policy, reporting destinations, alignment modes, intervals — is optional, which is why this checker shows present values and marks the rest as not specified rather than inventing a default.
How does a DMARC checker work?
Six steps, and only the first needs you. No email is sent at any point in them.
Enter a domain
example.com, or a pasted URL — the scheme, path, port and trailing dot are stripped before the query.
The domain is normalized
The input is trimmed and reduced to its domain half, then checked against the same domain rule the MX lookup uses.
The TXT record is queried
One DNS query goes out for TXT records at _dmarc.<domain>, the location RFC 7489 defines for DMARC policy.
A DMARC record is identified
A record counts as DMARC only when it carries the version tag v=DMARC1 — other TXT records at the name are reported separately, not parsed.
The supported tags are read
v, p, sp, pct, rua, ruf, adkim, aspf, fo and ri are read and checked against the values the specification allows.
The record and its policy are shown
The raw record is displayed unchanged, with the policy it requests and the reporting and alignment settings it carries.
The distinction that matters: this tool reads a published record. It does not test an email, and it cannot say whether a message passed DMARC.
What does a DMARC policy mean?
The policy tag asks receivers for something. What actually happens to a failing message is decided by the receiver applying its own policy and DMARC processing, so these are requests rather than outcomes.
Monitoring policy
The domain is not requesting quarantine or rejection for failing messages under this policy. It is the setting domains usually start with while they collect reports.
Suspicious mail policy
The domain requests that failing messages be treated as suspicious — subject to the receiver's behaviour and its other mail policies.
Reject policy
The domain requests that failing messages be rejected — again subject to receiver behaviour and DMARC processing, which the receiver applies.
No policy is ranked here as better than another, and no score is calculated: which setting suits a domain depends on what it is doing with reports and how much of its mail it has authenticated first.
Common DMARC record tags.
The tags this checker reads. A tag that is not in this list is left alone rather than guessed at, and a tag that is absent is reported as not specified.
| Tag | Purpose |
|---|---|
| v | DMARC version. Must be the first tag, with the value DMARC1. |
| p | The policy requested for the domain: none, quarantine or reject. |
| sp | The policy requested for subdomains, when it differs from p. |
| pct | The percentage of messages the policy applies to. |
| rua | Where aggregate reports are requested to be sent. |
| ruf | Where failure (forensic) reports are requested to be sent. |
| adkim | DKIM identifier alignment: r (relaxed) or s (strict). |
| aspf | SPF identifier alignment: r (relaxed) or s (strict). |
| fo | Which failure conditions should generate a report. |
| ri | The interval, in seconds, between aggregate reports. |
DMARC record example.
A typical published record, of the shape the checker parses:
v=DMARC1; p=none; rua=mailto:dmarc@example.com
- v=DMARC1
Identifies the record as DMARC, version 1, and has to come first.
- p=none
The policy requested for the domain — here, none beyond monitoring.
- rua=mailto:…
Where aggregate reports are requested to be sent.
That is one example, not a recommendation. The right record for a domain depends on what it sends, what it has authenticated, and what it is ready to do with failing mail.
DMARC vs. SPF vs. DKIM.
Three different jobs. This page reads the DMARC record only — it does not validate SPF or DKIM.
| Technology | Main purpose |
|---|---|
| SPF | Publishes which infrastructure is authorised to send mail for the domain. |
| DKIM | Adds a cryptographic signature to a message so a receiver can check it was not altered. |
| DMARC | Uses authentication results with domain alignment, and publishes the policy and reporting preferences for a domain. |
A DMARC record that references alignment and reporting is not a statement that a domain’s SPF or DKIM records are right. If you want to inspect other parts of a domain’s mail configuration, the MX record lookup reads the domain’s mail routing.
DMARC checker vs. email verification.
One looks at a domain’s published policy; the other looks at an address. Neither does the other’s job.
dmarc checker — this page
Reads the DMARC TXT record published at _dmarc.<domain>: the requested policy, the subdomain policy, reporting destinations and alignment settings. One domain per query.
Checking DMARC for example.com says nothing about person@example.com.
email verification
Works on an address instead: syntax, DNS and MX resolution, disposable detection, the SMTP mailbox probe, spam-trap and role checks, then a verdict, a reason and a score.
why check
Why check a domain’s DMARC record?
Mostly configuration work: confirming what a domain publishes, and whether a change has landed.
Email authentication setup
Confirm exactly what a domain publishes today before you change anything around it.
DNS troubleshooting
See whether a TXT record exists at the reserved _dmarc name and what it actually contains.
New domain setup
Check a domain you are bringing online, and whether a policy record is live yet.
Security configuration review
Record which policy a domain requests and how it asks for reports.
Deliverability troubleshooting
Establish the published policy as one data point while investigating mail behaviour.
Verifying a change
Re-run the lookup after editing DNS, keeping in mind that caches and TTL may delay what you see.
None of this promises better inbox placement. A published record is a configuration statement, and what receivers do with it is up to them.
What does a DMARC checker not check?
The tool reads one DNS record. Everything below sits outside that, and is kept here rather than left to assumption.
- Send an email, or perform any SMTP or mailbox probe.
- Verify a specific email address or prove a mailbox exists.
- Prove that any email message passed DMARC — that is decided per message, at delivery.
- Read a message's Authentication-Results header.
- Validate DKIM: the tool reads the SPF and DMARC records, not DKIM signatures.
- Guarantee inbox placement, or protection against every form of abuse.
- Identify who sent an individual email.
The presence of a record is not a pass, and its absence is not a verdict — a missing record only means no valid DMARC policy record was found at the name that was queried.
Why can’t I see my new DMARC record yet?
DNS answers are cached and each record has a TTL, so a change can take a while to be visible everywhere. When a record does not appear, these are the usual reasons.
- DNS caching: resolvers serve the answer they already have until it expires.
- TTL: the record's own time-to-live sets how long that cached answer is allowed to live.
- Nameserver changes: a domain moved to new nameservers can serve stale or no data while it settles.
- The wrong record name: DMARC belongs at _dmarc.<domain>, not at the apex.
- Provider configuration: a record saved as a draft, or in a zone that was never applied.
- Conflicting TXT records: more than one policy record at the same name, which is ambiguous by design.
- Propagation delays: different resolvers can answer differently for a while.
No specific propagation time is promised here — it depends on the TTLs and the resolvers in the path.
DMARC checker FAQ.
What the lookup reads, what a policy requests, and what a record can never prove.
A DMARC checker looks up a domain's _dmarc DNS TXT record and explains the policy information published there — the requested policy, subdomain policy, reporting destinations and alignment settings.
Related free tools
Each tool checks one layer. To run the full pipeline — MX lookup, live SMTP probe and catch-all detection with a reason and a score — use the API.