TLD Coverage API

What you get

Get the list of supported TLDs and RDAP endpoint health.

SynchronousRESTMCPSDK

Choose this product when

Who it is for

Use focused checks for a single decision or assemble a broader profile when context matters.

Choose this product when

Choose this to inspect whether a TLD has RDAP coverage and how the service should be discovered.

What you get

Get the list of supported TLDs and RDAP endpoint health.

Endpoints

Review the supported operations, inputs, outputs, execution modes, and response limits before integrating.

GET /v1/coverage View API reference

Credits and authentication

Free Authentication optional. 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/coverage

Query Parameters

Parameter	Type	required
live	string Allowed values `1`	optional

Response Fields

Field	Type
`gtlds[]`	string[]
`cctlds[]`	string[]
`total_tlds`	integer
`all_tlds[]`	string[]
`rdap_health[]`	object[]
`rdap_health[]`	object
`rdap_health[].tld`	string
`rdap_health[].endpoint`	string
`rdap_health[].ok`	boolean
`rdap_health[].p50_ms`	number
`rdap_health[].error_rate`	number
`bootstrap_source`	string
`bootstrap_last_updated`	string
`meta`	object
`meta.served_by`	string
`meta.bootstrap_ttl_s`	integer
`meta.live`	boolean

Example Request

curl "https://domscan.net/v1/coverage?live=1"

Example Response

{
  "gtlds": [
    "example"
  ],
  "cctlds": [
    "example"
  ],
  "total_tlds": 1,
  "all_tlds": [
    "com"
  ],
  "rdap_health": [
    {
      "tld": "com",
      "endpoint": "https://example.com",
      "ok": true,
      "p50_ms": 1.5,
      "error_rate": 0.5
    }
  ],
  "bootstrap_source": "iana",
  "bootstrap_last_updated": "2026-08-27T12:00:00Z",
  "meta": {
    "served_by": "example",
    "bootstrap_ttl_s": 1,
    "live": false
  }
}

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

Related products

Frequently asked questions

Where can I find the TLD Coverage request and response reference?

Use the API reference for TLD Coverage to review parameters, response fields, examples, status codes, and supported operation modes.

How should I interpret unknown or incomplete results from TLD Coverage?

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 Coverage priced?

Pricing depends on the operation and execution mode. Check the endpoint reference for the current credit cost, authentication requirement, and per-item rules.