WHOIS, RDAP and DNS FAQ

Direct answer: WHOIS and RDAP describe registration, DNS describes published services, and neither source alone proves who operates a website or whether a domain can be purchased.

For fields or behavior not settled by a short answer, use the lookup methodology and continue into the practical WHOIS guide before drawing a consequential registration conclusion.

A missing record is not a purchase promise: use the registration-and-DNS availability check to compare current evidence.

Match the question to the right evidence

Choose the evidence layer before interpreting a result: registration records answer sponsorship questions, DNS answers service-routing questions, and HTTP checks describe one observed response.

Who registered the domain?

Registration data names roles and contacts. It may be redacted or proxied, so compare the WHOIS response with structured RDAP evidence.

Where does the domain point?

DNS publishes delegation and service records. Inspect the current DNS records without treating a shared address as proof of ownership.

Is the website working?

An HTTP probe records one observation. Use the website uptime check, then verify repeated failures from another location.

Common domain research questions

Is WHOIS data always the domain owner's identity?

No. Records can be privacy protected, proxied, redacted, stale, or role-based. Treat them as registration evidence from a named source, not proof of who publishes a website.

Does no WHOIS result mean a domain is available?

No. The name may be reserved, blocked, premium, unsupported, or temporarily unavailable. Only a registrar's live registration flow can confirm availability and price.

Why do WHOIS and RDAP dates differ?

They may label different events or come from different parties. Compare the event type, timezone, responding service, and whether a date is a registry expiry or a registrar-facing renewal date.

Can a DNS lookup reveal the web host?

It identifies published DNS destinations. CDNs, reverse proxies, shared services, and separate mail infrastructure mean that an address is not automatically the origin host or site owner.

Is an uptime result global?

No. It is one observation from this server at one time. Regional routing, DNS, filtering, and application dependencies can make availability differ elsewhere.

Should I use WHOIS or RDAP?

Prefer RDAP when structured JSON, HTTPS, typed events, entity roles and notices are available. WHOIS remains useful for comparison and for services that still expose relevant legacy output, but its free-form text is harder to interpret consistently.

What does clientTransferProhibited mean?

It is a registrar-set EPP status that normally blocks transfer while the status remains active. It is not a website trust signal; confirm why the lock exists through the sponsoring registrar before changing it.

Do nameservers identify the website hosting company?

Not necessarily. Nameservers identify the authoritative DNS service. The website can use a different provider, a CDN, a reverse proxy, or addresses shared with unrelated sites.

Does a valid TLS certificate prove who owns a website?

No. It shows that a certificate was issued for the listed names and can be presented in a valid TLS connection. It does not by itself establish the legal identity or trustworthiness of the site operator.

What can reverse DNS establish?

A PTR lookup reports the hostname published by the address-space operator for an IP address. Forward-confirming that hostname can test consistency, but neither result proves who controls an application using the address.

Can a current lookup show the complete history of a domain?

No. Current WHOIS, RDAP and DNS results describe present or retained events from their sources. Historical research requires dated archives or observation datasets, each with its own collection gaps.

Do you retain my lookup?

Operational logs may temporarily record requests for reliability and abuse prevention. Do not submit secrets or unrelated personal data. See the privacy policy for details.