TLD Coverage API

Q: Which endpoints are included?

This guide covers 1 public endpoints: GET /v1/coverage .

{ "gtlds": ["com", "net", "org"], "cctlds": ["io", "es", "de"], "rdap_health": [ { "tld": "com", "endpoint": "https://rdap.verisign.com/com/v1", "ok": true, "p50_ms": 144, "error_rate": 0 } ], "bootstrap_last_updated": "2026-04-13T08:00:00.000Z", "meta": { "live": false } }

Category Domain Availability

Endpoints 1

Credits 1

Authentication optional

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.

99.99% Uptime

Production-ready endpoints are designed for 99.99% uptime and documented status handling.

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.

Product workflows

Embed domain checks, DNS intelligence, risk signals, or enrichment into onboarding, search, and internal tools.

Analyst automation

Replace repeated manual lookups with scheduled jobs, alerting, and reproducible investigation steps.

Clean JSON data

Use predictable fields, documented status codes, and credit costs instead of scraping provider pages.

AI and ops tooling

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 collection

Import ready-made requests for manual testing and team handoff.

SDKs and CLI

Use maintained packages and command-line workflows instead of writing boilerplate.

MCP integration

Expose 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.

Request parameters

Parameter

live

Response fields

Example Response

gtldscctldsrdap_healthbootstrap_last_updatedmetameta.live

Status coverage

HTTP Status Codes

200400402429500502503504

Endpoints

GET /v1/coverage

Credits: 1Authentication: optional

live

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

Endpoints

GET /v1/coverage

Parameter

live

HTTP Status Codes

200, 400, 402, 429, 500, 502, 503, 504

Credits / Authentication

1 / optional

Example Request

GET /v1/coverage bash

Open

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/coverage"

GET /v1/coverage?live=1 bash

Open

curl -H "X-API-Key: $DOMSCAN_API_KEY" "https://domscan.net/v1/coverage?live=1"

Example Response

200 OK json

{
  "gtlds": ["com", "net", "org"],
  "cctlds": ["io", "es", "de"],
  "rdap_health": [
    {
      "tld": "com",
      "endpoint": "https://rdap.verisign.com/com/v1",
      "ok": true,
      "p50_ms": 144,
      "error_rate": 0
    }
  ],
  "bootstrap_last_updated": "2026-04-13T08:00:00.000Z",
  "meta": {
    "live": false
  }
}

Frequently Asked Questions

Which endpoints are included?

This guide covers 1 public endpoints: GET /v1/coverage.

Does this API require authentication?

TLD Coverage is publicly accessible, but authenticated requests are still useful for usage tracking and higher limits where available.

How many credits does it use?

Requests in this guide use 1 credits depending on the endpoint. Bulk endpoints apply the published bulk rate shown on the page and in the full docs.

Where can I see the full parameters and related endpoints?

Use the full docs for TLD Coverage to review parameter details, authentication notes, and related endpoints in the same API family.

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.

Start for free with 10,000 credits per month. Start checking domains in seconds.

View Full API Documentation APIs