Enter a domain, URL, IP, email, or record and get a focused result without setup.
Get an SSL/TLS configuration grade (A+ to F) with detailed scoring and security recommendations.
GET /v1/ssl/grade?domain=example.com
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.
Get a quick A+ to F rating for the domain's TLS configuration.
See whether the site presents a certificate and whether HSTS is enabled.
Review the main findings before you start remediation.
GET /v1/ssl/grade?domain=example.com
{
"grade": "A",
"score": 92,
"has_certificate": true,
"hsts_enabled": true,
"issues": ["Missing OCSP stapling"]
}
The browser experience previews DomScan's structured endpoints, so teams can validate a use case before writing code.
Certificate validity, TLS protocol support, HSTS, cipher strength, and common configuration issues all influence the final grade.
The letter grade is a summary. The numeric score reflects the number and severity of findings, so two sites with the same grade can still score differently.
Start with missing certificates, protocol downgrade issues, and HSTS. Then review the remaining warnings and weak cipher settings.