99.99%
Uptime
Production-ready endpoints are designed for 99.99% uptime and documented status handling.
Category
Domain Intelligence
Endpoints
2
Key Features
8
Frequently Asked Questions
4
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
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
tld
Example Response
tldtypenamedescriptionintroducedoperatorrestrictionsrdap_supportedidn_supporteddnssec_supportedpricingpricing.registration_usd
HTTP Status Codes
200400402429500502503504
Endpoints
GET
/v1/tlds
GET
/v1/tlds/:tld
tld
Trust signals before you integrate
Transparent docs, authenticated requests, and visible reliability details make it easier to evaluate DomScan before you ship.
Uptime
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
Comprehensive TLD Database
Detailed info on 50+ popular TLDs with more being added.
Pricing Information
Registration, renewal, and transfer price estimates.
Trust Scores
Know which TLDs are premium, standard, or economy tier.
Use Case Recommendations
Discover which TLDs are best for startups, tech, e-commerce, etc.
Restriction Details
Learn about registration requirements and restrictions.
RDAP Support Status
Know which TLDs support modern RDAP protocol.
Filter by Type
Browse gTLDs, ccTLDs, new TLDs, or IDN extensions.
Popularity Rankings
See how popular each TLD is in the global market.
Example Request
curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/tlds/io"Example Response
{
"tld": "io",
"type": "ccTLD",
"name": "British Indian Ocean Territory",
"description": "Popular with tech startups and SaaS companies",
"introduced": 1997,
"operator": "Internet Computer Bureau",
"restrictions": "None - open registration",
"rdap_supported": true,
"idn_supported": false,
"dnssec_supported": true,
"pricing": {
"registration_usd": 40,
"renewal_usd": 40,
"transfer_usd": 40
},
"popularity": {
"rank": 5,
"tier": "top10",
"use_cases": ["startup", "tech", "saas", "api", "developer"]
},
"trust": {
"score": 85,
"tier": "premium",
"notes": "De facto tech startup TLD"
}
}Frequently Asked Questions
What is a TLD trust score?
Trust scores (0-100) reflect how trustworthy and established a TLD is. Premium TLDs like .com and .io have high scores, while newer or less-known TLDs have lower scores.
How accurate is the pricing information?
Pricing is based on market averages and may vary by registrar. Use it as a guideline - always check with your preferred registrar for exact pricing.
Can I filter TLDs by use case?
Yes! Use the use_case parameter (e.g., ?use_case=startup) to get TLDs recommended for specific purposes.
What is the difference between gTLD and ccTLD?
gTLDs (generic TLDs) like .com and .org are not tied to any country. ccTLDs (country code TLDs) like .uk and .de are assigned to specific countries but many allow global registration.
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
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.
Explore TLD Intelligence