Free DMARC inspector
The inspector reads a domain's published email authentication records and explains them in plain words, without an account. It runs on the platform's tools site and calls one anonymous API route, POST /v1/dmarc/tools/inspect. Monitoring a domain over time (daily checks, readiness for sending, the policy wizard) needs an account; the result card links to sign-up.
What it checks
The inspector runs the DNS-only part of a full domain check, inside the same lookup budget:
- SPF: whether one record is published, how many DNS lookups it needs out of 10, its
allqualifier and redirect, and which includes cost the most lookups. - DMARC: whether
_dmarc.<domain>publishes a record, its policy, subdomain policy,pct, alignment modes and how many report mailboxes it names. - BIMI, MTA-STS and TLS-RPT: whether their TXT records are published and well formed. The MTA-STS policy file itself is never fetched for an anonymous request.
It does not check DKIM: a DKIM key lives under a selector only the sender knows, and the account's domain check reads the selectors of its own identity.
Verdicts
| Verdict | Meaning |
|---|---|
protected | A valid DMARC policy enforces (quarantine or reject at 100 %). |
monitoring | A valid DMARC record that does not enforce on all mail yet: p=none, or quarantine or reject with a pct under 100. |
unprotected | No DMARC record is published. |
broken | The SPF or DMARC record cannot be relied on: several records, a record that does not parse, a DMARC record without a policy, an SPF record with +all, a loop, an unknown term or over the lookup limit, or names that did not answer in time. |
Every problem found is listed as text under the verdict.
Limits and refusals
- A human check (the challenge widget on the page) is required for every request; its token is used once. A missing or over-long token answers
401, a refused or reused token403. - Each visitor can run 10 inspections per minute (a burst of 10, then one more every 6 seconds); the answer to a domain is cached for 10 minutes, so asking again inside that window looks nothing up. An answer cut short by the deadline or the lookup budget, or one that observed nothing, is not cached. Busy domains and the whole service have their own per-minute ceilings. A refusal answers
429withRetry-After. - Only public host names are accepted: no IP address, no URL path, no
local,localhost,internalor reverse-lookup (arpa) zone; anything else answers400before a lookup runs. - When the platform's resolver cannot answer, the inspector answers
503withRetry-Afterinstead of a wrongunprotectedverdict; it also answers503while the human check cannot be verified or its counters cannot be read, and while it is starting.
Privacy
The inspector keeps no record of a visitor beyond the rate counter of the current minute, and keeps the answer to a domain for 10 minutes. The human check sends the visitor's address to the challenge provider that verifies it. The answer never says whether a domain belongs to an account or is monitored; within the cache window it carries cached: true and the time of the first inspection, so it tells that someone looked the domain up in the last 10 minutes.