Mike Zupke has updated his blog which could come in useful for people wishing to transfer out of Registerfly. I've posted this below as well as a contact email for Mike Zupke. I'm happy he's finally doing what he originally said he couldn't do.
ICANN spoke yesterday with Kevin Medina and Mark Klein of RegisterFly.
ICANN asked for greater clarity from RegisterFly about auth-info codes and draw attention to this link to the registerfly.com auth-info codes retrieval process.
RegisterFly indicated that auth-info codes are being distributed to
customers via RegsiterFly.com and customer service channels and they
claimed that the site is functioning as it should to allow names to be
unlocked. ICANN told RegisterFly it will run a test so we can verify
that these systems are indeed functioning as advised.
RegisterFly said they would have a developer research and correct
the problem registrars and other users are experiencing with port 43
and web-based Whois services. Presently, the RegisterFly Whois server
provides no registrant, administrative contact, technical contact, or
other registrar-level Whois data, but instead reports only
registry-level data. ICANN has told RegisterFly to correct this problem
and report back. The failure by RegisterFly to provide Whois service
effectively prohibits all registrants of .com and .net names from
transferring out, so this needs to be RegisterFly’s highest priority in
order to protect the interests of registrants. This must be corrected
immediately.
Regarding names registered as a reseller for eNom, RegisterFly
confirmed that an exchange of information will take place this Monday,
12 March that will result in access to eNom systems, and enable
“automatic” transfer of eNom names.
ICANN insisted upon daily reports indicating the number of transfers. We intend to publish these.
Finally ICANN said it would be referring and monitoring the
performance of RegisterFly on handling complaints referred to it and to
ICANN about RegisterFly.
It was made clear that it is absolutely imperative that the causes
of complaints regarding transfers and auth-codes have to cease
immediately. If they do not they will be the subject of further breach
notices.
Written by Mike Zupke You can contact Mike Zupke at
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
Please also follow the steps below or your
message may not be timely handled.
If you are continuing to experience
unlocking, auth-code, privacy service/protect-fly, or other whois problems
preventing transfers, please send an email to
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
with
the following details in this format:
1. all domain names affected;
2. your registerfly account name;
3. the email address associated with your
registerfly account;
4. a brief explanation of the specific
problem (in other words, say “I can’t get auth codes from the
control panel,” or “I can’t unlock my domain name in the
control panel,” or “I can’t log into my control panel”
etc.);
5. the date when you last attempted to do
the thing you can’t do.
Before you hit send, please (PLEASE)
double-check to ensure that you’ve included all of the details listed
above. If you don’t include the details above, we will return your email
to you with a request for additional information. This will slow the handling
of your complaint and also unfairly limit the availability of resources for
other registrants.
Please use email address
This e-mail address is being protected from spam bots, you need JavaScript enabled to view it
. You will receive an auto-response / anti-spam
verification email, so be sure you are writing from an email address you still
have access to or we won’t get your message.
Please also note that ICANN cannot force a
registrar to renew a domain name. You may, however, transfer your registration
to another registrar. To transfer your registration, you will need to unlock
the name, populate your whois record with valid email addresses (that you have
access to), and obtain the auth code from Registerfly and provide it to the
"gaining registrar." If you are having trouble with any of these
steps, please follow the instructions above.
I've received emails lately that things are starting to work with the transfers. This is good news for the domains that are still there. Good luck with it and please let us know in the comments how things are working.
|