npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

@ocku/whois

v1.1.5

Published

A low overhead asynchronous whois client for Node.js

Downloads

8

Readme

@ocku/whois

A low overhead asynchronous whois client for Node.js.

Usage

This library provides a simple interface consisting of a single asynchronous function. It can be used like this:

[!IMPORTANT]
The lookup function always returns a utf8 string.

// format: lookup(domain, options?)
import { lookup } from '@ocku/whois';
// or
const { lookup } = require('@ocku/whois');
// Query an ipv4 address
console.log(await lookup('1.1.1.1')); // ...

// Query an ipv6 address
console.log(await lookup('2606:4700:4700::1001')); // ...

// Query a domain
console.log(await lookup('lost.st')); // ...

// Query a domain with punycode
console.log(await lookup('lost.xn--tckwe')); // ...

// Query a tld
console.log(await lookup('de')); // ...

Configuration

Additionally, the behavior of the function can be customized with the optional options parameter, which has the following structure:

type LookupOptions = {
  follow?: number; // the maximum number of servers to follow.

  // type LookupServer
  server?: {
    // an optional server to use instead of choosing one automatically.
    host: string; // the host to connect to (add the port below, not here!)
    port?: number; // [default: 43] - this can be omitted most times.

    // when a whois message is sent, the (prefix, domain, and suffix) are joined by spaces.
    // this means that there's no need for trailing or leading spaces on {prefix} or {suffix}.
    prefix?: string; // [default: ''] - a string to send before the domain, usually handles (eg: '-T dn,ace' or 'n').
    suffix?: string; // [default: ''] - a string to send after the domain (uncommon, but here just in case).
    encoding?: string; // supported encodings: https://nodejs.org/docs/v20.1.0/api/util.html#encodings-supported-by-default-with-full-icu-data
  };
  timeout?: number; // a timeout in milliseconds.
  // allows you to make the request through a SOCKS proxy.
  // when present, socksClientOptions is directly passed to SocksClient.createConnection(1).
  // see https://www.npmjs.com/package/socks#quick-start-example
  socksClientOptions?: SocksClientOptions;
};

It can be used like this:

const options = { timeout: 10000 };
const res = await lookup('lost.st', options);
console.log(res); // ...

Punycode

Punycode domain lookups are supported, but to keep overhead low, special Unicode characters are not automatically transcoded to LDH.

For clarity:

const { toASCII } = require('punycode/');
// this is good
await lookup('nic.xn--tckwe'); // works
await lookup(toASCII('nic.コム')); // works
// this is bad
await lookup('nic.コム'); // goes through IANA, returns "No match"

Requirements

This library requires node 20.10.0 (LTS) to work.

Reference