Live
Service status
Check live service health and documented failure responses before you integrate.
Category
Security & Email
Endpoints
1
Key Features
4
Frequently Asked Questions
4
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
urldomainmode
Example Response
scanscan.modescan.statussummarysummary.posturesummary.risk_levelsummary.finding_countsummary.version_affected_countsummary.misconfiguration_countfindingscoveragecoverage.package_advisories
HTTP Status Codes
200400401402429500502503504
Endpoints
GET
/v1/vulnerabilities
urldomainmode
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Service status
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.
Free allowance
Sign Up for Free
Start with 10,000 monthly credits and upgrade only when usage grows.
Active
Example Request
Start from the curl and HTTP samples, then map the parameters into your application code.
Key Features
Exact Version Evidence
Only reviewed technology-to-package mappings and compatible observed versions are queried against OSV.
KEV and EPSS Prioritization
CISA KEV raises confirmed exploitation above probability, while FIRST EPSS adds daily threat context.
Explicit Coverage Gaps
Every source and scan stage reports checked, partial, failed, or not requested status.
Safe Passive Snapshot
The public endpoint inspects normal public responses and isolated rendering without exploit payloads.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/vulnerabilities?domain=example.com&mode=standard"Example Response
{
"scan": {
"mode": "standard",
"status": "complete"
},
"summary": {
"posture": "review",
"risk_level": "high",
"finding_count": 2,
"version_affected_count": 1,
"misconfiguration_count": 1
},
"findings": [{
"classification": "version_affected",
"severity": "high",
"priority": "urgent",
"component": {
"name": "jQuery",
"detected_version": "3.4.1",
"purl": "pkg:npm/jquery@3.4.1"
},
"advisory": {
"id": "GHSA-gxr4-xjj5-5px2",
"cves": ["CVE-2020-11022"],
"fixed_versions": ["3.5.0"]
},
"exploitation": {
"cisa_kev": true,
"epss_probability": 0.99019
}
}],
"coverage": {
"package_advisories": "checked",
"known_exploitation": "checked",
"exploitation_probability": "checked",
"relay_used": false
}
}Frequently Asked Questions
What does the scanner check?
It checks exposed technology versions, exact OSV advisory matches, CISA Known Exploited Vulnerabilities, FIRST EPSS values, and deterministic response-header protections.
Does a version match prove exploitation?
No. It means an exposed version is listed in an authoritative affected range. DomScan does not claim exploitation unless a future authorized verification check proves the behavior.
Which data sources are used?
The scanner uses OSV, the CISA Known Exploited Vulnerabilities Catalog, FIRST EPSS, and live public response evidence. All runtime sources have zero incremental data cost.
What does deep mode add?
Deep mode adds one isolated JavaScript-rendered page through the DomScan Edge Relay, which can expose runtime technology evidence that a basic response misses.
Related Tools & Resources
HTTP Status Codes
We document the HTTP status codes you should handle so you can distinguish 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
Server Error
500
Internal error
Bad Gateway
502
Upstream RDAP error
Service Unavailable
503
Upstream service unavailable or temporarily rate limited.
Gateway Timeout
504
Upstream lookup timed out.
Scan a Website for Vulnerabilities