Thick vs. Thin Registry: Storage Concept for Domain Data
The management of domain data is carried out by so called registries the operators of top level domains (TLDs). These differ in two basic architectural models: Thick Registry and Thin Registry. The distinction applies exclusively to the storage location and scope of domain data.
1. THICK REGISTRY
In a Thick Registry, all relevant domain data is stored centrally at the registry. This includes:
Registrar information
Contact details of the domain holder (Registrant, Admin-C, Tech-C)
Nameservers
Domain status
Example TLDs:
.com, .net, .org (partially)
Advantages:
Complete WHOIS information can be retrieved directly from the registry
Centralized data storage simplifies consistent maintenance and queries
Disadvantages:
Data changes require interaction with the registry or via the respective registrar
Higher administrative workload on the registry side
2. THIN REGISTRY
In a Thin Registry, the registry only stores minimal master data:
Domain name
Registrar
Domain status
Detailed contact and owner data are stored exclusively by the respective registrar.
Example TLD:
.de (Germany)
Advantages:
Lower administrative effort for the registry
Decentralized data storage reduces load on central systems
Disadvantages:
Complete WHOIS information only available via the registrar
Multi-level query processes during research or incident handling
PRACTICAL NOTE
The choice of registration model directly affects:
Availability of WHOIS data
Processes for domain transfers or contact changes
Points of contact for incident or abuse reports
Our website does not currently provide any information on whether our TLD is a thick or thin domain. We are already working on completing this information.