Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Used by people at amazing companies
Trust signals before you integrate
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.
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.
Send your API key with the documented header and keep requests consistent across services.
Start from the curl and HTTP samples, then map the parameters into your application code.
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.
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
Example Response
HTTP Status Codes
Endpoints
/v1/value
/v1/value/bulk
Trust signals before you integrate
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.
Key Features
Get low/mid/high value ranges in milliseconds.
Length, TLD tier, dictionary words, brandability, and more.
Premium (.com, .ai, .io), Standard (.net, .org), and Value tiers.
Analyze pronounceability and memorable qualities.
Premium pricing for common English words.
Valuate multiple domains in a single request.
Know how confident the algorithm is in each estimate.
See exactly which factors influenced the valuation.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/value?domain=my-site.com"
Example Response
{
"domain": "my-site.com",
"label": "my-site",
"tld": "com",
"estimate": {
"low": 297,
"mid": 453,
"high": 1016,
"currency": "USD"
},
"factors": {
"length": 7,
"tldTier": "premium",
"hasHyphens": true,
"isDictionaryWord": false,
"isBrandable": false,
"pronounceability": 0.8
},
"confidence": 0.61,
"analysis": {
"scope": "intrinsic_domain_value",
"range_source": "blended",
"confidence_label": "medium",
"primary_comparable_category": "Hyphenated domain",
"primary_comparable_range": { "low": 10, "high": 5000, "position": "mid", "relative_position": 0.61 },
"positive_factors": ["Premium .com market liquidity"],
"negative_factors": ["Hyphen reduces liquidity and buyer pool"]
}
}
Frequently Asked Questions
Our valuations are algorithmic estimates based on domain characteristics, not actual sales data. Actual market value depends on buyer demand, comparable sales, and negotiation. Use these as a starting point, not a definitive price.
Key factors include: domain length (shorter = more valuable), TLD tier (.com is premium), dictionary words, brandability, pronounceability, presence of hyphens/numbers, and pattern recognition (like CVCV patterns).
No, our current algorithm uses intrinsic domain characteristics only. We may add comparable sales data in the future to improve accuracy.
Yes! Use the POST /v1/value/bulk endpoint with an array of domains to valuate up to 100 domains in a single request.
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.
Request successful
Invalid parameters
Not enough credits to run this request.
Rate limit exceeded
Internal error
Upstream RDAP error
Upstream service unavailable or temporarily rate limited.
Upstream lookup timed out.
Valuate Domains for Free