Who sponsors the registration?
Start with RDAP for typed events, entity roles and notices. Compare the WHOIS response only when legacy referral text or registry-specific presentation matters.
Inspect registration evidence
Direct answer: Enter a domain for a referral-aware WHOIS lookup, or choose RDAP, DNS, IP and website checks when the question requires a different evidence source.
Normalizes the domain
Finds the registry referral
Queries the responding service
Labels source and time
The complete domain and network tool directory is the canonical catalogue. Use these four investigation paths to avoid mixing registration, DNS, routing and website observations into one unsupported conclusion.
Start with a WHOIS lookup for the legacy referral chain, use RDAP when you need structured events and notices, and inspect DNS records separately when the question concerns live services rather than registration.
Start with RDAP for typed events, entity roles and notices. Compare the WHOIS response only when legacy referral text or registry-specific presentation matters.
Inspect registration evidenceA DNS report compares the record families visible to this resolver. Follow with a nameserver lookup when the question is whether delegation targets and their addresses can be reached.
Trace DNS evidenceIP WHOIS describes the registered address range and RIR source. An IP-to-ASN lookup adds routing context; neither result identifies the person using a shared or cloud address.
Research an IP addressThe uptime check records one bounded HTTP observation. Use separate certificate and response-header checks when TLS identity or browser policy is the actual question.
Observe website behaviorThese systems describe different objects. Start with the narrowest source that can answer the question, then add another layer only when it supplies different evidence.
| Your question | Start with | Evidence source | Do not conclude |
|---|---|---|---|
| Who sponsors this domain registration? | Domain RDAP | The registry or registrar RDAP service selected through authoritative routing. | That the registrant, website publisher and hosting customer are the same party. |
| What did the legacy registration service publish? | WHOIS lookup | IANA referral data followed by the usable registry or registrar port-43 service. | That a missing field never existed or that an empty response proves availability. |
| Where are web and mail services delegated now? | DNS report | Current DNS answers for address, mail, authority and policy record families. | That a CDN, shared address or nameserver operator owns the domain. |
| Which organization received an IP range? | IP registration lookup | The relevant Regional Internet Registry registration service. | That the allocation holder is the person operating a site on the address. |
| Did the website answer this probe? | Website observation | A bounded DNS, connection, TLS and HTTP request from this server at one time. | Continuous uptime, global reachability or the legal identity of the publisher. |

Since 28 January 2025, most generic top-level-domain registries and registrars have no longer been contractually required to provide WHOIS, while RDAP remains required. ICANN lists exceptions for .com, .name and .post. WHOIS still matters for services that continue to publish it and for coverage outside that contractual change.
RDAP uses HTTPS, structured events, entity roles and notices. ICANN documents the transition, while RFC 9224 explains how IANA bootstrap data locates the authoritative RDAP service.
Compare WHOIS and RDAP field by fieldProprietary archives and continuous probes require collected data. WhoisRequest.org does not manufacture that coverage. Instead, these working utilities help you preserve current evidence, define future checks and move verified observations into your own workflow.
Record registration, DNS, certificate and archived-web observations in a local worksheet, then export the evidence as CSV without claiming that a missing snapshot proves nothing existed.
Define the URL, interval, timeout, redirect policy, accepted status and content assertion before choosing a scheduler or monitoring provider.
Call every working lookup through one documented GET interface, or export a live result with its tool, source context, methodology link and observation time.
9 min · Guide
11 min · Guide
8 min · Guide
10 min · Guide
8 min · Guide
9 min · Guide
17 Oct 2026 · Report
17 Oct 2026 · Report
17 Oct 2026 · Report