Skip to content
AdminKit

WHOIS

What is WHOIS?

WHOIS is a simple TCP query/response protocol, defined in RFC 3912, for looking up who registered a domain name or IP address block, with no authentication and an undefined response structure. AdminKit's Whois/RDAP tool looks up a domain or IP's registration details using RDAP, the newer, structured protocol gradually replacing it.

By AdminKit team, Netbase JSC · Updated

WHOIS is a simple TCP-based query/response protocol, defined in RFC 3912 (listed on the IETF Datatracker as informational, reflecting its unreformed, pre-standards-track origins), for looking up who registered a domain name or IP address block. A client opens a connection to port 43 of the responsible WHOIS server, sends the name being queried, and the server replies with a block of human-readable text before closing the connection — there’s no authentication, and RFC 3912 deliberately leaves the response’s structure undefined, acknowledging the protocol “lacks many of the protocol design attributes” expected of a modern IETF standard, kept this way for historic compatibility rather than reformed.

Because each registry formats, labels and discloses fields differently, and redacting data for privacy rules like GDPR is inconsistent across that unstructured text, RDAP — a newer, JSON-based, schema-consistent protocol defined in RFC 9083 — is gradually replacing it as the standard way to query registration data; for the gTLD registries and registrars ICANN oversees, ICANN’s own WHOIS/RDAP policy page lists the contractual provisions requiring each to publish this registration data. ARIN’s Whois/RDAP page draws the same contrast for IP and ASN data: RDAP is an HTTP-based REST-style protocol with standardized responses in JSON, whereas WHOIS is a text-based protocol using a specialized protocol and port. The organization name behind an ordinary public IP lookup comes from this same registration data — see what your IP lookup result actually shows for how to read it. That registration data is maintained by whichever Regional Internet Registry allocated the queried block in the first place.

AdminKit groups wHOIS under its DNS cluster — browse the AdminKit glossary index for other related terms.

Frequently asked questions

Is a WHOIS lookup authenticated?

No -- a client just opens a connection to port 43 of the responsible WHOIS server and sends the name being queried; RFC 3912 defines no authentication step at all.

Why is RDAP gradually replacing WHOIS?

Each WHOIS registry formats, labels and discloses fields differently, and redacting data for privacy rules like GDPR is inconsistent across that unstructured text. RDAP (RFC 9083) is a newer, JSON-based, schema-consistent protocol built to fix exactly that inconsistency.

Does RFC 3912 define a fixed structure for a WHOIS response?

No -- RFC 3912 deliberately leaves the response's structure undefined, acknowledging the protocol "lacks many of the protocol design attributes" expected of a modern IETF standard, kept this way for historic compatibility rather than reformed.

Who maintains the registration data a WHOIS lookup returns?

Whichever Regional Internet Registry allocated the queried IP block in the first place, or the relevant domain registry/registrar for a domain name lookup.