xref: /dragonfly/usr.bin/whois/whois.1 (revision 2ee85085)
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: src/usr.bin/whois/whois.1,v 1.15.2.9 2002/11/17 15:05:55 mike Exp $
34.\" $DragonFly: src/usr.bin/whois/whois.1,v 1.4 2005/01/09 13:30:06 liamfoy Exp $
35.\"
36.Dd January 9, 2005
37.Dt WHOIS 1
38.Os
39.Sh NAME
40.Nm whois
41.Nd "Internet domain name and network number directory service"
42.Sh SYNOPSIS
43.Nm
44.Op Fl aAbdgiIklmQrR6
45.Op Fl c Ar country-code | Fl h Ar host
46.Op Fl p Ar port
47.Ar name ...
48.Sh DESCRIPTION
49The
50.Nm
51utility looks up records in the databases maintained by several
52Network Information Centers
53.Pq Tn NICs .
54.Pp
55The options are as follows:
56.Bl -tag -width indent
57.It Fl a
58Use the American Registry for Internet Numbers
59.Pq Tn ARIN
60database.
61It contains network numbers used in those parts of the world covered neither by
62.Tn APNIC
63nor by
64.Tn RIPE .
65.Pp
66(Hint: All point of contact handles in the
67.Tn ARIN
68whois database end with
69.Qq Li -ARIN . )
70.Pp
71.It Fl A
72Use the Asia/Pacific Network Information Center
73.Pq Tn APNIC
74database.
75It contains network numbers used in East Asia, Australia,
76New Zealand, and the Pacific islands.
77.It Fl b
78Use the Network Abuse Clearinghouse database.
79It contains addresses to which network abuse should be reported,
80indexed by domain name.
81.It Fl c Ar country-code
82This is the equivalent of using the
83.Fl h
84option with an argument of
85.Qq Ar country-code Ns Li .whois-servers.net .
86.It Fl d
87Use the US Department of Defense
88database.
89It contains points of contact for subdomains of
90.Pa .MIL .
91.It Fl g
92Use the US non-military federal government database, which contains points of
93contact for subdomains of
94.Pa .GOV .
95.It Fl h Ar host
96Use the specified host instead of the default variant.
97Either a host name or an IP address may be specified.
98.Pp
99By default
100.Nm
101constructs the name of a whois server to use from the top-level domain
102.Pq Tn TLD
103of the supplied (single) argument, and appending
104.Qq Li .whois-servers.net .
105This effectively allows a suitable whois server to be selected
106automatically for a large number of
107.Tn TLDs .
108.Pp
109In the event that an IP
110address is specified, the whois server will default to the American
111Registry for Internet Numbers
112.Pq Tn ARIN .
113If a query to
114.Tn ARIN
115references
116.Tn APNIC , LACNIC ,
117or
118.Tn RIPE ,
119that server will be queried also, provided that the
120.Fl Q
121option is not specified.
122.Pp
123If the query is not a domain name or IP address,
124.Nm
125will fall back to
126.Pa whois.crsnic.net .
127.It Fl i
128Use the Network Solutions Registry for Internet Numbers
129.Pq Pa whois.networksolutions.com
130database.
131It contains network numbers and domain contact information for most of
132.Pa .COM , .NET , .ORG
133and
134.Pa .EDU
135domains.
136.Pp
137.Sy NOTE !
138The registration of these domains is now done by a number of
139independent and competing registrars and this database holds no information
140on the domains registered by organizations other than Network Solutions, Inc.
141Also, note that the
142.Tn InterNIC
143database
144.Pq Pa whois.internic.net
145is no longer handled by Network Solutions, Inc.
146For details, see
147.Pa http://www.internic.net/ .
148.Pp
149(Hint: Contact information, identified by the term
150.Em handle ,
151can be looked up by prefixing
152.Qq Li "handle "
153to the
154.Tn NIC
155handle in the query.)
156.It Fl I
157Use the Internet Assigned Numbers Authority
158.Pq Tn IANA
159database.
160It contains network information for top-level domains.
161.It Fl k
162Use the National Internet Development Agency of Korea's
163.Pq Tn KRNIC
164database.
165It contains network numbers and domain contact information
166for Korea.
167.It Fl l
168Use the Latin American and Caribbean IP address Regional Registry
169.Pq Tn LACNIC
170database.
171It contains network numbers used in much of Latin America and the
172Caribbean.
173.It Fl m
174Use the Route Arbiter Database
175.Pq Tn RADB
176database.
177It contains route policy specifications for a large
178number of operators' networks.
179.It Fl p Ar port
180Connect to the whois server on
181.Ar port .
182If this option is not specified,
183.Nm
184defaults to port 43.
185.It Fl Q
186Do a quick lookup.
187This means that
188.Nm
189will not attempt to lookup the name in the authoritative whois
190server (if one is listed).
191This option has no effect when combined with any other options.
192.It Fl r
193Use the R\(aaeseaux IP Europ\(aaeens
194.Pq Tn RIPE
195database.
196It contains network numbers and domain contact information
197for Europe.
198.It Fl R
199Use the Russia Network Information Center
200.Pq Tn RIPN
201database.
202It contains network numbers and domain contact information
203for subdomains of
204.Pa .RU .
205This option is deprecated; use the
206.Fl c
207option with an argument of
208.Qq Li RU
209instead.
210.It Fl 6
211Use the IPv6 Resource Center
212.Pq Tn 6bone
213database.
214It contains network names and addresses for the IPv6 network.
215.El
216.Pp
217The operands specified to
218.Nm
219are treated independently and may be used
220as queries on different whois servers.
221.Sh EXAMPLES
222Most types of data, such as domain names and
223.Tn IP
224addresses, can be used as arguments to
225.Nm
226without any options, and
227.Nm
228will choose the correct whois server to query.
229Some exceptions, where
230.Nm
231will not be able to handle data correctly, are detailed below.
232.Pp
233To obtain contact information about an
234administrator located in the Russian
235.Tn TLD
236domain
237.Qq Li RU ,
238use the
239.Fl c
240option as shown in the following example, where
241.Ar CONTACT-ID
242is substituted with the actual contact identifier.
243.Pp
244.Dl "whois -c RU CONTACT-ID"
245.Pp
246(Note: This example is specific to the
247.Tn TLD
248.Qq Li RU ,
249but other
250.Tn TLDs
251can be queried by using a similar syntax.)
252.Pp
253The following example demonstrates how to obtain information about an
254.Tn IPv6
255address or hostname using the
256.Fl 6
257option, which directs the query to
258.Tn 6bone .
259.Pp
260.Dl "whois -6 IPv6-IP-Address"
261.Pp
262The following example demonstrates how to query
263a whois server using a non-standard port, where
264.Dq Li query-data
265is the query to be sent to
266.Dq Li whois.example.com
267on port
268.Dq Li rwhois
269(written numerically as 4321).
270.Pp
271.Dl "whois -h whois.example.com -p rwhois query-data"
272.Sh SEE ALSO
273.Rs
274.%A Ken Harrenstien
275.%A Vic White
276.%T NICNAME/WHOIS
277.%D 1 March 1982
278.%O RFC 812
279.Re
280.Sh HISTORY
281The
282.Nm
283command appeared in
284.Bx 4.3 .
285