Thick vs Thin WHOIS
Embed This Widget
Add the script tag and a data attribute to embed this widget.
Embed via iframe for maximum compatibility.
<iframe src="https://tldfyi.com/iframe/glossary/thick-vs-thin-whois/" width="420" height="400" frameborder="0" style="border:0;border-radius:10px;max-width:100%" loading="lazy"></iframe>
Paste this URL in WordPress, Medium, or any oEmbed-compatible platform.
https://tldfyi.com/glossary/thick-vs-thin-whois/
Add a dynamic SVG badge to your README or docs.
[](https://tldfyi.com/glossary/thick-vs-thin-whois/)
Use the native HTML custom element.
Thick and thin WHOIS describe two models for storing [[registrant]] contact data in a TLD's [[whois|WHOIS]] system. In the thin model, the [[registry-operator|registry]] stores only technical data (nameservers and [[registrar]] of record), while full contact details are held by the individual [[registrar]]; queries must be forwarded to the registrar's own WHOIS server for complete records. In the thick model, the registry centralizes all contact data — registrant, administrative, and technical contacts — in a single authoritative database. ICANN mandated that .com and .net migrate from thin to thick WHOIS in 2013, improving data consistency. All new [[gtld|gTLDs]] operate thick WHOIS under the 2012 [[raa|RAA]].
Example
Before 2013, a .com WHOIS query returned minimal data from Verisign's registry, then pointed you to the registrar's own WHOIS server for contact details — the thin model. Post-migration, Verisign's thick WHOIS returns all registrant and contact information directly.