Who it is for
Use focused checks for a single decision or assemble a broader profile when context matters.
What you get
Get detailed intelligence about a TLD including pricing, restrictions, registrar support, and usage statistics.
SynchronousRESTMCPSDK
Choose this product when
Choose this product when
Choose this to understand a TLD and its registration-oriented characteristics before checking a specific name.
What you get
Get detailed intelligence about a TLD including pricing, restrictions, registrar support, and usage statistics.
Endpoints
Review the supported operations, inputs, outputs, execution modes, and response limits before integrating.
Credits and authentication
0-1 Authentication required. Check the operation reference for the exact cost and any per-item pricing.
Example operation
Use documented operations to collect, assess, enrich, verify, compare, protect, or monitor public evidence.
GET
/v1/tlds
Query Parameters
| Parameter | Type | required |
|---|---|---|
| type |
string
Allowed values
gtldcctldnew-gtldidn
|
optional |
| trust_tier |
string
Allowed values
premiumstandardeconomysuspicious
|
optional |
| use_case | string | optional |
Response Fields
| Field | Type |
|---|---|
tlds[] |
object[] |
tlds[] |
object |
tlds[].tld |
string |
tlds[].type |
string |
tlds[].name |
string |
tlds[].rdap_supported |
boolean |
tlds[].trust_tier |
string |
tlds[].popularity_rank |
integer |
tlds[].registration_usd |
number |
total |
integer |
by_type |
object |
by_type.gTLD |
integer |
by_type.ccTLD |
integer |
by_type.newTLD |
integer |
by_type.idn |
integer |
by_trust_tier |
object |
by_trust_tier.premium |
integer |
by_trust_tier.standard |
integer |
by_trust_tier.economy |
integer |
use_case |
string |
meta |
object |
Example Request
curl "https://domscan.net/v1/tlds?type=gtld&trust_tier=premium&use_case=startup"Example Response
{
"tlds": [
{
"tld": "com",
"type": "gTLD",
"name": "example",
"rdap_supported": false,
"trust_tier": "premium",
"popularity_rank": 1,
"registration_usd": 0.5
}
],
"total": 1,
"by_type": {
"gTLD": 1,
"ccTLD": 1,
"newTLD": 1,
"idn": 1
},
"by_trust_tier": {
"premium": 1,
"standard": 1,
"economy": 1
},
"use_case": "example",
"meta": {}
}Limits and evidence boundaries
Results describe observed public evidence and its provenance.
Coverage is bounded by the documented inputs, budgets, sources, and response limits.
Evidence can change over time; use timestamps and freshness fields when provided.
Reviewed 2026-08-22
Frequently asked questions
Where can I find the TLD Intelligence request and response reference?
Use the API reference for TLD Intelligence to review parameters, response fields, examples, status codes, and supported operation modes.
How should I interpret unknown or incomplete results from TLD Intelligence?
Unknown or partial results mean that the requested evidence could not be fully determined. Keep the result state, confidence, freshness, and limitations in downstream decisions.
How is TLD Intelligence priced?
Pricing depends on the operation and execution mode. Check the endpoint reference for the current credit cost, authentication requirement, and per-item rules.
