whois searches for an object in a WHOIS database. WHOIS is a query and response protocol that is widely used for querying databases that store the registered users of an Internet resource, such as a domain name or an IPaddress block, but is also used for a wider range of other information.
Most modern versions of whois try to guess the right server to ask for the specified object. If no guess can be made, whois will connect to whois.networksolutions.com for NIC handles or whois.arin.net for IPv4 addresses and network names.
When the Internet was first emerging from the primordial ooze of the ARPANET, there was only one organization that handled all domain registrations: DARPA. WHOIS was developed (and standardized in the early '80s) to look up domains, people and other resources related to domain and number registrations. Because all registration was done by one organization at that time, there was one centralized server for all WHOIS queries. This made looking up WHOIS information very easy.
The first WHOIS servers were highly permissive and would allow wildcard searches. A WHOIS query of a person's last name would yield all individuals with that name; a query with a given keyword returned all registered domains containing that keyword. A query for a given administrative contact returned all domains associated with the administrator. Since the advent of the commercialized Internet, multiple registrars, and spammers, such permissive searching is no longer available.
Responsibility of domain registration remained with DARPA as the ARPANET became the Internet during the 1980s. Then the National Science Foundation directed that management of Internet domain registration would be handled by commercial, third-party entities. InterNIC was formed in 1993 under contract with the NSF, consisting of Network Solutions, Inc., General Atomics and AT&T. In 1999, management of the TLD.com, .net, and .org was assigned to ICANN.
By 2005, there were many more generic top-level domains than there had been in the early 1980s, and many more country-code top-level domains. This led to a complex network of domain name registrars and registrar associations, especially as the management of Internet infrastructure became more internationalized. As a result, performing a WHOIS query on a domain now requires knowing the correct, authoritative WHOIS server to use, and tools to do WHOIS proxy searches have become common.
In 2004, an IETF committee was formed to create a new standard for looking up information on domain names and network numbers. The current working name for this proposed new standard is Cross Registry Information Service Protocol, or CRISP. It is intended to someday replace WHOIS, but is currently still in development.
Technical Notes
Please remember that whois.networksolutions.com by default will only search in the domains database. If you want to search for NIC handles you have to prepend a "!" character. When you do this, the default server becomes whois.networksolutions.com.
When querying whois.arin.net for IPv4 or IPv6 networks, the CIDR netmask length will be automatically removed from the query string.
When querying whois.nic.ad.jp for AS numbers, the program will automatically convert the request in the appropriate format, inserting a space after the string AS.
When querying whois.denic.de for domain names and no other flags have been specified, the program will automatically add the flag -T dn.
When querying whois.dk-hostmaster.dk for domain names and no other flags have been specified, the program will automatically add the flag --show-handles.
If the /etc/whois.conf config file exists, it will be consulted to find a server before applying the normal rules. Each line of the file should contain a regular expression to be matched against the query text and the WHOIS server to use, separated by white space. IDN domains must use the ACE (Ascii Compatible Encoding) format.
The WHOIS protocol does not specify an encoding for characters which cannot be represented by ASCII and implementations vary wildly. If the program knows that a specific server uses a certain encoding, if needed it will transcode the server output to the encoding specified by the current system locale.
Command linearguments will always be interpreted accordingly to the current system locale and converted to the IDN ASCII Compatible Encoding.
Configuration
The whois configuration file is located at /etc/whois.conf by default.
Environment
The following environment variables affect the operation of whois:
LANG
When querying whois.nic.ad.jp and whois.jprs.jp, English text is requested unless the LANG or LC_MESSAGES environment variables specify a Japanese locale.
WHOIS_OPTIONS
A list of options which will be evaluated before the ones specified on the command line.
WHOIS_SERVER
This server will be queried if the program cannot guess where some kind of objects are located. If the variable does not exist then whois.arin.net will be queried.
查看英文版
查看中文版
whois 例子
whois computerhope.com
對域名computerhope.com執行whois查詢。
whois computerhope.com
Performs a whois query for the domain name computerhope.com.
whois (WHOIS目錄服務的客戶端)
在類似Unix的操作系統上，whois命令是WHOIS目錄服務的客戶端。
On Unix-like operating systems, the whois command is a client for the WHOIS directory service.
查看英文版
查看中文版
1 whois 運行系統環境
2 whois 描述
3 whois 語法
4 whois 例子
whois 運行系統環境
Unix&Linux
whois 描述
whois在WHOIS數據庫中搜索對象。WHOIS是一種查詢和響應協議，它廣泛用于查詢存儲Internet資源（例如域名或IP地址塊）的注冊用戶的數據庫，但也可用于更廣泛的其他信息。
Whois的大多數現代版本都嘗試猜測正確的服務器來請求指定的對象。如果無法猜測，whois將連接到whois.networksolutions.com（用于NIC句柄）或whois.arin.net（用于獲取IPv4地址和網絡名稱）。
whois searches for an object in a WHOIS database. WHOIS is a query and response protocol that is widely used for querying databases that store the registered users of an Internet resource, such as a domain name or an IP address block, but is also used for a wider range of other information.
Most modern versions of whois try to guess the right server to ask for the specified object. If no guess can be made, whois will connect to whois.networksolutions.com for NIC handles or whois.arin.net for IPv4 addresses and network names.
查看英文版
查看中文版
whois 語法
whois [ -h HOST ] [ -p PORT ] [ -aCFHlLMmrRSVx ] [ -g SOURCE:FIRST-LAST ] [ -i ATTR ] [ -S SOURCE ] [ -T TYPE ] object選件
歷史
當Internet從ARPANET的原始滲入中首次出現時，只有一個組織可以處理所有域注冊：DARPA。WHOIS的開發（并在80年代初進行了標準化）旨在查找與域名和號碼注冊相關的域名，人員和其他資源。因為所有注冊當時都是由一個組織完成的，所以所有的WHOIS查詢都只有一臺中央服務器。這使得查找WHOIS信息非常容易。
首批WHOIS服務器是高度允許的，并允許通配符搜索。對一個人的姓氏進行WHOIS查詢將產生所有具有該名字的人；使用給定關鍵字的查詢將返回包含該關鍵字的所有注冊域。對給定管理聯系人的查詢返回了與管理員關聯的所有域。自從商業化的Internet，多個注冊服務商和垃圾郵件發送者出現以來，這種允許的搜索就不再可用。
隨著ARPANET在1980年代成為互聯網，DARPA仍然負責域名注冊。然后，美國國家科學基金會（National Science Foundation）指示，互聯網域名注冊的管理應由商業第三方實體進行。InterNIC于1993年與NSF簽約，后者由Network Solutions，Inc.，General Atomics和AT＆T組成。在1999年，TLD .com，.net和.org的管理已分配給ICANN。
到2005年，通用頂級域名的數量比1980年代初的數量要多，并且國家代碼頂級域名的數量也更多。這導致了域名注冊商和注冊商協會的復雜網絡，特別是隨著Internet基礎設施的管理變得更加國際化。結果，在域上執行WHOIS查詢現在需要知道要使用的正確，權威的WHOIS服務器，并且進行WHOIS代理搜索的工具已經很普遍。
2004年，成立了IETF委員會，以創建用于查找域名和網絡號信息的新標準。該提議的新標準的當前工作名稱是“交叉注冊中心信息服務協議”或CRISP。打算有一天取代WHOIS，但目前仍在開發中。
技術說明
請記住，默認情況下whois.networksolutions.com僅在域數據庫中搜索。如果要搜索NIC句柄，則必須在前面加上“ ！ ”字符。執行此操作時，默認服務器將變為whois.networksolutions.com。
當查詢whois.arin.net的IPv4或IPv6網絡時，CIDR網絡掩碼長度將自動從查詢字符串中刪除。
當查詢whois.nic.ad.jp的AS編號時，程序將自動以適當的格式轉換請求，并在字符串AS后面插入一個空格。
當查詢whois.denic.de的域名并且未指定其他標志時，程序將自動添加標志-T dn。
當查詢whois.dk-hostmaster.dk的域名并且未指定其他標志時，程序將自動添加標志--show-handles。
如果存在/etc/whois.conf配置文件，則在應用常規規則之前將先咨詢它以查找服務器。文件的每一行都應包含一個正則表達式，以與查詢文本和要使用的WHOIS服務器進行匹配，并用空格隔開。IDN域必須使用ACE（Ascii兼容編碼）格式。
WHOIS協議未為無法用ASCII表示的字符指定編碼，并且實現方式千差萬別。如果程序知道特定服務器使用某種編碼，則如果需要，它將把服務器輸出轉碼為當前系統區域設置指定的編碼。
命令行 參數將始終根據當前系統區域設置進行解釋，并轉換為IDN ASCII兼容編碼。
組態
默認情況下，whois配置文件位于/etc/whois.conf中。
環境
以下環境變量會影響whois的操作：
whois [ -h HOST ] [ -p PORT ] [ -aCFHlLMmrRSVx ] [ -g SOURCE:FIRST-LAST ] [ -i ATTR ] [ -S SOURCE ] [ -T TYPE ] objectOptions
History
When the Internet was first emerging from the primordial ooze of the ARPANET, there was only one organization that handled all domain registrations: DARPA. WHOIS was developed (and standardized in the early '80s) to look up domains, people and other resources related to domain and number registrations. Because all registration was done by one organization at that time, there was one centralized server for all WHOIS queries. This made looking up WHOIS information very easy.
The first WHOIS servers were highly permissive and would allow wildcard searches. A WHOIS query of a person's last name would yield all individuals with that name; a query with a given keyword returned all registered domains containing that keyword. A query for a given administrative contact returned all domains associated with the administrator. Since the advent of the commercialized Internet, multiple registrars, and spammers, such permissive searching is no longer available.
Responsibility of domain registration remained with DARPA as the ARPANET became the Internet during the 1980s. Then the National Science Foundation directed that management of Internet domain registration would be handled by commercial, third-party entities. InterNIC was formed in 1993 under contract with the NSF, consisting of Network Solutions, Inc., General Atomics and AT&T. In 1999, management of the TLD .com, .net, and .org was assigned to ICANN.
By 2005, there were many more generic top-level domains than there had been in the early 1980s, and many more country-code top-level domains. This led to a complex network of domain name registrars and registrar associations, especially as the management of Internet infrastructure became more internationalized. As a result, performing a WHOIS query on a domain now requires knowing the correct, authoritative WHOIS server to use, and tools to do WHOIS proxy searches have become common.
In 2004, an IETF committee was formed to create a new standard for looking up information on domain names and network numbers. The current working name for this proposed new standard is Cross Registry Information Service Protocol, or CRISP. It is intended to someday replace WHOIS, but is currently still in development.
Technical Notes
Please remember that whois.networksolutions.com by default will only search in the domains database. If you want to search for NIC handles you have to prepend a "!" character. When you do this, the default server becomes whois.networksolutions.com.
When querying whois.arin.net for IPv4 or IPv6 networks, the CIDR netmask length will be automatically removed from the query string.
When querying whois.nic.ad.jp for AS numbers, the program will automatically convert the request in the appropriate format, inserting a space after the string AS.
When querying whois.denic.de for domain names and no other flags have been specified, the program will automatically add the flag -T dn.
When querying whois.dk-hostmaster.dk for domain names and no other flags have been specified, the program will automatically add the flag --show-handles.
If the /etc/whois.conf config file exists, it will be consulted to find a server before applying the normal rules. Each line of the file should contain a regular expression to be matched against the query text and the WHOIS server to use, separated by white space. IDN domains must use the ACE (Ascii Compatible Encoding) format.
The WHOIS protocol does not specify an encoding for characters which cannot be represented by ASCII and implementations vary wildly. If the program knows that a specific server uses a certain encoding, if needed it will transcode the server output to the encoding specified by the current system locale.
Command line arguments will always be interpreted accordingly to the current system locale and converted to the IDN ASCII Compatible Encoding.
Configuration
The whois configuration file is located at /etc/whois.conf by default.
Environment
The following environment variables affect the operation of whois:
查看英文版
查看中文版
whois 例子
對域名computerhope.com執行whois查詢。
Performs a whois query for the domain name computerhope.com.
查看英文版
查看中文版
其他命令行
whereis | write | wc | which | w | whatis | who | whoami | wait | wall |