As we continue to adjust to the new GDPR (General Data Protection Regulation), we’ve updated our “Private Registration” feature. This feature is now active by default and hides your data in Gandi’s public Whois (except for your country, your anonymized email address and your organization name, if applicable.
Beyond that, we will also no longer replace your contact information with Gandi’s contact information and this will no longer be sent to the registry. Your personal information will instead be replaced by the phrase “REDACTED FOR PRIVACY.” In our Whois, all of your data will be hidden, including first and last name, except for country and, organization name when applicable.
If you activated Private domain registration before July 9, 2018, you won’t notice any change. The registry will continue to use this same registration information so long as you don’t update your contact information with Gandi.
If, on the other hand, you would like to display your contact information in the Whois, it is now possible to deactivate Private domain registration from your Gandi account. By deactivating Private domain registration, you consent to have your contact information published in the public Whois database. You may rescind this consent at any moment by reactivating the Private registration option.
To manage these settings for your domains, go to the Control panel in your account, then to Domains, then to your domain, and click on the “Contacts” tab.
—
Please note that Private domain registration does not apply to the TLDs listed below, where your contact information is protected directly by the registry. In this case, Gandi publishes the whois entry as listed by the registry. For these TLDs, then, you’ll need to contact our Customer Care team in order to show your contact information in the whois:
.se, .nu, .uk, .eu, .be, .fr, .re, .pm, .tf, .wf, .yt, .at, .ie, .pt, .pl, .vg, .gd, .nz, .no, .lv, .ro, .ru, .af, .cx, .gs, .gy, .ht, .hn, .ki, .kn, .sb, .tl, .kn, .ms, .nf, .lt, .de, .at, .sk, .la, .pw, .fm, .radio.fm, .radio.am, eu.com, uk.com, gb.net, uk.net, cn.com, jpn.com, sa.com, us.com, br.com, ru.com, za.com, de.com, se.net, ae.org, gr.com, us.org, com.de, jp.net, hu.net, in.net, co.com
Tagged in corporateDomain names
Gandi’s Private Domain Registration contains 2 parts: the “Hidden WHOIS Data” (aka. “protected Whois” in the GDPR email sent out to users, aka. WHOIS obfuscation) and the the “Anonymized Email Address” (aka. “Anti-spam” on the domain registration page, aka. “Email address hidden” on the account information page). For more informations about these see the related docs at https://docs.gandi.net/en/domain_names/common_operations/whois_privacy.html and https://v4.gandi.net/static/contracts/en/whois/pdf/ObfuscatedWhois_Intl_1.1.pdf or the old wiki page at https://web.archive.org/web/20171218151544/https://wiki.gandi.net/en/domains/private-registration .
This blog post and the new doc page left out, but only certain extensions are compatible with this feature: https://wiki.gandi.net/en/domains/private-registration/gandi-provided For example the .in and .us TLDs still don’t support any domain privacy. (correct me if I’m wrong)
Gandi’s “Private Domain Registration” feature differs from the very popular and similarly named domain proxy services (usually referred as “private registration”, “domain privacy”, “WHOIS protection”) where someone else registers the domain for you, and then just lends it for usage.
Examples:
– at Register.com it is called “Private Domain Registration” https://www.register.com/masking/index.rcmx
– at GoDaddy it is called “Domain Privacy / Privacy Protection” https://www.godaddy.com/domainaddon/private-registration.aspx
– at Domain.com it is called “Domain Privacy” https://www.domain.com/domains/whoisprivacy
– at Network Solutions it is called “Private Registration” https://www.networksolutions.com/domain-name-registration/private.jsp
Gandi DOES NOT provide a domain proxy service; this is why there are some data which you can’t set private.
Sidenote: most certificate authorities (even Let’s Encrypt) require you to be the owner (the legitimate registrant) of the domain to issue an SSL/TLS certificate for it, therefore they don’t support domain proxy services.
Gandi’s Private Domain Registration contains 2 parts: the “Hidden WHOIS Data” (aka. “protected Whois” in the GDPR email sent out to users, aka. WHOIS obfuscation) and the the “Anonymized Email Address” (aka. “Anti-spam” on the domain registration page, aka. “Email address hidden” on the account information page). For more informations about these see the related docs at https://docs.gandi.net/en/domain_names/common_operations/whois_privacy.html and https://v4.gandi.net/static/contracts/en/whois/pdf/ObfuscatedWhois_Intl_1.1.pdf or the old wiki page at https://web.archive.org/web/20171218151544/https://wiki.gandi.net/en/domains/private-registration .
This blog post and the new doc page left out, but only certain extensions are compatible with this feature: https://wiki.gandi.net/en/domains/private-registration/gandi-provided For example the .in and .us TLDs still don’t support any domain privacy. (correct me if I’m wrong)
Gandi’s “Private Domain Registration” feature differs from the very popular and similarly named domain proxy services (usually referred as “private registration”, “domain privacy”, “WHOIS protection”) where someone else registers the domain for you, and then just lends it for usage.
Examples:
– at Register.com it is called “Private Domain Registration” https://www.register.com/masking/index.rcmx
– at GoDaddy it is called “Domain Privacy / Privacy Protection” https://www.godaddy.com/domainaddon/private-registration.aspx
– at Domain.com it is called “Domain Privacy” https://www.domain.com/domains/whoisprivacy
– at Network Solutions it is called “Private Registration” https://www.networksolutions.com/domain-name-registration/private.jsp
Gandi DOES NOT provide a domain proxy service; this is why there are some data which you can’t set private.
Sidenote: most certificate authorities (even Let’s Encrypt) require you to be the owner (the legitimate registrant) of the domain to issue an SSL/TLS certificate for it, therefore they don’t support domain proxy services.
Comments are closed.