Software Download

About whois

whois is a client for the WHOIS directory service.

Syntax

whois [ -h HOST ] [ -p PORT ] [ -aCFHlLMmrRSVx ] [ -g SOURCE:FIRST-LAST]

      [ -i ATTR ] [ -S SOURCE ] [ -T TYPE ] object

whois -t TYPE

whois -v TYPE

whois -q keyword

Description

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 anInternet 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.comfor NIC handles or whois.arin.net for IPv4 addresses and network names.

Options

-h HOST	Connect to WHOIS database host HOST.
-H	Suppress the display of legal disclaimers.
-p PORT	When connecting, connect to network port PORT.
--verbose	Operate verbosely.
--help	Display a help message, and exit.

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 the administrator was associated with. Since the advent of the commercialized Internet, multiple registrars, andspammers, 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 ofNetwork Solutions, Inc., General Atomics and AT&T. In 1999, management of the TLDs.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 becomeswhois.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:

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.

Examples

whois softwaresnomi.blogspot.com

Performs a whois query for the domain name softwaresnomi.blogspot.com.