Live
Service status
Check live service health and documented failure responses before you integrate.
Category
Web Intelligence
Endpoints
2
Key Features
6
Frequently Asked Questions
5
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
canonical_domainorganizationorganization.nameidentitiesconfidence
HTTP Status Codes
200400401402429500502503504
Endpoints
GET
/v1/identity-resolution
POST
/v1/identity-resolution/bulk
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
Domain-First Resolution
Start with a company website instead of an ambiguous person or brand name.
Declared Public Profiles
Discover identities from JSON-LD sameAs, rel=me, and public homepage links.
Platform Normalization
Receive consistent platform, category, handle, and canonical profile URL fields.
Evidence and Confidence
Every match states where it was found and how strongly the website declared it.
Multiple Identity Categories
Classify social, developer, creator, federated, and app-store identities.
Bulk Domain Resolution
Resolve up to 10 company domains per request with ordered partial-success results.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/identity-resolution?domain=example.com"curl -X POST -H "X-API-Key: $DOMSCAN_API_KEY" -H "Content-Type: application/json" \
-d '{"domains":["example.com","github.com"]}' https://domscan.net/v1/identity-resolution/bulkExample Response
{
"canonical_domain": "example.com",
"organization": { "name": "Example" },
"identities": [
{
"platform": "github",
"type": "developer",
"handle": "example",
"url": "https://github.com/example",
"source": "same_as",
"confidence": "high"
}
],
"confidence": 0.75
}Frequently Asked Questions
Does this API resolve companies or individual people?
The API is designed for company and project domains. It does not attempt to identify private individuals from personal information.
Are returned profiles verified by the social platform?
No. Results are profiles declared by the website, not platform verification. The response preserves the declaration source and confidence.
Which public sources are used?
DomScan reads public homepage links, JSON-LD sameAs values, and rel=me relationships from the target website.
Why might an existing company profile be missing?
A profile is omitted when the website does not declare it, the page is blocked, or the platform URL cannot be classified safely.
Can I resolve several domains in one request?
Yes. The bulk endpoint accepts up to 10 domains and reports success or failure for every input.
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.
Resolve Public Company Identities