Enter a domain, URL, IP, email, or record and get a focused result without setup.
DMARC Record Checker
Enter a domain to retrieve its live _dmarc TXT record, validate the record, and understand the published policy.
POST /v1/tools/dmarc/validate
Run the check, then ship the workflow
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Outputs highlight statuses, risks, records, and next actions instead of raw provider noise.
Use the request and response examples to turn a one-off check into an API call or recipe.
Used by people at amazing companies
What this tool helps you decide
Each page is shaped around a practical operational question, not just a raw lookup.
See the current DNS, registration, security, pricing, or reputation evidence.
Compare the result with related checks so the next move is easier to trust.
Copy examples, open linked tools, or move into API documentation when you need scale.
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
Authenticated endpoints use API keys with clear credit costs before you call them.
Start with 10,000 monthly credits and upgrade only when usage grows.
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Retrieve the DMARC policy currently published for the domain.
Check the required version and policy tags, plus the structure of optional settings.
Review enforcement, subdomain policy, alignment modes, and reporting destinations.
Example Request
POST /v1/tools/dmarc/validate
Content-Type: application/json
{"domain":"example.com"}
Example Response
{
"domain": "example.com",
"record": "v=DMARC1; p=reject; pct=100",
"valid": true,
"policy": "reject",
"percentage": 100,
"strength": "strong"
}
Built from the same API surface
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Frequently Asked Questions
They state the domain owner's requested handling for messages that fail DMARC. None requests monitoring, quarantine treats failures as suspicious, and reject requests rejection.
A valid DMARC TXT record may not be published at _dmarc for the domain, or a recent DNS change may not yet be visible to the resolver used for the check.
No. The record defines policy. A message passes DMARC only when an authenticated SPF or DKIM identity aligns with the domain in the From address.