I am sorry you had that experience. Normally, if evidence is provided by the complainant that the whois is incorrect, most registrars will require that the registrant provides evidence that the updated data is correct, if only to avoid a follow-on complaint. If evidence suggests that the address is obviously and intentionally fake and the domain likely used in abuse, we may not even wait for the feedback of the customer before deactivating.
Best,
Volker
>>[SAH] Actually, there *are* requirements to provide valid data and for registrars to perform validation processing:
How do you expect toothless policy to work *on the Internet*? Seriously?
worst that can happen when you put in fake whois data is that your domain gets reported, you change "123 fake st" to "124 fake st", and your registrar is satisfied because what more can they possibly do. I know this because I went through this with an old sinkhole domain. It's a total joke. Let's not pretend it's anything more than that.
On Tue, Feb 14, 2017 at 1:31 PM, Hollenbeck, Scott <shollenbeck@verisign.com> wrote:
From: gnso-rds-pdp-wg-bounces@icann.
org [mailto:gnso-rds-pdp-wg-bounces@icann.org ] On Behalf Of allison nixon
Sent: Tuesday, February 14, 2017 1:21 PM
To: Volker Greimann <vgreimann@key-systems.net>
Cc: RDS PDP WG <gnso-rds-pdp-wg@icann.org>
Subject: [EXTERNAL] Re: [gnso-rds-pdp-wg] Dangers of public whois
>>to your first point: the right to privacy of ones own data may be different where I live and where you live. Suffice it to say that in our day-to-day business we get eough complaints from customers who feel their rivacy has been violated either by our putting their data out for everyone to see or by customers of ours who provide services that do the same. And we both agree that whois privacy will not protect you 100%.
So put your contact address as "123 fake st" and your phone number as "555-555-5555". Make a fake email. No one is forcing you to disclose more than you want to. And the only people who disclose too much are doing so by mistake, not by coercion.
[SAH] Actually, there *are* requirements to provide valid data and for registrars to perform validation processing:
https://www.icann.org/
resources/pages/approved-with- specs-2013-09-17-en#whois- accuracy
Scott
--
_________________________________
Note to self: Pillage BEFORE burning.
-- Bei weiteren Fragen stehen wir Ihnen gerne zur Verfügung. Mit freundlichen Grüßen, Volker A. Greimann - Rechtsabteilung - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Folgen Sie uns bei Twitter oder werden Sie unser Fan bei Facebook: www.facebook.com/KeySystems www.twitter.com/key_systems Geschäftsführer: Alexander Siffrin Handelsregister Nr.: HR B 18835 - Saarbruecken Umsatzsteuer ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu Der Inhalt dieser Nachricht ist vertraulich und nur für den angegebenen Empfänger bestimmt. Jede Form der Kenntnisgabe, Veröffentlichung oder Weitergabe an Dritte durch den Empfänger ist unzulässig. Sollte diese Nachricht nicht für Sie bestimmt sein, so bitten wir Sie, sich mit uns per E-Mail oder telefonisch in Verbindung zu setzen. -------------------------------------------- Should you have any further questions, please do not hesitate to contact us. Best regards, Volker A. Greimann - legal department - Key-Systems GmbH Im Oberen Werk 1 66386 St. Ingbert Tel.: +49 (0) 6894 - 9396 901 Fax.: +49 (0) 6894 - 9396 851 Email: vgreimann@key-systems.net Web: www.key-systems.net / www.RRPproxy.net www.domaindiscount24.com / www.BrandShelter.com Follow us on Twitter or join our fan community on Facebook and stay updated: www.facebook.com/KeySystems www.twitter.com/key_systems CEO: Alexander Siffrin Registration No.: HR B 18835 - Saarbruecken V.A.T. ID.: DE211006534 Member of the KEYDRIVE GROUP www.keydrive.lu This e-mail and its attachments is intended only for the person to whom it is addressed. Furthermore it is not permitted to publish any content of this email. You must not use, disclose, copy, print or rely on this e-mail. If an addressing or transmission error has misdirected this e-mail, kindly notify the author by replying to this e-mail or contacting us by telephone.