Enter a domain, URL, IP, email, or record and get a focused result without setup.
Build DMARC records with policy, reporting, and alignment options.
POST /v1/tools/dmarc/build
Use the browser tool for a fast answer, then move the same logic into scripts, monitoring, or product flows when it becomes repeatable.
Enter a domain, URL, IP, email, or record and get a focused result without setup.
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
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.
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.
Generate none, quarantine, or reject policies.
Add a rua mailbox for aggregate reports.
Tune the pct value while you phase in enforcement.
{
"policy": "quarantine",
"percentage": 100,
"rua": ["mailto:dmarc@example.com"]
}
{
"record": "v=DMARC1; p=quarantine; pct=100; rua=mailto:dmarc@example.com"
}
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
The policy tells receivers how to handle mail that fails SPF or DKIM alignment: monitor only, quarantine, or reject.
No, but adding a reporting mailbox helps you monitor authentication failures and deployment progress.
Pct sets the percentage of mail the policy applies to. Many teams start below 100 while testing and increase it gradually.