I have some late breaking and Great news for the customers of Registerfly. Enom has officially announced that they are no longer going to be associated with Registerfly. This is big. This is so big in fact that this has put the Registefly server down due to too much traffic. This is such fantastic news I've literally been dancing around the office and getting ready to light up a fat cigar to celebrate.
Our efforts have not been vain and finally someone has heard our complaints and is acting on it. Enom, we commend you for doing the right thing and for taking a stand against the unethical business practices of Registerfly. Please click below to read more!
Recently I've been in contact with Mike Zupke of ICANN and ICANN is fully aware of what's going on with Registerfly. His response wasn't all that great. His admittance of knowing what's going on and not being able to provide a positive solution automatically allow everyone to be able to name ICANN in a lawsuit and you are welcome to use the below correspondence as evidence of such. It's called: Unjust Enrichment
Below I've provided the emails in chronological order and responses from both the Ombudsman of ICANN and Mike Zupke. The emails will be listed by date. The first email is my original email to the Ombudsman and next will be his response. I've made these public due to the fact that Mr. Zupke conveniently ignored my last email with no response... hence the squeaky wheel. Please read on and comment.
Ok folks, I just got off the Phone with Enom (28 minute wait). I've been given specific instructions on how to get names out of Registerfly that still list the whois as Enom. You must do all of the following and I will update this if anything changes. Please Read More for the instructions. I've also forwarded an email to Enom to make sure of any changes or corrections that have to be made to this. Please make sure you read-on in the bottom right of this article to find out more.
Registerfly - Get your names out! UPDATED!
All related correspondence is highlighted in yellow.
Enom can help. There is one important condition that has to be in place before Enom can help. This is that the whois information must list Enom as the Registrar of record. I use Whois.sc.
Similar to strides independent business owners made during the advent of the telephone, the Internet has changed forever the way business gets done. Apart from the obvious impact the Internet has had on travel, commerce and the like, the ability to set up shop and market a Web presence has afforded even today's smallest businesses the opportunity to vie for a piece of the big guys' pies.
In Part1 of this post I have explained the problem I had faced, when trying to renew one domain registered with RegisterFly. This is the second part of the post and shows a step by step procedure describing the solution that worked for me and allowed me to move away from registerfly and not loose my domain.
1. Why is this happening?
Registerfly is not explaining to their customer what the real problem is. From my own experiences and findings here is what is happening:
RegisterFly used to be an ENOM reseller. All this started when they moved away from Enom and become a standalone registrar.
Earlier this year, anyone renewing their domains on registerfly have seen that instead of the normal instant action this required a two step process. This was actually transferring their domain from Enom to RegisterFly’s own system. This caused some confusion but it was working and myself have renewed a few domains like that without any problems except the longer time to finish and the fact that I had received a transfer request that needed to be approved for the renewal to work.
Starting around the end of October (presumably October 26th), .COM and .NET domains can be only transferred with an AuthCode, as well as .INFO or BIZ domains. This means that you will need the domain authcode in order to make any domain transfer.
I have some late breaking and Great news for the customers of Registerfly. Enom has officially announced that they are no longer going to be associated with Registerfly. This is big. This is so big in fact that this has put the Registefly server down due to too much traffic. This is such fantastic news I've literally been dancing around the office and getting ready to light up a fat cigar to celebrate.
Recently I've been in contact with Mike Zupke of ICANN and ICANN is fully aware of what's going on with Registerfly. His response wasn't all that great. His admittance of knowing what's going on and not being able to provide a positive solution automatically allow everyone to be able to name ICANN in a lawsuit and you are welcome to use the below correspondence as evidence of such. It's called: 
