Whois Proxy


Latest release: v. 1.3.4 (08 Jan 2008)

wp.cgi is an open source whois tool for looking up the owners, technical contacts and abuse desks of any domain, IPv4 or IPv6 number, NIC-Handle or ASN on the internet. (WP is NOT a cgi proxy!

No need to know which server to ask: WP discovers it for you. including both gTLDs and ccTLDs -- i.e. not just .com .net .org .edu, but also all others, including all the 2-letter country-code domains on the net that run a whois server on port 43. If they have no server on port 43, WP will return a link to their web whois (if they have one) or a related web site (if there is one).

wp.cgi runs either as a web application or on the command-line, depending on how it is called.

wp.cgi is a total rewrite of the famous Geek Tools Whois Proxy. It does all the things the other one does, and a few things more. It is all in perl, so it really should run anywhere. Tested on: Debian sid, RH7.1, OS X (Panther), AIX, FreeBSD, Digital Unix, and Windows with Apache and ActiveState Perl. Requires: Net::DNS perl libraries. Optional: HTML::Parser, Cache::FileCache (all available from CPAN.org).

The latest source code is available, under GNU license, and there is a working demo at http://jhbro.fr/cgi-bin/wp1.3.cgi.

The very latest code is obtainable from the CVS archives, including the most up-to-date version of the whoislist, and ZapTrash.config.

WP Home | Download | Install | Help | FAQ | CHANGES | Contact | Guestbook


wp.cgi can output (valid) HTML 4.01 (strict), or run on the command line. It uses the perl -w switch as well as the "strict pragma", and has all its functions encapsulated in fairly clear, generally small and neat subroutines, making it easier to maintain than its ancestor.

It is also configurable from a web form, so you should not even have to ever look at any perl code to get it up and running.

Among its configurable options are LogHits (self-expl), and "ZapTrash" (for those whois servers that are just so damn verbose with their disclaimers and copyright notices..) lets you suppress them. It is quite easy to expand the database of trash to zap. (But it is not recommended if you plan to run it as a public service..).

The form itself (or commandline switches) will allow you to accept Korean or Japanese or Chinese output. By default, output is ascii-only, and the queried server is told to reply in English (when that is an option).

It will also look up abuse addresses not only for domain names, but also for IP#s iff the reverse DNS for that number resolves, and you have checked the Ask AbuseNet option.

wp.cgi recursively strips long domain names (from the left) until one resolves. It automatically removes 3rd level domains and higher for .net .com .org .edu .gov .de .dk .no, and only searches on Domain.TLD.

Version History

v. 1.3.4 is another maintenancer release. The main change is we have reverted to HTML 4.01, and abandoned XHTML because the output of the queried whois servers is too variable and too often breaks the rules of XML/XHtml. HTML is far more forgiving, so we will stick with it.

v. 1.3.3 is a maintenance release. The main diffs is a new option to display all intermediate server output instead of only the last one, and updated whoistlist and ZapTrash.config. The function CheckSOA() has been disabled since whenever it happened to fail it would time out and we got a blank page -- not even an error message! This version also corrects a dumb wrapped line in wp.config which was causing lots of headaches for first-time installers.

v. 1.3.2 also supplies a tweak to convince whois.DeNic.DE to reply with more than "available/unavailable". Get the latest revision of wp.cgi from CVS.

v. 1.3.0 is i18n compatible. Default output is now UTF-8 rather than ISO-8859-1. We begin with English (US), German, French, and Vietnamese. New languages will be added as the translations come in. Note that this does NOT translate the output of the whois servers, but only that which is internal to wp. Several other tweaks also improve handling of ReferralServers.

v.1.3.0 has a new configurable option to cache results if you have the Cache::FileCache module, and have configured it to be on. This should significantly reduce the load both on your server and the nics' whois servers.
See Changes for more history.

Rate WP at CGIExpo.com/

WP Home | Download | Install | Help | FAQ | CHANGES | Contact | Guestbook

Valid CSS!Valid XHTML1.1! Copyright 2014 John Bro
All rights reserved.
Last Update 08 Jan 2008