Live
Service status
Check live service health and documented failure responses before you integrate.
Domain Intelligence
Name Availability API
Check a brand or product name everywhere in one request: domain availability across up to 20 extensions, the same handle on social and developer platforms, and the package name in npm, PyPI, crates.io, RubyGems, NuGet, Packagist and Homebrew. Get a verdict, a score and the evidence for every item.
Category
Domain Intelligence
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
nametldsplatformspackages
Example response
nameverdictscoresummarysummary.com_availablesummary.domainssummary.domains.checkedsummary.domains.freesummary.domains.takensummary.domains.unknownsummary.handlessummary.handles.checked
HTTP status codes
200400401402429
Endpoints
GET
/v1/name-check
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
Three checks in one
Domains, platform handles and package names are checked in parallel and returned in one response.
Verdict and score
available_everywhere, mostly_available, contested or unknown, with the share of definite results that are free.
Your own lists
Choose up to 20 extensions, any supported platforms or all of them, and the registries that matter to your stack.
Unknown is never free
Blocked, rate-limited or failed checks are reported as unknown and left out of the score.
Example request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/name-check?name=acmeflow&tlds=com,io,ai"Example response
{
"name": "acmeflow",
"verdict": "mostly_available",
"score": 80,
"summary": {
"com_available": false,
"domains": { "checked": 3, "free": 2, "taken": 1, "unknown": 0 },
"handles": { "checked": 20, "free": 17, "taken": 2, "unknown": 1 },
"packages": { "checked": 7, "free": 6, "taken": 1, "unknown": 0 }
},
"domains": [{ "domain": "acmeflow.io", "status": "available" }],
"handles": [{ "platform": "github", "status": "available" }],
"packages": [{ "registry": "npm", "status": "not_found" }]
}Frequently asked questions
How much does a check cost?
5 credits per name, whatever lists you choose. When nothing could be determined, the credits are refunded.
What does not_found mean for packages?
No package uses the name. Registries such as npm and PyPI may still refuse names that are too similar to existing ones, so not_found is a strong signal, not a guarantee.
Which name formats are accepted?
Letters, digits and inner hyphens, from 2 to 63 characters, so the same name works as a domain, a handle and a package.
Can AI agents use it?
Yes. It is available as the name_check MCP tool, so an assistant can propose names and keep only the ones that are free.
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
Check a name