For developers & LLMs

Data & API Reference

Everything you need to programmatically access nTLD.zone data — sources, refresh cadence, MCP tools, and machine-readable endpoints.

Data Sources

nTLD.zone aggregates data from three canonical sources in the domain name industry:

  • ICANN CZDS (Centralized Zone Data Service) — Daily zone files for gTLDs. This is the primary source for live domain counts, additions, and deletions. We ingest zone files every 24 hours for all participating registries.
  • ICANN Monthly Registry Reports — Registrar-level market share and domains under management (DUM) figures published by registries each month. Used for registrar breakdowns and monthly trend validation.
  • IANA Root Zone Database — The authoritative source for TLD delegation dates, technical operators (backend providers), and registry assignments.

Refresh Frequency

Live zone data is fetched from CZDS once every 24 hours. The ingestion pipeline runs automatically and processes zone files for all participating TLDs in parallel.

Monthly reports are ingested as soon as ICANN publishes them — typically within 1–3 days of the monthly deadline.

Launch phases (Sunrise, Landrush, GA dates) are updated weekly by monitoring IANA and registry announcements.

The dashboard shows a real-time ingestion status badge — if you see "running" or a recent timestamp, the latest data is live. TLDs marked "awaiting first refresh" are tracked in the database but have not yet had a successful zone file download (this usually resolves within 48 hours of being added).

Coverage & Definitions

We track all new gTLDs delegated since 2012 — generic, brand, geographic, and community extensions. This includes:

  • All ICANN-contracted gTLDs participating in CZDS
  • Brand TLDs with public zone data
  • Geographic and community extensions

live data source means the TLD has at least one successfully ingested zone file and shows daily counts. none means the TLD is in our database but awaiting its first zone snapshot.

Domain counts reflect live, delegated domains in the DNS root zone — not registrations, not reserved names, not sunrise-blocked labels. This is the most accurate count of actually resolving domains.

MCP Server

nTLD.zone exposes a Model Context Protocol (MCP) server at:

https://ntld.zone/api/mcp

The endpoint uses Streamable HTTP (POST JSON-RPC). It is public, read-only, and requires no authentication.

Available Tools

ToolDescription
list_tldsList tracked TLDs with current counts, registry, operator, and growth. Filter by category, registry, backend, or name substring. Supports pagination.
get_tldFull detail for a single TLD: daily history (up to 365 days), launch phases, registrar market share, registry, and operator.
list_registriesRegistry groups with portfolio size (number of TLDs and total domains under management).
list_registrarsTop registrars aggregated across all TLDs by latest domains under management.
top_moversBiggest gainers and losers over 7-day or 30-day windows.
searchFuzzy search across TLDs, registries, and technical operators.

Connecting

Claude Desktop / Cursor

Add the following to your MCP settings:

{
  "mcpServers": {
    "ntld-zone": {
      "url": "https://ntld.zone/api/mcp"
    }
  }
}

ChatGPT / Custom clients

Use the endpoint directly with JSON-RPC 2.0 POST requests. Example curl:

curl -X POST https://ntld.zone/api/mcp \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{
    "jsonrpc": "2.0",
    "id": 1,
    "method": "tools/call",
    "params": {
      "name": "list_tlds",
      "arguments": { "limit": 5 }
    }
  }'

Machine-Readable Endpoints

EndpointFormatDescription
/llms.txtMarkdownSite map and data pointers for LLM crawlers
/llms-full.txtMarkdown tableFull snapshot of all TLDs, top registries, and operators. Refreshed daily. Cached 1 hour.
/api/mcpJSON-RPCMCP server endpoint (POST only). See MCP section above.
/sitemap.xmlXMLAll indexable page URLs with lastmod timestamps

License & Attribution

All nTLD.zone data is published under CC-BY-4.0 (Creative Commons Attribution 4.0 International).

You are free to use, share, adapt, and build upon the data for any purpose — including commercial use and AI training — provided you give appropriate credit.

Required attribution

Data from nTLD.zone (https://ntld.zone)

When republishing or referencing in academic work, please link to the source. For bulk data access or research collaborations, get in touch.

Data Freshness

Zone snapshot data reflects the previous day's CZDS files. ICANN typically publishes zone files with a 24–48 hour delay. Monthly registry reports reflect the prior calendar month. For the most current possible view, check the "Last data refresh" timestamp on the Dashboard.

Frequently asked questions

What is a new top-level domain (nTLD)?
New TLDs are the domain extensions ICANN delegated as part of the 2012 New gTLD Program — for example .app, .xyz, .online, .shop, and several hundred others. nTLD.zone tracks daily registration counts and operator data for every one of them.
Where does nTLD.zone get its data?
Daily zone files come from ICANN's Centralized Zone Data Service (CZDS), monthly domains-under-management figures from ICANN's monthly registry reports, and delegation/operator metadata from the IANA Root Zone Database.
How often is the data updated?
Zone snapshots are fetched once every 24 hours. Monthly registry reports are ingested within 1–3 days of ICANN publication. Launch phases are reviewed weekly.
Can I use this data in my own product or AI model?
Yes. All data is published under CC-BY-4.0 and is free to use commercially, including for AI training and retrieval, provided you credit nTLD.zone with a link to https://ntld.zone.
Is there a programmatic API?
Yes. nTLD.zone exposes a Model Context Protocol (MCP) server at https://ntld.zone/api/mcp, plus markdown snapshots at /llms.txt and /llms-full.txt.
What does 'domains live' mean versus 'registered'?
'Domains live' is the count of names actually delegated in the DNS root zone on a given day. 'Registered (official)' is the domains-under-management figure published by each registry's ICANN monthly report and is usually higher because it includes names registered but not yet resolving.