What is Thick Lookup and Thin Lookup in Domain Expiry Monitor?
The Domain Expiry Monitor detects the expiry date of a domain via WHOIS records. WHOIS is a socket level protocol that runs over TCP port 43. A WHOIS client queries each server, starting from the root server until it receives a response containing the records.
Root (whois.iana.org) > Registry (TLD specific) > Registrar
WHOIS registries can be THICK or THIN. Most registries use a THICK model which stores the WHOIS records of all the domains they're responsible for.
Thin Lookups
Thin Lookups are those where the queried domain information is fetched from the Registrar's Whois Server. A few of the top level domains like .com, .net etc. implement Thin Lookups. Thin Lookup is one where you can only get to information about the registry. Given below are excerpts from a thin lookup for site24x7.com. Below are excerpts from a thin lookup for zoho.com.
Thick Lookups
Thick Lookups are those where the queried domain information is fetched from the Registry Server. Whenever such a domain is registered, or the user edits the WHOIS information of the domain, the registrar pushes the information to the registry.
Most TLDs maintain thick registries which contain all the information from registrars. Below are excerpts from a thick lookup for zoho.in.
There is no registrar lookup for a thick registry. The expiration date and other details are provided by the registry itself.
Root (whois.iana.org) > Registry (TLD specific) > Registrar
WHOIS registries can be THICK or THIN. Most registries use a THICK model which stores the WHOIS records of all the domains they're responsible for.
Thin Lookups
Thin Lookups are those where the queried domain information is fetched from the Registrar's Whois Server. A few of the top level domains like .com, .net etc. implement Thin Lookups. Thin Lookup is one where you can only get to information about the registry. Given below are excerpts from a thin lookup for site24x7.com. Below are excerpts from a thin lookup for zoho.com.
Thick Lookups
Thick Lookups are those where the queried domain information is fetched from the Registry Server. Whenever such a domain is registered, or the user edits the WHOIS information of the domain, the registrar pushes the information to the registry.
Most TLDs maintain thick registries which contain all the information from registrars. Below are excerpts from a thick lookup for zoho.in.
There is no registrar lookup for a thick registry. The expiration date and other details are provided by the registry itself.
Related Articles
Monitor and validate DNS IP changes using regex
DNS administrators often monitor their DNS servers to detect changes in domain resolution and ensure IP mappings remain secure and accurate. Problem When your organization adds or modifies an IP address for your domain name, it’s critical to: Be ...No data for service and process in Windows server monitor
If you see "No Data" for process and service metrics (such as CPU or memory usage of monitored services) in the Site24x7 Windows server monitor user interface, follow the troubleshooting steps below. Run PowerShell Commands Open PowerShell as ...Difference between a website monitor and a SOAP Web Service monitor
Website monitor will support monitoring of any web application via POST, GET and HEAD methods of configuration. Learn more on the performance metrics provided for a website monitor. SOAP Web Service monitors , on the other hand, lets you to ...Monitor websites that require a HTTP POST to determine availability
You can monitor websites that require HTTP POST to determine availability. You can configure HTTP request methods to be passed (POST/GET/HEAD/POST XML) under the HTTP Configuration while adding a monitor itself. Log in to the Site24x7 client and ...Monitor database issues for OpenCart or Joomla websites
Database issues for websites developed using OpenCart or Joomla can be identified by enabling a Content Match. Configure your website response such that a particular text is always present during all success responses and absent during all error ...