RegisterFly, Class Action, ICANN and Registries
I got notice yesterday evening of a class action brought to in a US Court against RF, eNom and ICANN.
Although I can understand why the plaintiff is naming eNom and ICANN ( though i don't think that she will succeed in demonstrating that there were illegal conduct from both ) it is somewhat baffling why some other registrars and registries are left alone from this action.
On the process of trying to solve the problem ICANN stated that it had come to an agreement with the registries (all? some of them?) so domains would not be lost.
But what was the registries' approach to this agreement?
I would assume that the best option would have been to mark all RF-registered domains with a REGISTRY-LOCK status, thus preventing RF to modify the domains and to prevent the domains from expiring.
Has this been done this way? Well, apparently no. The option was more in the line of making affeceted domains something like "Server Deletion Prohibited". This only kept domains from deleting, not from expiring. For those registrants who depended on their domains remaining active this amounts to little more than nothing.
- repb's blog
- Login or register to post comments

Comments
After ICANN's recent response
to a request to investigate a registrar who has forged their own whois contact info...
I think I can well imagine just why ICANN was named in the class action.
If I don't start getting some answers soon myself, I think I'll be joining them.
Registerfly Class action lawsuit
Yes, I think we are due compensation for having to move domains to other registrars as well as for emotional anguish. This will put some of us in dire financial consequences because having to move them to other registrars. We should have the transfer fees waved. Also, to have the same level of privacy adds another layer of costs