Closed maverick85 closed 2 years ago
Hello @maverick85 ,
Thank you for sharing your concerns.
In short, Openprovider is a Netherlands-based registrar, and must comply with GDPR regulations. As such, the Openprovider WHOIS system operates within the parameters of ICANN's interim specifications issued for companies handling personal data of citizens of EU member states.
If you would like, our Domains and DNS product manager can contact you to continue this conversation.
Dear @wmetge, Thank you for your reply. I already had one of such conversations once with one of your reps via ticket.
We have domains registered under company names, whose owners want the WHOIS data to be public. We have domains registered under individual names, where the user MAY opt for anonymity if he so pleases. GDPR policies are fine, but don't come saying you're complying with the parameters of ICANN's specs because that's simply a blatant lie. You are operating in the manner you (OP) sees fit and you have no interest in changing this to a better service. You don't even dignify to offer whois protection with .io domains for example, which is perfectly supported, so users get a choice.
That is why while using other operators, that are also GDPR compliant and here, we get one thing, and with OP we get another.
Our company name is omitted from our own domain. This is simply brutal. Your replies and others alike state one thing clearly: for OpenProvider, you're doing what's right and no effort will be done to fix it.
That's why we've engaged in conversations with other customer's of OP and why we're and others are actively looking for the next best opportunity to move from OpenProvider.
P.S. I also enjoyed the way how you closed this issue quickly to get it out of the way. Shame on you.
Describe the bug
We're quite unsatisfied by the way OpenProvider provides the domain information that is then returned on the
whois
consult. We believe OpenProvider is doing this deliberately, on a market strategy for marketing the OpenProvider brand, instead of being a true white-label operator as they advertise.To Reproduce
For the example I'll perform an
whois
consult on an .io domain registered at NameCheap, and another at OpenProvider. NameCheap, for example, also provides an option for Identity Privacy on .io domains, whilst OP does not.NameCheap example:
So as all can see, a name registered via NameCheap has the registrar info - NC, but also the correct information to the Registrant, the Admin contact and the Tech contact.
Now lets take a look into a domain registered with OpenProvider:
Registrar information: OP ... all OK Registrant information: NONE
Does OpenProvider have a privacy option for .IO domains? NO
Unlike other operators, OpenProvider does not allow Privacy to be ON or OFF in .IO domains. It simply enforces this privacy, and the only information that appears associated to a given domain is that of OpenProvider.
This is something that happens with many, many TLD's. The information displayed is truncated, inefficient, and most times only the information for OpenProvider is displayed. OpenProvider HIDES the registrant information. We feel this is a brutal practice that should be corrected for a better service.
Expected behavior
Domain information to be passed correctly.
Screenshots
N/A
Server info:
N/A
Additional context
N/A