Failed Registerfly Renewal Expirations & Redemption.

Notes: the simplest stuff

Some people harbor the expectation that Registerfly will be put out of business by a Revoked RAA situation from ICANN. The actual facts are more likely that they will have to remove the ICANN STAMP, and strictly act as a name affilliate/reseller, as they did when they first started that company. Registerfly could continue operations after March 31st, likley buying domains through TUCOWS or some equivalent that they have a working API for.

ACTION request: The US DEPT of Commerce can step in, along with ICANN, past the simple action of Revoked RAA. Reselling Registrars need to be on-board with this, as it is a watershed event. The urgency is with respect to 2007 expired names and ongoing expirations during this event, over and above the transfer-away issues. Failed Renewals that lead to expirations are not the fault of the domain registrant. Registerfly must not be allowed to continue.

Domains are rights-rented and not owned. Some people actually think when they "buy" a domain , it is theirs, and are stunned after 2 years that they have to re-buy it for $$$ redemption if they find out it is expired. A disconnect occurs when a website owner is not the domain registrant ( webmaster or some one else aquires the domain ) It happens in a substantial number of instances, and the website owner just does not know what happened after the fact. They "buy" from one website to find the registrar is yet another website. The system as it is now is not kind to them.

ACTION: Somehow we need to improve awareness and eliminate the manner in which redemption is applied, especially when it becomes a punishment for a failed renewal by Registerfly.

Alternate access

ICANN needs to maintain access to critial data.

The WhoIs registry needs to have a 'legal owner' section that requires the domain owners contact info and which is visible only to ICANN. This would allow the use of ProtectFly or other data protection services but still allow ICANN to be able to tell who the owner is.

Also, ICANN should be able to issue AuthCodes.

Mark K

Failed Registerfly Renewal Expirations & Redemption.comment

THis is not good. They should be shut down and us transfered out


The situational conduct for Registerfly is not an anomaly, but it is the worst in history. A 15 day arms-length probation by paper notification should perhaps be augmented by an immediate on-site audit and remedial action team instantiation ( empowered registry qualified personnel ), at the expense of the registrar in question. This could be ammended to the RAA as an option for ICANN to flex some rapid response mechanisms. The rules already in place are good, but there was never any intent in the system to handle this issues presented by Registerfly.

For example ICANN stated no "domain shall expire" for this event, as it should & that was not executed fully. Domains Have Expired, Registerfly did not fully comply, customers lost out and websites vanished. Inherent in any free market society is an implicit need for some minimum level of trust for it to function, like driving on the proper side of the road.

It's sort of a reparations issue for many. Who fixes it, and how does that fix get funded ... I suspect that what you desire may be:

A Team to deploy at a de-acredited registrar to see that these problems are abated, and hopefully information gathering is made more direct. Granted it may be janitorial record-keeping repairs but it should happen in the hands of qualified personnel.

By way of allegory.. if a child throws rocks and breaks windows, how do you deal with it? Do you spank the child and leave the windows broken? The effect of unintended consequence can be that the broken windows lead to yet more disaster. The effective response is to detect the problem, to go to the site of the problem with a window repair person, find all the broken windows and force the child and his/her parents to pay for immediate repairs. In this case of Registerfly it is Unified Names INC as the parent, and someone has to revoke & manage the rock-handling status of Registerfly. As part of many agreements there are usually punitive clauses, this would be no exception.


Jeff, you are the most sane person I know. I agree. I think that there should be more regulation and to show which are reseller accounts


The truth is that Registerfly bought the accredation of ICANN by aquiring an accredited registrar, and then extending that to all its services. Very much an end-run around ICANN. ICANN did go to the offices of Registerfly and were rebuffed on Audit Tasks that in fact are already outlined in the RAA.

I do not want to belabor the issue too much but i do think that ICANN should be able to request a strong hand in the matter of Registerfly by request to the White House / US Dept of Commerce for it's ability to intervene for reasons of business practice. It is time for the US.DOC to do just a bit of Parenting for this issue.

IMHO Registerfly's behavior has now elevated the prevailing view to be an International Embarrassment for America... and I know that greater influences should have a problem with that, and in fact they are sharp folks that read this and other logs out on the net.

March 31st should be more than just the dropping of another shoe, it should be Day 1 of redress and reparations to the harmed customers of Registerfly, regardless where they live on our planet. For many people this situation appears to be a certain mis-step without any closure for them.

And of course, i want my domain back from Expirefly.

Registerfly extention

This was the wrong thing. They are just delaying the inevitable. Registerfly needs to have the proceeds sold and distributed amongst the victims. The people who made this happen should pay in the pocket books that owned the registry and enom should pay because it is as guilty as Registerfly in this instance

You know

I think the FEDS need to get involved. This is bigger than what ICANN can handle