WHOIS privacy, often called Domain Privacy, is designed to reduce the public exposure of personal domain-registration information such as a registrant’s name, address, phone number, or direct email address where the TLD and applicable policy allow it.
But in 2026, there is an important update to understand: for generic top-level domains, RDAP is now the primary modern protocol for registration data. ICANN made RDAP the definitive source for gTLD registration information beginning January 28, 2025, replacing the legacy WHOIS model for most gTLD registration-data access.
The industry still commonly uses the term “WHOIS privacy,” so this guide uses both terms. The more accurate question today is:
What registration data is public through RDAP or other registration-data services, what is redacted or replaced, and what information does the registrar still retain?
For NiceNIC customers, eligible domains currently receive free Domain Privacy with registration, renewal, transfer, and reactivation where registry and policy rules permit it. You can also review the NiceNIC Domain Privacy service or check the public output for a domain with the NiceNIC domain lookup tool.
For the current policy framework, see the ICANN Registration Data Policy and ICANN's RDAP and WHOIS transition notice.
Quick Answer: What Does WHOIS Privacy Actually Do?
WHOIS vs RDAP: What Changed?
For decades, people used the word WHOIS for public domain-registration lookups.
That terminology is still common, but the technical system has changed.
ICANN states that as of January 28, 2025, the Registration Data Access Protocol (RDAP) became the definitive source for delivering gTLD registration information in place of the sunsetted WHOIS services for most gTLDs.
RDAP provides advantages including:
- standardized structured responses;
- internationalization support;
- secure access mechanisms;
- authoritative service discovery;
- the ability to provide differentiated access to registration data.
You can check gTLD registration data through the ICANN Lookup service or use the NiceNIC domain lookup tool.
Practical point: Users still search for "WHOIS privacy," but modern gTLD registration-data lookups are increasingly an RDAP question.
What Registration Data Does a Registrar Still Collect?
Privacy does not mean the registrar stops collecting registration data.
Under the current ICANN Registration Data Policy for applicable gTLDs, registrars are required to collect or generate registration information that can include:
- domain name;
- registrar details;
- domain status;
- registrant name;
- street address;
- city;
- state or province where applicable;
- postal code where applicable;
- country;
- phone number;
- email address;
- registration-expiration information.
That means:
"Not publicly displayed" does not mean "the registrar does not have it."
Registrants should therefore provide accurate registration information even when public output is redacted or a privacy service is active.
What Information Can Still Be Public?
Domain Privacy does not make the entire registration record disappear.
For applicable gTLDs, public registration-data output can still include information such as:
- domain name;
- registrar name and IANA ID;
- registrar URL;
- domain creation date;
- expiration information;
- domain status codes;
- nameservers;
- DNSSEC information where applicable;
- registrar abuse-contact information.
Some registrant-related fields may be redacted, pseudonymized, replaced, or handled differently depending on:
- applicable law;
- ICANN policy;
- registry requirements;
- the registrar's privacy/proxy implementation;
- the registrant's consent where relevant.
This is why “WHOIS privacy hides everything” is incorrect.
Domain Privacy vs Policy Redaction: They Are Not Exactly the Same Thing
This distinction is increasingly important.
Policy redaction
Under the ICANN Registration Data Policy, a registrar or registry can be required or permitted to redact certain personal registration-data fields from public RDDS/RDAP output depending on applicable law and policy conditions.
In that situation, public output may show a value as redacted rather than displaying the underlying personal information.
Privacy or proxy service
A dedicated privacy or proxy service is a separate service layer.
Where an applicable privacy or proxy service is used, the public registration data associated with that service may be displayed according to the relevant policy and service model.
Both can reduce direct public exposure of personal registration data, but they are not technically identical.
What Does NiceNIC Domain Privacy Do?
NiceNIC currently adds free Domain Privacy to eligible domains during:
- registration;
- renewal;
- transfer;
- reactivation.
NiceNIC’s current support guidance states that Domain Privacy is enabled for eligible TLDs and that some extensions cannot use the service because of registry restrictions.
Before registering an extension, check the current NiceNIC Domain Privacy eligibility guide.
You can also review the dedicated NiceNIC Domain Privacy page.
Important: Do not assume every ccTLD or restricted TLD supports the same privacy model. Registry rules can differ substantially.
Does Domain Privacy Change Who Controls the Domain?
Enabling a privacy service should not be confused with selling or transferring the domain to somebody else.
Domain Privacy changes what registration information is publicly displayed. It does not by itself perform a domain transfer or move the registration into another registrar account.
For valuable domains, keep separate records showing:
- registrar account;
- registrant information;
- purchase records;
- invoices;
- transfer history;
- internal ownership authorization.
Do not rely only on a public WHOIS or RDAP result to establish who controls a business-critical domain.
Does Domain Privacy Make You Anonymous?
No.
Domain Privacy reduces public exposure. It does not create absolute anonymity.
Your registrar can still retain underlying registration information and may have obligations involving:
- ICANN policy;
- registry requirements;
- verification;
- data escrow;
- lawful disclosure requests;
- court orders;
- dispute-resolution procedures;
- applicable law.
The correct expectation is:
Privacy from routine public lookup is not immunity from legitimate legal or policy-based disclosure.
Can Someone Still Contact the Domain Holder?
Potentially, yes.
Where a registrar redacts a registrant email under the ICANN Registration Data Policy, the applicable registration-data output can provide:
- a relay or masked email address; or
- a link to a contact form.
This allows legitimate communication without necessarily exposing the registrant’s direct email address.
That helps balance:
- privacy;
- legitimate communication.
Can Law Enforcement or Other Requesters Obtain Nonpublic Registration Data?
Potentially, but nonpublic data is not simply released because somebody asks for it.
ICANN operates the Registration Data Request Service for requests involving nonpublic gTLD registration data and participating registrars.
NiceNIC also publishes a formal Request for Disclosure of Nonpublic Registration Data policy.
NiceNIC’s current process requires properly formed requests to be reviewed on their own merits and does not treat a request as an automatic right to disclosure.
Relevant considerations can include:
- requester identity;
- specific data requested;
- legal basis or legitimate interest;
- purpose;
- proportionality;
- rights and freedoms of the data subject;
- applicable law;
- registry and ICANN requirements.
For ccTLDs, disclosure rules can differ because the applicable registry and local legal framework may not follow the same gTLD process.
Does Domain Privacy Replace Accurate Registration Data?
No.
This is one of the most important points in this guide.
Do not enter fake:
- name;
- address;
- phone;
because you believe the public record will be private anyway.
Privacy protects public exposure where permitted.
It does not remove:
- verification requirements;
- registration-data obligations;
- ownership-control responsibilities;
- compliance obligations;
- legal responsibilities.
Does Domain Privacy Prevent Spam and Phishing?
It can reduce one source of publicly harvested contact information.
If a direct email address, phone number, or street address would otherwise be publicly visible, reducing that visibility can reduce some:
- automated scraping;
- unsolicited marketing;
- spam;
- social-engineering opportunities.
But it does not eliminate phishing.
Attackers can still target you through:
- company websites;
- social networks;
- public business directories;
- breached databases;
- guessed email addresses;
- fake registrar messages.
For important domains, combine Domain Privacy with the controls in NiceNIC's domain security checklist.
Does WHOIS Privacy Prevent Domain Hijacking?
No.
Domain hijacking is mainly a control problem, not a public-directory problem.
Protect the registrar account with:
- a unique password;
- Two-Factor Authentication;
- secure recovery email;
- Domain Lock;
- protected Auth/EPP Codes;
- controlled staff access.
Domain Privacy can be one layer of a security strategy, but it is not a substitute for account security.
Does Domain Privacy Affect DNS, Nameservers, Hosting, or Email?
Normally, no.
Domain Privacy concerns registration-data publication.
It does not by itself change:
- nameservers;
- A records;
- AAAA records;
- CNAME records;
- MX records;
- hosting provider;
- website content;
- email routing.
If your website or email stops working after another domain-related change, troubleshoot the actual domain, DNS, or hosting layer rather than assuming Privacy caused the outage.
Does WHOIS Privacy Affect SEO?
Domain Privacy does not make your website invisible to Google or Bing.
Search engines index website content through web crawling. Domain-registration privacy changes registration-data exposure, not the website content served to crawlers.
Enabling privacy does not itself:
- remove the site from Google;
- block normal crawling;
- change DNS;
- change hosting;
- create a ranking bonus.
Do not buy Domain Privacy because somebody promises it will improve rankings.
Use it for its real purpose:
Reducing unnecessary public exposure of registration data where applicable.
Is WHOIS Privacy Required?
No universal rule requires every registrant to use a separate Domain Privacy service.
Whether you should use it depends on:
- what the TLD permits;
- what data would otherwise be public;
- whether policy redaction already applies;
- whether the domain belongs to an individual or organization;
- your privacy and operational requirements.
For many eligible NiceNIC domains, there is little reason to leave the available privacy service unused when it is included without a separate privacy fee.
Is WHOIS Privacy Free?
That depends on the registrar and the TLD.
Some registrars charge separately for privacy.
NiceNIC currently adds free Domain Privacy for eligible TLDs during registration, renewal, transfer, and reactivation.
Use the NiceNIC privacy eligibility page to check the current rule rather than assuming every extension is supported.
Important: "Free Privacy" does not mean every TLD supports Privacy. Registry restrictions still apply.
Which TLDs Do Not Support the Same Privacy Model?
Country-code domains and restricted extensions can follow different rules.
A registry may:
- prohibit a registrar privacy service;
- publish registration data under local rules;
- require local-presence information;
- use a different registration-data access model;
- have different disclosure requirements.
Therefore, never assume that the privacy behavior of .COM applies unchanged to every ccTLD.
Check the exact TLD before registration or transfer.
How to Check Whether Your Domain Privacy Is Working
Use this simple process.
Step 1: Check the domain through RDAP or registration-data lookup
Use:
- NiceNIC Domain Lookup; or
- ICANN Lookup for applicable gTLD data.
Step 2: Look at what is public
Check whether direct personal information such as your:
- name;
- street address;
- phone;
- direct email
is publicly exposed, redacted, or replaced according to the applicable system.
Step 3: Do not treat technical fields as a privacy failure
Seeing:
- registrar;
- nameservers;
- domain status;
- creation date;
- expiration information
does not mean personal Privacy is disabled.
Step 4: Check NiceNIC privacy eligibility
If you expected Privacy but personal data appears publicly, review the NiceNIC Domain Privacy eligibility guide.
If the result still does not match the expected configuration, contact NiceNIC Support.
Why Is My Name Still Visible Even With Domain Privacy?
Possible reasons include:
Always verify against a current authoritative source rather than relying on an old screenshot or third-party data cache.
Why Can My Country or State Still Appear?
Public registration-data rules do not treat every data element in exactly the same way.
Some fields can have different publication or redaction requirements from direct identifiers such as:
- registrant name;
- street;
- phone;
- email.
So:
Privacy does not necessarily mean every geographic or organizational field disappears from every registration-data output.
Look at the exact TLD, applicable policy, and specific field rather than assuming a universal display format.
Does Domain Privacy Hide the Registrar?
No.
Public gTLD registration-data output generally continues to identify the sponsoring registrar.
It can also display:
- Registrar IANA ID;
- registrar URL;
- registrar abuse contact;
- domain status;
- nameservers.
This transparency helps users determine who is responsible for the domain registration without requiring personal registrant contact information to be publicly exposed.
Does Domain Privacy Hide the Expiration Date?
Not necessarily.
Registration dates and status information are part of the technical and registrar-level information commonly available through public registration-data systems.
If your concern is protecting the domain from expiration, use:
- renewal monitoring;
- auto-renew;
- valid payment;
- early renewal.
Privacy is not a lifecycle-management tool.
Does Domain Privacy Protect a Business Domain Differently From a Personal Domain?
The practical value can differ.
Personal registrant
Privacy can be particularly useful when underlying registration information includes:
- home address;
- personal phone;
- personal email.
Business registrant
A business may already publish:
- company address;
- public phone;
- support email.
But that does not mean every registrar-account contact or employee’s personal information should automatically be public.
Businesses should decide deliberately which information is intended to be public.
What About the Registrant Organization Field?
This field deserves special attention.
For business-critical domains, review:
- registrant name;
- organization;
- account owner;
- registrar login;
- internal ownership records.
Do not assume that a public Organization field tells the whole story about who contractually controls the domain.
Keep internal documentation as well.
Domain Privacy vs Domain Security
These are different goals.
For a valuable domain, use Privacy together with the controls in How to Secure a Domain Name.
Common WHOIS Privacy Misunderstandings
"WHOIS privacy means nobody can know who registered the domain."
Incorrect.
It reduces routine public exposure. Underlying registration information can still be retained and may be disclosed under applicable lawful processes.
"WHOIS is still the only registration-data system."
Outdated.
RDAP became the definitive gTLD registration-data source beginning January 28, 2025.
"If my name is redacted, I must be using a paid privacy service."
Not necessarily.
Policy redaction and a separate privacy/proxy service are different concepts.
"Privacy means I can enter fake registration information."
No.
Accurate registration data is still required.
"Privacy hides my nameservers and registrar."
No.
Technical and registrar-level fields can remain public.
"Privacy prevents domain hijacking."
No.
Use 2FA, Domain Lock, Auth Code protection, secure email, and access controls.
"Privacy makes me immune to lawful disclosure."
No.
Properly formed disclosure requests can still be reviewed under applicable policy and law.
"All TLDs support the same privacy service."
No.
Registry and local rules vary.
Who Should Use Domain Privacy?
It is worth considering for:
- individual domain owners;
- freelancers;
- small businesses;
- domain investors;
- agencies managing customer domains;
- portfolio owners;
- anyone who does not need personal registration contact information published publicly.
The decision is especially easy when the TLD supports it and the registrar includes it without a separate privacy fee.
WHOIS / RDAP Privacy Checklist
- Your registration data is accurate.
- Your registrant email is valid and monitored.
- You know whether the TLD supports the privacy service.
- You understand that RDAP is now the modern gTLD registration-data system.
- You checked the public output for the exact domain.
- Your direct personal data is not unexpectedly exposed.
- You understand which technical fields remain public.
- You know that Privacy does not replace 2FA or Domain Lock.
- You know how legitimate third parties can request nonpublic data.
- You know where to contact the registrar if the public result looks wrong.
Frequently Asked Questions
What is WHOIS privacy?
WHOIS privacy, also called Domain Privacy, reduces the public exposure of personal domain-registration data where the applicable TLD and policy support it.
Is WHOIS still used in 2026?
The term is still widely used, but RDAP became the definitive source for modern gTLD registration information beginning January 28, 2025.
What is RDAP?
RDAP is the Registration Data Access Protocol. It provides structured access to domain-registration data and replaced legacy WHOIS as the primary modern gTLD registration-data protocol.
Is Domain Privacy the same as RDAP redaction?
No. Policy redaction and a dedicated privacy/proxy service can both reduce public exposure, but they are technically different mechanisms.
Is WHOIS privacy free at NiceNIC?
NiceNIC currently adds free Domain Privacy for eligible TLDs with registration, renewal, transfer, and reactivation. Registry restrictions apply.
Does NiceNIC provide free privacy for .COM?
NiceNIC currently lists many common gTLDs among the extensions eligible for free Domain Privacy. Check the current eligibility page before ordering.
Can I register a domain anonymously?
Domain Privacy is not anonymous registration. The registrar still collects and maintains required underlying registration information.
Can law enforcement see private WHOIS data?
Nonpublic registration data can potentially be disclosed through applicable lawful processes, but disclosure is not automatic merely because a request is submitted.
Can someone contact me if my domain is private?
Applicable registration-data systems can provide relay email addresses or contact forms so legitimate communication can occur without exposing the registrant’s direct email.
Does WHOIS privacy affect SEO?
No direct SEO advantage should be expected. Privacy changes public registration-data exposure, not website content or normal search-engine crawling.
Does WHOIS privacy affect email?
No. Domain Privacy does not normally change MX records, mailboxes, or email routing.
Does WHOIS privacy affect DNS?
No. It does not normally change nameservers or DNS records.
Does WHOIS privacy prevent domain transfers?
Privacy itself should not be treated as a universal transfer block. Transfer eligibility depends on domain status, TLD rules, registrar lock, Auth Code, and other transfer requirements.
Why can I still see my registrar and nameservers?
Because Domain Privacy is intended to reduce exposure of personal registration data, not remove technical information about the domain.
Why is my information still visible?
Check TLD eligibility, current authoritative RDAP output, whether privacy is active, and whether the visible information is technical rather than personal contact data.
Do all ccTLDs support WHOIS privacy?
No. Country-code registries can use their own publication, privacy, disclosure, and eligibility rules.
The Most Important Rule About Domain Privacy
Do not ask only:
"Is WHOIS privacy turned on?"
Ask:
What data is publicly visible, what data is held privately by the registrar, what does the TLD permit, and what can still be disclosed through legitimate processes?
That question reflects how domain-registration privacy actually works today.
Check and Protect Your Domain Registration Data
- Review NiceNIC Domain Privacy
- Check which TLDs are eligible for free Domain Privacy
- Check a domain's public registration data
- Search and register a domain
- Compare current domain prices
- Review the NiceNIC domain-security checklist
- Read NiceNIC's nonpublic registration-data disclosure process
- Visit the NiceNIC Trust Center
Primary Sources and Further Reading
- ICANN — Launching RDAP; Sunsetting WHOIS
- ICANN — Registration Data Policy
- ICANN — Information for RDAP Users
- ICANN — Registration Data Lookup
- ICANN — Registration Data Request Service
- NiceNIC — Domain Privacy Service
- NiceNIC — Free Domain Privacy Eligibility
- NiceNIC — Domain Privacy FAQ
- NiceNIC — Request for Disclosure of Nonpublic Registration Data
- NiceNIC — Domain Name Registration Service Agreement
