xref: /netbsd/usr.bin/whois/whois.1 (revision bf9ec67e)
1.\"	$NetBSD: whois.1,v 1.17 2002/02/08 01:36:38 ross Exp $
2.\"
3.\" Copyright (c) 1985, 1990, 1993
4.\"	The Regents of the University of California.  All rights reserved.
5.\"
6.\" Redistribution and use in source and binary forms, with or without
7.\" modification, are permitted provided that the following conditions
8.\" are met:
9.\" 1. Redistributions of source code must retain the above copyright
10.\"    notice, this list of conditions and the following disclaimer.
11.\" 2. Redistributions in binary form must reproduce the above copyright
12.\"    notice, this list of conditions and the following disclaimer in the
13.\"    documentation and/or other materials provided with the distribution.
14.\" 3. All advertising materials mentioning features or use of this software
15.\"    must display the following acknowledgement:
16.\"	This product includes software developed by the University of
17.\"	California, Berkeley and its contributors.
18.\" 4. Neither the name of the University nor the names of its contributors
19.\"    may be used to endorse or promote products derived from this software
20.\"    without specific prior written permission.
21.\"
22.\" THIS SOFTWARE IS PROVIDED BY THE REGENTS AND CONTRIBUTORS ``AS IS'' AND
23.\" ANY EXPRESS OR IMPLIED WARRANTIES, INCLUDING, BUT NOT LIMITED TO, THE
24.\" IMPLIED WARRANTIES OF MERCHANTABILITY AND FITNESS FOR A PARTICULAR PURPOSE
25.\" ARE DISCLAIMED.  IN NO EVENT SHALL THE REGENTS OR CONTRIBUTORS BE LIABLE
26.\" FOR ANY DIRECT, INDIRECT, INCIDENTAL, SPECIAL, EXEMPLARY, OR CONSEQUENTIAL
27.\" DAMAGES (INCLUDING, BUT NOT LIMITED TO, PROCUREMENT OF SUBSTITUTE GOODS
28.\" OR SERVICES; LOSS OF USE, DATA, OR PROFITS; OR BUSINESS INTERRUPTION)
29.\" HOWEVER CAUSED AND ON ANY THEORY OF LIABILITY, WHETHER IN CONTRACT, STRICT
30.\" LIABILITY, OR TORT (INCLUDING NEGLIGENCE OR OTHERWISE) ARISING IN ANY WAY
31.\" OUT OF THE USE OF THIS SOFTWARE, EVEN IF ADVISED OF THE POSSIBILITY OF
32.\" SUCH DAMAGE.
33.\"
34.\"     @(#)whois.1	8.2 (Berkeley) 6/20/94
35.\"
36.Dd January 12, 2002
37.Dt WHOIS 1
38.Os
39.Sh NAME
40.Nm whois
41.Nd TCP/IP Internet directory service, RIPE version
42.Sh SYNOPSIS
43.Nm ""
44.Op Fl 46aFSrR
45.Op Fl h Ar host
46.Op Fl p Ar port
47.Op Fl i Ar attributes
48.Op Fl s Ar sources
49.Op Fl T Ns Ar \ types
50.Op Fl L | m | M
51.Ar identifier
52.Nm ""
53.Fl t Ar type
54.Nm ""
55.Fl v Ar type
56.Sh DESCRIPTION
57The
58.Nm
59program is a client implementation of the WHOIS protocol for querying
60databases and directory services on the Internet.
61Most often, it is used to query the domain name contact and administration
62databases of Internet Domain Name Registrars.
63.Pp
64The WHOIS protocol does not specify very much of the format of
65either the query or the servers' response.
66In essence, the protocol calls for a
67.Tn NETASCII
68word or phrase to be sent on a
69.Tn TCP
70connection to a
71.Tn WHOIS
72server, which then sends some amount of
73.Tn NETASCII
74in response on the same connection,
75closing the connection when it has finished sending.
76Necessarily, both the format and the content of the response will be server-dependent
77.Po
78e.g. what you get back depends on who you ask, and what you ask
79.Pc .
80.Pp
81By default,
82.Nm
83will send the query to
84.Qq whois.internic.net .
85.Pp
86When
87.Nm
88is used to query an Internet domain name registrar's database, the
89.Ar identifier
90can be either a name
91.Po
92e.g.
93.Qq Karrenberg
94.Pc ,
95a
96.Tn NIC-handle
97.Po
98e.g.
99.Qq DK58
100.Pc ,
101an IP network number
102.Po
103e.g.
104.Qq 192.87.45.0/24
105.Pc ,
106or a domain name
107.Po
108e.g.
109.Qq ripe.net
110.Pc .
111.Sh OPTIONS
112.Bl -tag -width indent
113.It Fl h Ar host
114Query a host other than the default.
115.It Fl p Ar port
116Connect to a
117.Tn TCP
118port other than 43 (the default).
119.El
120.Pp
121By default,
122.Nm
123will attempt to connect to a WHOIS server with both IPv6 and IPv4,
124in that order.
125To force one or the other transport:
126.Bl -tag -width indent
127.It Fl 4
128connect with IPv4/TCP only.
129.It Fl 6
130connect with IPv6/TCP only.
131.El
132.Ss RIPE specific extensions
133This version of
134.Nm
135implements protocol extensions compatible with a version of the RIPE
136database WHOIS server that supports classless IP addresses.
137All IP network numbers are considered classless IP network numbers of
138the form prefix/length, like 192.87.45.0/24 for a class C sized network
139number and 128.86.0.0/16 for a class B sized network number.
140Any length can be given.
141If no length is given, the server assumes a host lookup (i.e. length 32).
142.Pp
143By default, the server will return the first less specific network
144number, which can be an exact match if available in the database.
145.Bl -tag -width indent
146.It Fl a
147This causes the server to include information from
148non-RIPE WHOIS databases in the reply.
149Currently these are the public parts of the US NIC and NSFnet databases.
150Please note that the RIPE NCC does not maintain these databases.
151The information is included for for your convenience only.
152.It Fl F
153fast output.
154Force the WHOIS server to not reformat the output.
155This can save time for large objects.
156The output of the RIPE WHOIS server will be in two letter short form.
157This option implies -r.
158.It Fl L
159lookup all less specific networks.
160Has effect only when looking up IP network numbers.
161.It Fl m
162lookup first level more specific networks.
163Has effect only when looking up IP network numbers.
164.It Fl M
165lookup all more specific networks.
166Has effect only when looking up IP network numbers.
167.It Fl r
168non-recursive lookup.
169This will cause the server to not lookup referenced objects.
170.It Fl R
171suppress referrals.
172Forces local copy of a domain object to be shown even if it contains referral.
173.It Fl i Ar attributes
174attributes is a comma separated list of attributes.
175the WHOIS server will return all objects that match the search keys
176in one of these attributes.
177.It Fl s Ar sources
178sources is a comma separated list of database sources.
179The WHOIS server will only search the databases that match the
180specified sources.
181.It Fl S
182requests the server to leave out "syntactic sugar" that may normally
183be inserted in some database objects.
184.It Fl t Ar type
185requests the server to send a template for an object with type "type".
186.It Fl v Ar type
187requests the server to send a verbose template for an object with type "type".
188.It Fl T Ar types
189types is a comma separated list of object types.
190requests the server to only send back objects that match one of the "types".
191.El
192.Sh EXAMPLES
193.Bd -literal -offset indent
194$ whois karrenberg
195person:  Daniel Karrenberg
196address: RIPE Network Coordination Centre
197address: Kruislaan 409
198address: NL-1098 SJ Amsterdam
199address: Netherlands
200phone:   +31 20 5925065
201fax-no:  +31 20 5925155
202e-mail:  dfk@ripe.net
203nic-hdl: DK58
204changed: dfk@ripe.net 920407
205changed: ripe-dbm@ripe.net 920407
206source:  RIPE
207$ whois -h whois.ripe.net -r 192.87.45.0/24
208inetnum:     192.87.45.0
209netname:     RIPE-NCC
210descr:       RIPE Network Coordination Centre
211descr:       Amsterdam, Netherlands
212country:     NL
213admin-c:     Daniel Karrenberg
214tech-c:      Marten Terpstra
215connect:     RIPE NSF WCW
216aut-sys:     AS3333
217ias-int:     192.87.45.80  AS1104
218ias-int:     192.87.45.6   AS2122
219ias-int:     192.87.45.254 AS2600
220rev-srv:     ns.ripe.net
221rev-srv:     ns.eu.net
222notify:      ops@ripe.net
223changed:     tony@ripe.net 940110
224source:      RIPE
225.Ed
226.Ss Other Useful WHOIS Servers
227Herewith follows an incomplete list of other potentially useful
228WHOIS servers on the Internet.
229.Pp
230For information about IP address allocations,
231the registrars who handle those allocations are:
232.Bl -tag -width indent
233.It whois.arin.net
234American Registry for Internet Numbers.
235.It whois.apnic.net
236Asia-Pacific Network Information Center.
237.It whois.ripe.net
238Reseaux IP Europeens - Network Coordination Center.
239.El
240.Pp
241Internet domain names can now be registered through many different
242competing registrars, many of whom (but probably not all of whom)
243operate WHOIS servers:
244.Bl -tag -width indent
245.It whois.networksolutions.com
246Network Solutions, operators of the InterNIC.
247.It whois.ripe.net
248RIPE domains, assignments, \*[Am] routing info.
249.It whois.ra.net
250Merit/IRR routing info.
251.It whois.geektools.com
252recursing proxies that query internic.net.
253.It whois.fucknsi.com
254a meta-WHOIS server that attempts to query all the registrars.
255.It whois.opensrs.net
256same as above, but also authoritative for OpenSRS domain names.
257.El
258.Sh RIPE VERSION
259This is the RIPE version of the WHOIS client program.
260For questions refer to
261.Aq ncc@ripe.net .
262For more information about the RIPE database please also refer to
263.Aq ncc@ripe.net .
264.Sh SEE ALSO
265.Xr networks 5 ,
266.Xr bind 8 ,
267.Pa http://www.domainbuyersguide.com/
268.Rs
269.%R RFC
270.%N 812
271.%D March 1982
272.%T "NICNAME/WHOIS"
273.%O (Obsolete)
274.Re
275.Rs
276.%R RFC
277.%N 954
278.%D October 1985
279.%T "NICNAME/WHOIS"
280.Re
281.Sh BUGS
282Most of the extra flags are ONLY supported by the RIPE whois server,
283or copies of the same version of the software.
284Usage of these flags may cause errors on other whois servers.
285.Pp
286.Nm
287uses
288.Xr getaddrinfo 3
289functions, thus search order depends on the function.
290