When you register a domain, your name, email, phone number, and address are published in the public WHOIS database. Anyone can request this data — spammers actively use it for mailing lists. WHOIS Privacy replaces your data with the privacy service's data.
What WHOIS Shows Without Protection
Domain Name: EXAMPLE.COM
Registrant Name: Ivan Ivanov
Registrant Email: ivan@example.com
Registrant Phone: +380501234567
Registrant Address: Kyiv, UkraineWhat WHOIS Shows With Privacy
Domain Name: EXAMPLE.COM
Registrant Name: Privacy Protected
Registrant Email: privacy@whois.zevshost.net
Registrant Phone: +1 (555) 000-0000
Registrant Address: Privacy ServiceWhy Enable WHOIS Privacy
- 🛡 Spam protection — your email doesn't end up in spammer databases
- 🔒 Personal data protection under GDPR
- 🚫 Protection from social engineering and phishing
- 🌐 Anonymity when registering competitor domains
Enabling Privacy at ZevsHost
When registering a domain, check the box for "Enable WHOIS Privacy." For an existing domain: Billing → Domains → select the domain → "WHOIS Privacy" → "Enable."
WHOIS Privacy Limitations
| Zone | Privacy Available |
|---|---|
| .com, .net, .org, .info | ✅ Yes |
| .ua, .com.ua | ❌ No (regulator requirement) |
| .eu | ✅ Partial |
| .gov, .edu | ❌ No |
Common Messages and Rejections When Enabling Privacy
| Message or Situation | What It Means | What to Do |
|---|---|---|
| "WHOIS Privacy is not available for this TLD" | The zone's registry (for example .ua, .de, .fr) requires publishing real registrant data under local regulations | Use an intermediary legal entity or register an adjacent zone (.com, .net) for the public-facing profile |
| Registrant Organization shows "Redacted for Privacy" | This is the standard GDPR redaction for individuals in the EEA, applied automatically by ICANN-accredited registrars — it is not the paid Privacy service | Full organizational anonymity still requires the separate WHOIS Privacy Protection service |
| The "Verify your WHOIS contact information" email gets ignored by the system | ICANN requires yearly registrant email verification (2013 RAA); the Privacy service receives this email instead of you and confirms it automatically | Make sure the Privacy service is active on the email address the registrar actually checks |
The domain suddenly shows a clientHold status after a Privacy change | Some registrars temporarily lock a domain to verify ownership when Privacy is enabled or disabled | Wait 24–48 hours and avoid changing NS servers during this period |
Verifying That Privacy Is Actually Enabled
# Check via whois from the console
whois example.com | grep -i registrant
# Expected result when protection is enabled:
Registrant Name: Privacy Protected
Registrant Organization: Privacy Service
Registrant Email: privacy@whois.zevshost.net- If the output still shows a real name, phone number, or personal email, Privacy is not active — check the status in the registrar panel
- For some registries (.io, .co), the public WHOIS sometimes updates with up to a 24-hour delay after enabling Privacy
- The RDAP protocol (
rdap.org) shows the same data as structured JSON — useful for automated checks
When WHOIS Privacy Will Not Protect You
- A court order or subpoena to the registrar — the Privacy service is obligated to disclose real data under a lawful request
- A UDRP domain dispute — the arbitration panel can request the registrant's real data from the registrar to establish good or bad faith
- Zones with mandatory publication (.ua, .de, and some other ccTLDs) — Privacy is either unavailable there or available only for legal entities with restrictions
- A data leak at the payment stage or from the registrar's internal billing system — Privacy hides only the public WHOIS, not the registrar's internal databases
Comparing Privacy Policies Across Popular Registrars
| Registrar | Privacy Cost | Enabled by Default |
|---|---|---|
| ZevsHost | Free for most zones | Yes, at registration |
| Namecheap | Free (WhoisGuard) | Yes, at registration |
| GoDaddy | Paid, a separate add-on | No, must be enabled manually |
| Google Domains (Squarespace Domains) | Free for individuals | Yes, by default for supported zones |
When transferring a domain between registrars, the Privacy setting doesn't carry over automatically — it must be re-enabled at the new registrar right after the transfer completes.
- If Privacy was paid at the old registrar but is free at the new one, the transfer also cuts your domain costs
- Before transferring, make sure the email on file with the Privacy service actually receives mail — the transfer authorization request goes there
Frequently asked questions
If WHOIS Privacy is not available for a zone like .ua, is there another lawful way to hide personal contact details?
There is usually no direct equivalent of Privacy for such a zone, but some owners register the domain through an intermediary entity whose public details are already business contacts rather than personal ones. Another option is keeping the main site on a domain in a different zone where Privacy is available, using the local zone only to satisfy the regulator.
Does enabling Privacy affect delivery of domain renewal notices?
No, renewal and other account emails from the registrar still go to the real email address tied to the account in the control panel; Privacy only replaces what shows up in the public WHOIS database, not the internal contact used to reach the client. Confirm the address in the control panel is current, not just the contact shown in WHOIS.
Is it fine to toggle Privacy on and off repeatedly, or does frequent switching raise flags?
Random toggling does leave a trace: some registrars lock a domain temporarily to verify ownership every time the Privacy state changes, and NS servers are best left untouched during that window. Switching protection on and off repeatedly without good reason raises both the risk of short technical locks and the chance of losing track of which data is currently published.
If a company rather than an individual registers a domain, does Privacy work the same way?
Somewhat differently: the standard GDPR redaction of personal data applies specifically to individuals from a certain region, while an organization's public details often stay visible by default. Hiding a company's own contact details usually requires separately enabling the paid or free Privacy service rather than relying on the automatic redaction that applies to individuals.