OpenGrok

whois.1 revision 1.1.1.4

RIPE version marten (at] ripe.net 1.10 94/09/07
whois - TCP/IP Internet directory service, RIPE version whois [ -aFSrR ] [ -h host ] [ -p port ] [ -i attributes ] [ -s sources ] [ -T types ] [ -L | -m | -M ] identifier whois -t type whois -v type whois searches for an object in the RIPE Network Management database. The key can be either a name (such as "Karrenberg"),a nic-handle (such as "DK58"), a network number ("192.87.45.0/24") or a domain name ("ripe.net"). This version of the whois client works with a version of the RIPE database whois server that supports classless IP addresses. All IP network numbers are considered classless IP network numbers of the form prefix/length, like 192.87.45.0/24 for a class C sized network number and 128.86.0.0/16 for a class B sized network number. Any length can be given. If no length is given, the server assumes a host lookup (ie length 32). By default, the server will return the first less specific network number, which can be an exact match if available in the database.

8 -a This causes the server to include information from non-RIPE whois databases in the reply. Currently these are the public parts of the US NIC and NSFnet databases. Please note that the RIPE NCC does not maintain these databases. The information is included for for your convenience only.

8 -F fast output. Force the whois server to not reformat the output. This can save time for large objects. The output of the RIPE whois server will be in two letter short form. This option implies -r.

8 -h host Select alternate host to direct the query

8 -p port Connect to port 'port'

8 -L lookup all less specific networks. Has effect only when looking up IP network numbers.

8 -m lookup first level more specific networks. Has effect only when looking up IP network numbers.

8 -M lookup all more specific networks. Has effect only when looking up IP network numbers.

8 -r non-recursive lookup. This will cause the server to not lookup referenced objects.

8 -R suppress referrals. Forces local copy of a domain object to be shown even if it contains referral.

8 -i attributes attributes is a comma separated list of attributes. the whois server will return all objects that match the search keys in one of these attributes.

8 -s sources sources is a comma separated list of database sources. The whois server will only search the databases that match the specified sources.

8 -S requests the server to leave out "syntactic sugar" that may normally be inserted in some database objects.

8 -t type requests the server to send a template for an object with type "type".

8 -v type requests the server to send a verbose template for an object with type "type".

8 -T types types is a comma separated list of object types. requests the server to only send back objects that match one of the "types".

8

example% whois karrenberg person: Daniel Karrenberg address: RIPE Network Coordination Centre address: Kruislaan 409 address: NL-1098 SJ Amsterdam address: Netherlands phone: +31 20 5925065 fax-no: +31 20 5925155 e-mail: dfk (at] ripe.net nic-hdl: DK58 changed: dfk (at] ripe.net 920407 changed: ripe-dbm (at] ripe.net 920407 source: RIPE example% whois -h whois.ripe.net -r 192.87.45.0/24 inetnum: 192.87.45.0 netname: RIPE-NCC descr: RIPE Network Coordination Centre descr: Amsterdam, Netherlands country: NL admin-c: Daniel Karrenberg tech-c: Marten Terpstra connect: RIPE NSF WCW aut-sys: AS3333 ias-int: 192.87.45.80 AS1104 ias-int: 192.87.45.6 AS2122 ias-int: 192.87.45.254 AS2600 rev-srv: ns.ripe.net rev-srv: ns.eu.net notify: ops (at] ripe.net changed: tony (at] ripe.net 940110 source: RIPE

This is the RIPE version of the whois client program. This is intended for European users as it will query a RIPE whois server by default rather than the US NIC whois server. For questions refer to <ncc (at] ripe.net>. For more information about the RIPE database please also refer to <ncc (at] ripe.net> This version also includes a compiled-in option to find secondary RIPE database servers closer to your machine, if there are any.

Most of the extra flags are ONLY supported by the RIPE whois server, or copies of the same version of the software. Usage of these flags may cause errors on other whois servers. .SH SEE ALSO
RFC 812: NICNAME/WHOIS

Indexes created Thu Oct 30 16:09:53 GMT 2025