The data, without
the interface.
The public site is generated from static data. This page documents the shape of that data, the fields the interface expects, and the authoritative sources each production field should resolve back to.
Small files with obvious jobs.
JSON
plannedplannedOne TLD record, explicit layers.
The fixture is deliberately smaller than the final schema. Production records should expand into nested source-specific sections rather than collapsing unrelated authorities into one convenient object.
{
"label": "xyz",
"display_label": ".xyz",
"idn": {
"is_idn": false,
"a_label": "xyz",
"u_label": null
},
"delegation": {
"currently_delegated": true,
"iana_type": "generic",
"sponsoring_organisation": "…",
"registration_date": "…"
},
"registry": {
"website": "…",
"rdap": "…",
"whois": "…"
},
"icann": {
"agreement_status": "active",
"spec_13_brand": false,
"spec_12_community": false
},
"provenance": {
"iana_root_database": "…",
"icann_registry_agreement": "…"
}
}
Fields should say what they mean, not more.
labelASCII protocol-safe TLD label without the leading dot.
IANA / rootdisplay_labelHuman-facing label, including native Unicode where applicable.
IANA + IDNA normalizationcurrently_delegatedWhether the label is present in the current delegated top-level namespace.
IANAiana_typeThe classification attached to the IANA root-zone record.
IANAsponsoring_organisationThe sponsoring organisation in the IANA record.
IANAagreement_statusStatus of the applicable ICANN registry agreement record.
ICANNspec_13_brandWhether the agreement material explicitly supports the Specification 13 brand attribute.
ICANNdnssec_ds_presentWhether DS material is present for the TLD in authoritative root data.
Root DNS / IANAProduction data should carry its receipts.
This site can document where data comes from; it should not invent licensing permissions on behalf of IANA, ICANN, registries, or other source providers.