Enter a domain, URL, IP, email, or record and get a focused result without setup.
SPF Record Checker
Enter a domain to retrieve its live SPF TXT record and validate the published sending policy.
POST /v1/tools/spf/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 SPF policy currently published in DNS for the domain.
Check the record structure, version, terms, and common policy problems.
Review qualifiers, mechanisms, includes, redirects, and the final all rule.
Example Request
POST /v1/tools/spf/validate
Content-Type: application/json
{"domain":"example.com"}
Example Response
{
"domain": "example.com",
"record": "v=spf1 include:_spf.example.net -all",
"valid": true,
"dns_lookups": 1,
"max_lookups": 10,
"policy": "fail"
}
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
It retrieves the domain's published SPF TXT record and checks its structure and policy terms. It does not test whether a specific email message passes SPF.
The domain may not publish a TXT record beginning with v=spf1, or the DNS change may not yet be visible to the resolver used for the check.
No. SPF is one authentication signal. Delivery also depends on DKIM, DMARC, sender reputation, message content, and recipient policies.