A reference layer for
the namespace.
gTLDs turns fragmented registry and root-zone information into a fast interface you can actually read. The point is not to rewrite the source material. The point is to make authoritative facts easier to find, compare, and verify.
The source material is excellent.
The browsing experience can be better.
IANA and ICANN publish the records that matter. But answering one practical question can mean moving between delegation pages, registry agreements, RDAP bootstrap data, IDN tables, and technical records.
This project is a presentation and normalization layer over those sources: one stable page per TLD, consistent field names, clear source links, fast local search, and enough explanation to understand what each field actually means.
A boringly strict set of rules.
Registry and delegation facts should resolve back to the authoritative IANA or ICANN record that supports them.
IANA classification, DNS delegation, ICANN agreement status, and contract attributes are related fields, not one homemade “type”.
A string looking descriptive does not prove its eligibility rules, purpose, price, popularity, safety, or registration restrictions.
The public site is plain HTML, CSS, JavaScript and data files. Primary content does not depend on a runtime API or database.
Search, stable URLs, readable technical records, source provenance, and resilient mobile layouts beat dashboard theatre.
What belongs here, and what does not.
- TLD identity and delegation state
- IANA classifications and sponsoring organisations
- ICANN registry agreements and explicit contract attributes
- RDAP, WHOIS, name servers and root DNSSEC signals
- IDN labels and protocol-safe A-label handling
- Source-grounded guides to the machinery around TLDs
- Who “should” use a TLD
- Registration eligibility without a source
- Trustworthiness or safety rankings
- Popularity claims without a defined dataset
- Registrar pricing or availability presented as registry fact
- Corporate ownership guessed from technical infrastructure
Source data in. Static reference out.
The production shape is intentionally simple. An offline updater fetches and validates official source material, normalizes it into a canonical dataset, then renders static pages and a compact search index.