Clients. Servers. Libraries.
Everything the public service runs on is published. Take the whole stack or borrow the parts you need.
[host]$ lft -S -E eggs.gnu.org:587 TTL LFT trace to eggs.gnu.org (209.51.188.92):587/tcp 1 192.0.2.1 0/1/1 ±0ms ** [neglected] no reply packets received from TTLs 2 through 4 5 nyiix-px.jfk01.twdx.net (198.32.160.208) 2/2/2 ±0ms 6 bbr02-ae-4-901.bos01.twdx.net (198.160.63.126) 7/7/7 ±0ms 7 dcr03-hu-0-8-0-0.bsn04.twdx.net (198.160.62.201) 7/7/7 ±0ms ** [firewall] the next gateway may statefully inspect packets 8 mass-ix.fsf.org (206.53.143.61) 7/7/7 ±0ms 9 [target open] eggs.gnu.org (209.51.188.92):587 7.4ms
LFT and WhoB
Layer Four Traceroute is the all-in-one traceroute: TCP, UDP, ICMP and RFC 1393 probes; firewall traversal; ECMP diamonds; path MTU discovery; continuous watch mode; AS annotation of every hop. WhoB is the likeable whois client that tells a network engineer everything about a routed address by typing one line and reading one line. They ship together.
Client software
Server software
Development libraries
C whois library
Full single and bulk pWhoIs support, plus functions for many other network registries and recursive lookups that dig until the answer is found. The current whois.c / whois.h ship inside LFT.
PHP client
Socket-level access to Prefix WhoIs from PHP for single lookups and batches. Requires PHP with sockets.
RIPE NCC RIS client
Companion PHP library resolving prefix data from RIPE NCC's Routing Information Service.
Built by other people
Prefix WhoIs is plain whois on TCP/43, so it fits anywhere a socket does. Community-maintained projects that build on it:
type=json.community·PythonBuilt something? Tell us and we will list it here.