Live
Service status
Check live service health and documented failure responses before you integrate.
Category
Workflow Recipes
Endpoints
12
Credits
7-25
Authentication
Authentication required
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
domainkeywordsdomains
Example Response
successdatameta
HTTP Status Codes
200400401402429500502503504
Endpoints
GET
/v1/recipes/due-diligence
domain
GET
/v1/recipes/brand-launch
domain
GET
/v1/recipes/threat-assessment
domain
GET
/v1/recipes/domain-finder
keywords
GET
/v1/recipes/competitor-intel
domain
GET
/v1/recipes/portfolio-audit
domains
POST
/v1/recipes/portfolio-audit
domains
GET
/v1/recipes/email-deliverability
domain
GET
/v1/recipes/dns-migration
domain
GET
/v1/recipes/infrastructure-discovery
domain
GET
/v1/recipes/defensive-registration
domain
GET
/v1/recipes/phishing-investigation
domain
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
Endpoints
GET /v1/recipes/due-diligence • GET /v1/recipes/brand-launch • GET /v1/recipes/threat-assessment • GET /v1/recipes/domain-finder • GET /v1/recipes/competitor-intel • GET /v1/recipes/portfolio-audit • POST /v1/recipes/portfolio-audit • GET /v1/recipes/email-deliverability • GET /v1/recipes/dns-migration • GET /v1/recipes/infrastructure-discovery • GET /v1/recipes/defensive-registration • GET /v1/recipes/phishing-investigation
Parameter
domain, keywords, domains
HTTP Status Codes
200, 400, 401, 402, 429, 500, 502, 503, 504
Credits / Authentication
7-25 / Authentication required
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/recipes/due-diligence?domain=example.com"curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/recipes/brand-launch?domain=example.com"curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/recipes/threat-assessment?domain=example.com"Frequently Asked Questions
Which endpoints are included?
This guide covers 12 public endpoints: GET /v1/recipes/due-diligence, GET /v1/recipes/brand-launch, GET /v1/recipes/threat-assessment, GET /v1/recipes/domain-finder, GET /v1/recipes/competitor-intel, GET /v1/recipes/portfolio-audit, POST /v1/recipes/portfolio-audit, GET /v1/recipes/email-deliverability, GET /v1/recipes/dns-migration, GET /v1/recipes/infrastructure-discovery, GET /v1/recipes/defensive-registration, GET /v1/recipes/phishing-investigation.
Does this API require authentication?
Yes. Send your API key with the `X-API-Key` or `Authorization: Bearer` header when calling Workflow Recipes.
How many credits does it use?
Requests in these guides use 7-25 credits depending on the endpoint. For bulk endpoints, credits use the standard per-item rate.
Where can I see the full parameters and related endpoints?
Use the full docs for Workflow Recipes to review parameter details, authentication notes, and related endpoints in the same API family.
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.
Start free with 10,000 credits per month. Use any public API and add credits only when you need them.