Domains

Domain privacy: understanding WHOIS and RDAP

Protecting a domain's public contact details does not mean deleting all of its registration data. To understand what is actually masked, you need to distinguish between public lookups, registry requirements, and your status as holder.

THE KEY POINTS

The short answer.

WHOIS/RDAP privacy limits the publication of certain contact details when supported. It does not remove the data required for registration, nor all of the domain's public technical elements, and does not guarantee absolute anonymity.

  • RDAP is a protocol for looking up registration data.
  • Protection depends on the extension, the registry, and the registrar.
  • Check which fields are actually published and who remains the domain holder.

01What are WHOIS and RDAP for?

WHOIS and RDAP allow you to look up information related to a domain's registration. RDAP offers a structured response format and mechanisms for differentiating access. It was designed to replace the WHOIS protocol, historically used for these lookups.

A public lookup may display elements such as the registrar, statuses, dates, or nameservers. The holder's contact details may be absent, masked, or replaced depending on the applicable rules. The result depends on the domain being queried, not just the lookup tool.

02Masked data does not mean nonexistent data

Data may be stored in the registrar's private space while not appearing in the public response. Privacy affects this publication. It does not exempt you from providing the accurate information required for the chosen extension.

You also need to distinguish between customer account information and the information required to register the domain. A portal that asks for little data to open an account does not prove that all registries will apply the same requirements to every extension.

03Confidentiality and proxy: what's the difference?

According to the distinction published by ICANN, a privacy service may replace the published contact details while keeping the customer as the registered holder. A proxy service, on the other hand, may become the holder listed in the registry. The contract is therefore just as important as the presentation of the public result.

Before activating a service, check who is listed as holder, how to receive communications, and how to handle a transfer. The goal of WispHost is to preserve your holder status while using the available official protection; masking of contact details must not be confused with a change of holder.

04Why does the result vary by extension?

Not all extensions fall under the same registry and do not necessarily offer the same fields or protections. A rule that applies to a generic extension must not be automatically extended to all country-code extensions. Check the conditions of the one you plan to use.

The phrase "WHOIS protection included" must therefore be read within its scope: compatible extensions, affected fields, and registrar conditions. It cannot be used to promise that the name, address, region, or country will disappear in all cases.

05How do you verify protection after activation?

Check the public result using the registry's RDAP service or a recognized tool, then verify the fields one by one. Next, check in your private space that your contact details are correct and that the contact arrangements remain usable. Keep the information needed to manage the domain.

  • Who is the registered holder?
  • Which fields are actually publicly visible?
  • How are messages intended for the holder forwarded?
  • Are the renewal and transfer conditions clear?

06Don't confuse availability with registration

The absence of a registration in a search is not a reservation. A name may be subject to special conditions, a different price, or become unavailable before validation by the registry. Availability checking and registration are two separate steps.

On WispHost, start by searching for your name and comparing extensions. Check the purchase price, renewal, and compatibility of protection before proceeding. For a specific privacy requirement, have the masked fields confirmed for the chosen extension rather than relying on a general promise.

Sources & references

To explore the technical points further and find the information at its source.

WISPHOST INFORMATION