xref: /freebsd/usr.bin/whois/whois.1 (revision 5521ff5a4d1929056e7ffc982fac3341ca54df7c)
1.\" Copyright (c) 1985, 1990, 1993
2.\"	The Regents of the University of California.  All rights reserved.
3.\"
4.\" Redistribution and use in source and binary forms, with or without
5.\" modification, are permitted provided that the following conditions
6.\" are met:
7.\" 1. Redistributions of source code must retain the above copyright
8.\"    notice, this list of conditions and the following disclaimer.
9.\" 2. Redistributions in binary form must reproduce the above copyright
10.\"    notice, this list of conditions and the following disclaimer in the
11.\"    documentation and/or other materials provided with the distribution.
12.\" 3. All advertising materials mentioning features or use of this software
13.\"    must display the following acknowledgement:
14.\"	This product includes software developed by the University of
15.\"	California, Berkeley and its contributors.
16.\" 4. Neither the name of the University nor the names of its contributors
17.\"    may be used to endorse or promote products derived from this software
18.\"    without specific prior written permission.
19.\"
20.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
21.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
22.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
23.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
24.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
25.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
26.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
27.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
28.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
29.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
30.\" SUCH DAMAGE.
31.\"
32.\"     From: @(#)whois.1	8.1 (Berkeley) 6/6/93
33.\" $FreeBSD$
34.\"
35.Dd November 17, 1999
36.Dt WHOIS 1
37.Os
38.Sh NAME
39.Nm whois
40.Nd "Internet domain name and network number directory service"
41.Sh SYNOPSIS
42.Nm
43.Op Fl adgimpQrR6
44.Op Fl h Ar host
45.Ar name ...
46.Sh DESCRIPTION
47.Nm
48looks up records in the databases maintained by several
49Network Information Centers
50.Pq Tn NICs .
51.Pp
52The options are as follows:
53.Bl -tag -width indent
54.It Fl a
55Use the American Registry for Internet Numbers
56.Pq Tn ARIN
57database.
58It contains network numbers used in those parts of the world covered neither by
59.Tn APNIC
60nor by
61.Tn RIPE .
62Contact (handle) information should be looked up by appending
63.Qq Li -ARIN
64to the NIC handle:
65.Pp
66.Dl "$ whois -a foo3-ARIN"
67.Pp
68.It Fl d
69Use the US Department of Defense
70database.
71It contains points of contact for subdomains of
72.Pa .MIL .
73.It Fl g
74Use the US non-military federal government database, which contains points of
75contact for subdomains of
76.Pa .GOV .
77.It Fl h Ar host
78Use the specified host instead of the default variant.
79Either a host name or an IP address may be specified.
80.Pp
81By default
82.Nm
83constructs the name of a whois server to use from the top-level domain
84.Pq Tn TLD
85of the supplied (single) argument, and appending
86.Qq Li .whois-servers.net .
87This effectively allows a suitable whois server to be selected
88automatically for a large number of TLDs.
89.Pp
90In the event that an IP
91address is specified, the whois server will default to the American
92Registry for Internet Numbers
93.Pq Tn ARIN .
94If a query to
95.Tn ARIN
96references
97.Tn APNIC
98or
99.Tn RIPE ,
100that server will be queried also, provided that the
101.Fl Q
102option is not specified.
103.Pp
104If the query is not a domain name or IP address,
105.Nm
106will fall back to
107.Pa whois.crsnic.net .
108.It Fl i
109Use the Network Solutions Registry for Internet Numbers
110.Pq Pa whois.networksolutions.com
111database.
112It contains network numbers and domain contact information for most of
113.Pa .COM , .NET , .ORG
114and
115.Pa .EDU
116domains.
117.Pp
118.Sy NOTE !
119The registration of these domains is now done by a number of
120independent and competing registrars and this database holds no information
121on the domains registered by organizations other than Network Solutions, Inc.
122Also, note that the
123.Tn InterNIC
124database
125.Pq Pa whois.internic.net
126is no longer handled by Network Solutions, Inc.
127For details, see
128.Pa http://www.internic.net/ .
129.Pp
130Contact (handle) information should be looked up by prefixing
131.Qq Li "handle "
132to the NIC handle in the querry:
133.Pp
134.Dl "$ whois -i 'handle foo3'"
135.Pp
136.It Fl m
137Use the Route Arbiter Database
138.Pq Tn RADB
139database.
140It contains route policy specifications for a large
141number of operators' networks.
142.It Fl p
143Use the Asia/Pacific Network Information Center
144.Pq Tn APNIC
145database.
146It contains network numbers used in East Asia, Australia,
147New Zealand, and the Pacific islands.
148.It Fl Q
149Do a quick lookup.
150This means that
151.Nm
152will not attempt to lookup the name in the authoritative whois
153server (if one is listed) nor will it contact InterNic if a lookup
154fails.
155This flag has no effect when combined with any other flag.
156.It Fl r
157Use the R\(aaeseaux IP Europ\(aaeens
158.Pq Tn RIPE
159database.
160It contains network numbers and domain contact information
161for Europe.
162.It Fl R
163Use the Russia Network Information Center
164.Pq Tn RIPN
165database.
166It contains network numbers and domain contact information
167for subdomains of
168.Pa .RU .
169.It Fl 6
170Use the IPv6 Resource Center
171.Pq Tn 6bone
172database.
173It contains network names and addresses for the IPv6 network.
174.El
175.Pp
176The operands specified to
177.Nm
178are concatenated together (separated by white-space) and presented to
179the
180.Nm
181server.
182.Pp
183The default action, unless directed otherwise with a special
184.Ar name ,
185is to do a very broad search, looking for matches to
186.Ar name
187in all types of records and most fields (name, nicknames, hostname, net
188address, etc.) in the database.
189For more information as to what
190.Ar name
191operands have special meaning, and how to guide the search, use
192the special name
193.Dq Li help .
194.Sh SEE ALSO
195.Rs
196.%A Ken Harrenstien
197.%A Vic White
198.%T NICNAME/WHOIS
199.%D 1 March 1982
200.%O RFC 812
201.Re
202.Sh HISTORY
203The
204.Nm
205command appeared in
206.Bx 4.3 .
207