The Tool Desk
Outbyte Driver Updater FREEScan for outdated or missing drivers - takes under a minuteDriver Scan →Outbyte PC Repair FREEClear out junk files and repair common Windows errorsFree Scan →Java does not provide a built-in WHOIS lookup through InetAddress: that class resolves host names to IP addresses and can perform reverse name lookups. Domain registration data is a different task. For generic top-level domains (gTLDs), ICANN made RDAP the definitive registration-data source on 28 January 2025, while retaining specified exceptions and not ending WHOIS everywhere. To query registration data from Java, discover the appropriate RDAP service, make the standardized HTTP request, and parse its JSON response.
Why Java name lookup is not a WHOIS lookup
InetAddress.getByName() resolves a host name to an IP address. getCanonicalHostName() can perform a reverse name lookup through the system resolver. Neither method returns the domain’s registrar, registration dates, nameservers as registration records, or other registration data. They answer a DNS-related question, not a registration-directory question. See Oracle’s Java SE 25 InetAddress API.
As an Amazon Associate I earn from qualifying purchases.
WHOIS is a separate protocol for querying registration data; ICANN identifies RFC 3912 as its protocol specification. RDAP—Registration Data Access Protocol—is its standardized successor for registration-data access. The phrase “WHOIS is dead in modern Java” is therefore shorthand for a change in the registration-data ecosystem, not a Java API that was removed.
Recommended Free Tools
What changed: RDAP is now the primary gTLD route
ICANN announced that, as of 28 January 2025, RDAP became the definitive source for delivering generic top-level domain registration information in place of sunsetted WHOIS services. Most contractual WHOIS obligations for gTLD registries and registrars ended at that transition. ICANN’s guidance identifies .com, .name, and .post as exceptions. This milestone is specific to gTLDs; it does not establish that WHOIS has disappeared for every top-level domain worldwide. Read ICANN’s transition announcement and RDAP user information.
#1 Best Overall
- Used Book in Good Condition
RDAP uses HTTP and defined query patterns. RFC 9082 directs clients to discover the appropriate service base URL through the IANA bootstrap registry, then append the specified query path; a client should not assume one registry endpoint works for every namespace. Responses use RDAP’s defined data structures, typically represented as JSON. The protocol and query rules are specified in RFC 9082.
ICANN describes RDAP’s advantages as more standardized access and response formats, internationalization support, secure access, authoritative service discovery, and differentiated access. These are protocol and ecosystem capabilities, not a guarantee that every provider exposes the same data or that any particular response is complete. More background is available on ICANN’s RDAP overview.
Ways to check a domain
| Approach | Best for | Automation and integration |
|---|---|---|
| ICANN Lookup in a browser | A person checking one domain interactively | Manual; no application integration required. Use ICANN Lookup. |
| ICANN’s open-source command-line RDAP client | Repeatable terminal queries or scripting workflows | More suitable for automation than a browser lookup; consult ICANN’s RDAP user information for the client resource. |
| A Java RDAP client or application integration | Registration lookups inside a Java application | Requires service discovery, an HTTP request, and response parsing; select an implementation appropriate to the namespaces and workflow you need. |
ICANN has reported more than 10 billion RDAP queries per month across all types of RDAP servers as a December 2024 estimate, alongside more than 40 known client implementations and more than 15 known server implementations on its user information page. These are ICANN-reported estimates and counts, not independent measurements or a guarantee of an implementation’s coverage.
How to structure an RDAP lookup in Java
A robust implementation follows the protocol’s discovery and query model rather than hardcoding a single registry host. At a high level:
- Choose the lookup target. Decide which domain name and namespace you are querying. The applicable RDAP service depends on the namespace and provider.
- Discover the service base URL. Consult the IANA RDAP bootstrap registry to find the authoritative service associated with the target. RFC 9082 describes this discovery approach; do not assume a universal endpoint.
- Build the defined query. Append the domain query path required by RFC 9082 to the discovered base URL, using the domain object query pattern.
- Send an HTTP request. RDAP is implemented over HTTP. Use your chosen Java HTTP client to request the resource and handle the returned status and response body according to your application’s needs.
- Parse the RDAP response. Read the returned RDAP JSON and account for absent or restricted fields. The service determines what data is available for that domain.
This is the architectural shape, not a drop-in Java library recipe. The cited sources establish the protocol and discovery pattern, but do not establish a particular current Java HTTP/JSON library, library version, rate limit, or comprehensive coverage of country-code TLDs. Those choices need to be verified against the implementation and services your application will actually use.
Independent reader supportYour contribution helps us test, update, and keep practical guides available for everyone.What to expect when a lookup returns little or no data
The requested field is not public
A public lookup may not expose nonpublic registration data. ICANN advises users to check public Lookup first. If a legitimate need remains, its Registration Data Request Service (RDRS) may provide a request path for participating registrars; otherwise, ICANN points users to the sponsoring registrar. RDRS availability depends on registrar participation. See ICANN’s transition guidance and Lookup.
RDAP does not provide the queried information
ICANN Lookup says a domain query may be redirected to the corresponding gTLD registry’s WHOIS service when the requested information is not available through RDAP. That fallback is a behavior of ICANN Lookup, not evidence that a Java RDAP client should silently substitute WHOIS for every failed RDAP request. See ICANN Lookup.
Do these 3 things before closing this tab:
1Scan for outdated or missing drivers - takes under a minute2Repair Windows errors before they cause bigger problems3Fix the driver behind crashes, sound loss and screen glitchesThe domain uses a namespace outside the stated gTLD transition
The 2025 change described by ICANN concerns gTLD registration data and contractual obligations. For another namespace, confirm which registration-data service applies rather than assuming the gTLD transition rules or endpoint are universal.
Quick Recap
Product prices and availability are accurate as of the date/time indicated and are subject to change. Any price and availability information displayed on Amazon at the time of purchase will apply.
