Live
Service status
Check live service health and documented failure responses before you integrate.
Security & Trust
Domain security rating API
Rate the external security of a vendor, customer or your own domains in one call. Six areas are scored from public, passive checks and combined into a 0 to 100 score and an A to F grade, with every finding behind it.
Category
Security & Trust
Endpoints
1
Key Features
4
Frequently asked questions
4
Used by people at these companies
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
OpenAPI
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
10,000
Free allowance
Start with 10,000 monthly credits and upgrade only when usage grows.
What this API helps you ship
Use this page as a production brief: endpoints, examples, response shape, and the workflow pieces needed to plug DomScan into your own product.
Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.
Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.
Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.
Feed agents, dashboards, SOAR playbooks, and CRMs through OpenAPI, SDK, Postman, or MCP.
Integration workflow
A simple path from first request to repeatable production usage.
Authenticate once
Send your API key with the documented header and keep requests consistent across services.
Query with examples
Start from the curl and HTTP samples, then map the parameters into your application code.
Operate and monitor
Use status codes, credit costs, and response fields to build retries, logs, and alerts.
Developer kit
Jump from this page into machine-readable docs, request collections, SDKs, or agent tooling.
OpenAPI schema
Generate clients or inspect every request and response shape.
Postman collectionImport ready-made requests for manual testing and team handoff.
SDKs and CLIUse maintained packages and command-line workflows instead of writing boilerplate.
MCP integrationExpose domain intelligence to AI agents and internal assistant workflows.
Parameters and response map
Scan the inputs, output fields, and status codes before wiring the endpoint into your client.
Parameter
domain
Example response
domainstatusscoregradescore_confidencechecks_unknowncategoriesfindings
HTTP status codes
200400401402429
Endpoints
GET
/v1/security-rating
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Live
Service status
Check live service health and documented failure responses before you integrate.
OpenAPI
API artifacts
OpenAPI, Swagger, Postman, CLI, SDK, and MCP links are one click away.
API keys
Protected access
Authenticated endpoints use API keys with clear credit costs before you call them.
10,000
Free allowance
Start with 10,000 monthly credits and upgrade only when usage grows.
Key Features
Six weighted areas
Certificate and TLS, HTTP security headers, SPF and DMARC, DNSSEC and CAA, blocklist reputation and security.txt.
Findings with severity
Each lost point is a coded finding with a severity, so you can sort, alert or report on them.
Critical problems cap the grade
An expired or revoked certificate, a broken chain or a blocklist listing always gives an F, whatever the other scores.
Unknown is not a failure
A check that cannot be completed is left out of the score and reported, with a confidence level for how much was measured.
Example request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/security-rating?domain=github.com"Example response
{
"domain": "github.com",
"status": "partial",
"score": 81,
"grade": "B",
"score_confidence": "medium",
"checks_unknown": 1,
"categories": [
{ "id": "tls", "status": "scored", "score": 85, "weight": 30 },
{ "id": "http_headers", "status": "scored", "score": 85, "weight": 20 },
{ "id": "email_authentication", "status": "scored", "score": 85, "weight": 20 },
{ "id": "dns", "status": "scored", "score": 40, "weight": 10 },
{ "id": "reputation", "status": "unknown", "score": null, "weight": 15 },
{ "id": "disclosure", "status": "scored", "score": 100, "weight": 5 }
],
"findings": [{ "category": "dns", "code": "dnssec_not_enabled", "severity": "low" }]
}Frequently asked questions
Is this a vulnerability scan?
No. Only passive checks are used: what any browser, mail server or resolver can see. Nothing is attacked.
How are grades assigned?
A from 90, B from 80, C from 70, D from 60, otherwise F, from the weighted average of the areas that could be measured.
Why can the score be null?
When no area could be measured, for example because the domain does not resolve, the score and grade are null and the request is refunded.
How many credits does it cost?
Five credits per rating. Ratings with no measured area are refunded.
Related tools and resources
HTTP status codes
These are the HTTP status codes to handle, so you can tell apart successful responses, auth issues, credits, rate limits, missing data, and upstream failures.
OK
200
Request successful
Bad Request
400
Invalid parameters
Unauthorized
401
Missing or invalid API key/session.
Payment Required
402
Not enough credits to run this request.
Too Many Requests
429
Rate limit exceeded
Rate a domain