FAQs for RegisterFly customers

by Mike Zupke on April 3, 2007

UPDATE: ICANN has announced the bulk transfer of gTLD names from RegisterFly to Go Daddy. Please see the announcement at http://www.icann.org/announcements/announcement-29may07.htm for more information.

Archived FAQs

Over the last several weeks, ICANN has fielded thousands of inquiries from Registerfly customers by email and telephone. We have put together a list of 14 FAQs below as an attempt to answer some of the questions we’ve heard most.

If you have additional suggestions for other Registerfly customers or questions that might apply to others, please leave them as comments below.

日本語 (in Japanese, courtesy of Motohisa Ohno)

Q. How do I transfer my name(s) out of Registerfly?

A. First, you need to select a new gaining registrar. You can find a list of accredited regsitrars at http://www.internic.net (click “Registrars”). When selecting a registrar, consider all relevant factors, not just price. Find out what others say about them and investigate their customer service options and response times. Your new registrar will help you with the transfer process. If they can’t or won’t, find a different registrar.

Next, you need to unlock your domain name, ensure the Whois data for the name is accurate, and get the auth code from Registerfly. Theoretically, you should be able to do all of this within your Registerfly control panel. If not, see the Qs below.

Then, request the transfer from your new registrar. Your new registrar will confirm your identity by asking for the auth code and sending you a “Form of Authorization” (FOA). The FOA usually gets emailed to the administrative contact email address on file for the domain name; this is why it’s important that your Whois data be accurate. You will need to affirmatively respond to the FOA, either by clicking a link or submitting some information (like a random code) from the FOA letter back to the registrar.

You will need to repeat the process for each domain name. After you have acknowledged the FOA and provided the gaining registrar with the correct auth code, the registrar will notify the registry to process the transfer. The registry will notify Registerfly and wait five days (see Q below) and then process the transfer.

Q. How can I get auth codes from Registerfly? They don’t seem to answer their telephones. UPDATED

A. We’ve heard from numerous Registerfly customers that Registerfly’s support tickets go unanswered and that it is impossible or next to impossible to get them on the telephone. Some people, however, have had some success using the steps below:

The first place you should go to get auth codes is your control panel. The process at Registerfly isn’t exactly logical, so you can find instructions for obtaining auth codes from Registerfly here.

If your control panel shows no auth codes or shows “RRP” or doesn’t allow you to log in or doesn’t show all of your domain names, you will need to contact Registerfly. Several customers have reported successfully getting auth codes by submitting a support ticket with the appropriate subject (requesting an auth code). Registerfly has also indicated that this is the best way to get auth codes. The average turn-around time is 1-3 days. If you are unable to submit a support ticket, write to compliance@registerfly.com. In your email, include the following:

1. all domain names affected;

2. your registerfly account name;

3. the email address associated with your registerfly account; and

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.).

ICANN has forwarded hundreds or even thousands of emails to this address on behalf of Registerfly customers, and some of them are being answered. We continue to receive many complaints from customers that Registerfly does not respond, but there is evidence that at least some people are getting assistance from Rfly.

If you don’t get a response from compliance@registerfly.com, be persistent. But please also be reasonable. First, check your spam folder to ensure you haven’t already received a response. We’ve heard from several people that email from @registerfly.com gets caught in their spam filters. If you don’t get a response in two business days, try again. Although you may be frustrated, please keep in mind that Registerfly is receiving hundreds of emails at this address and there are, perhaps, three people answering them. So this is why we ask you to wait at least two business days.

After allowing two business days, try emailing again. Start your message with “This is the X (a number) time I’ve tried contacting you.” And then paste the rest of your original message in. Give them two business days, and if you still don’t have your auth codes, try again.

Q. What about unlocking names or changing Whois data?

A. The process is essentially the same as above. Write to compliance@registerfly.com. In your email, include the following:

1. all domain names affected;

2. your registerfly account name;

3. the email address associated with your registerfly account; and

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.).

If you don’t get a response from compliance@registerfly.com, be persistent. But please also be reasonable. First, check your spam folder to ensure you haven’t already received a response. We’ve heard from several people that email from @registerfly.com gets caught in their spam filters. If you don’t get a response in two business days, try again. Although you may be frustrated, please keep in mind that Registerfly is receiving hundreds of emails at this address and there are, perhaps, three people answering them. So this is why we ask you to wait at least two business days.

After allowing two business days, try emailing again. Start your message with “This is the X (a number) time I’ve tried contacting you.” And then paste the rest of your original message in. Give them two business days, and if you still don’t have your issue resolved, try again.

Q. After doing everything necessary, why does the “gaining registrar” say that the transfer is pending approval by Registerfly?

A. After a transfer is initiated (with correct auth codes), the registry notifies the “losing registrar” that it is going to transfer the name in 5 days. The losing registrar then has the ability to deny the transfer or affirmatively acknowledge it. It can only deny the transfer for one of the 9 reasons listed in the Inter-Registrar Transfer Policy. If Registerfly does nothing in those 5 days, the transfer will be processed automatically by the registry.

The point of the 5 day window is to allow a losing registrar to ensure that the transfer was legitimately requested. Many registrars do this by sending an email to the customer saying something like “We received a transfer request. If this is unauthorized, click here.” In the emails we’ve seen from Registerfly, it gives you the option to deny a transfer or approve it. If you approve the transfer, it will be processed almost immediately. If you deny it, the transfer is canceled. If you do nothing, the transfer will process automatically in about five days.

Q. If ICANN terminated Registerfly’s accreditation agreement on 31 March, why do they still claim to be accredited?

A. Registerfly decided to file an arbitration action to stall the termination. For better or worse, this is their right under the accreditation agreement. The accreditation agreement is a contract that ICANN has to follow. If we didn’t follow the agreement, Registerfly could potentially continue operations as an accredited registrar indefinitely. So please be patient and understand that we are doing everything we legally can to protect registrants without jeopardizing our right to terminate Registerfly’ accreditation.

Q. What will happen when Registerfly’s accreditation is finally terminated?

A. There are a number of paths we could pursue, and to some extent, the one we follow will depend on the behavior of Registerfly. In the ‘big picture’ the process looks like this: (1) Registerfly loses its access to the registries; (2) a competent and qualified accredited registrar is selected by ICANN to receive a ‘bulk transfer’ of names (and underlying data) from Registerfly to it; (3) former Registerfly customers will be able to contact the new registrar to manage or transfer their names.

Q. How does the bulk transfer work? UPDATED

A. ICANN has the power to approve a bulk transfer from one registrar to another. We will not do so unless the transfer is in the community interest. We have told Kevin Medina he should name a “gaining registrar” now and stop hurting his customers, but he has not done so. If Kevin does name a gaining registrar, we will only approve the transfer if it is in the community interest.

In a bulk transfer, there is no fee to the customer. However, a bulk transfer is different from a normal transfer in that it does not add a year to the registration.

Some people have observed that there are names in their Registerfly control panels that are no longer registered at Registerfly. In the event of a bulk transfer, the registries will move the names that are actually at Registerfly to another registrar. It makes no difference whether Registerfly thinks it has the name or not.

Q. Why doesn’t ICANN bulk transfer the names now?

A. Like it or not, Registerfly is still technically accredited, pending the outcome of our lawsuit against them or their arbitration action. Because Registerfly is accredited, we cannot initiate a bulk transfer. When Registerfly’s termination is final, we will bulk transfer the names, either to a registrar suggested by Kevin Medina or one chosen by ICANN.

Q. What is the status of names that were deleted by Registerfly that are currently in RGP (redemption grace period) or PendingDelete?

A. The registries have agreed not to “drop” names that are deleted by Registerfly. In other words, the names will not be permanently deleted. Today, Registerfly could technically allow its customers to redeem names in RGP, but given its history of not being able to fund the registries, it doesn’t seem like that’s going to happen. (There has to be money in Registerfly’s registry accounts in order to process transactions.)

Since Registerfly has failed in its obligations to its customers, we are continuing our discussions with the registries and others to ensure that customers will be able to regain control of their domain names. Unfortunately, unless Registerfly begins funding its registry accounts in earnest, we may not be able to make that happen until their accreditation agreement is finally terminated.

Q. What if my name was deleted before the registries began prohibiting deletions by Registerfly?

A. If the name is available for registration, by all means, register it.
If the name was registered by someone else, you have at least four options:
1. Work out an agreement with the current registrant.

2. Wait and see if the current registrant lets it expire.

3. File a lawsuit in court against the current registrant.

4. For cases involving “abusive registrations” (this is a narrow category, so you should proceed with caution), begin an administrative proceeding under the Uniform Domain-Name Dispute-Resolution Policy. For more details on this option, see http://www.icann.org/udrp/udrp.htm.

If you decide to file a complaint under the UDRP, you’ll need to do so via one of ICANN’s three approved domain-name dispute-resolution service providers:

* Asian Domain Name Dispute Resolution Centre [ADNDRC]
* The National Arbitration Forum [NAF]
* World Intellectual Property Organization [WIPO]

(Please note that the answer above applies only to domain names in .com, .net, .org, or other generic Top Level Domains operated under contract with ICANN such as .biz, .info or .name. Dispute resolution policies vary in other TLDs such as .gov, .edu, or .us and the 240+ other country code Top Level Domains. Please note also that ICANN generally recommends seeking legal advice before deciding which of the above alternatives is best in any particular situation.)

Q. What can I do about names that were registered through Registerfly at eNom?

A. If you have names registered at eNom, you should contact them for assistance. eNom’s email address is customersupport@enom.com. eNom has some, but apparently not all, of the underlying customer data for Registerfly names that have privacy protection protect-fly enabled. eNom may be able to help you with renewing a name with them or transferring to another registrar. If eNom is unable to help you (because the privacy service is enabled and they don’t have the underlying customer data), you should contact Registerfly as detailed above.

Q. How do I know if my name is at eNom or Registerfly?

A. To determine the name of the registrar of record for your domain name(s), perform a Whois search on the name at InterNIC. The results of the search will provide you with the name and web address of the registrar of record for the name(s).

Q. Can ICANN help me get a refund from Registerfly for services not received?

A. The short answer is ‘no.’ ICANN is not a regulatory agency or governmental body. We are required to work within the framework of a contract (the Registrar Accreditation Agreement) and that contract does not give us the power to order Registerfly to issue refunds.

If you feel that Registerfly owes you money, you might try taking that up directly with them. Alternatively, you might retain an attorney to assist you in collecting the money owed.

Q. I continue to receive renewal notices from Registerfly. Should I pay for renewal?

A. You can make this decision for yourself, but before you pay Registerfly for anything, look at their track record…

For what it’s worth, I tried to register a .com name with Registerfly a few weeks ago as a test. The registration failed, but that didn’t stop Registerfly from taking my $9.95 and asking me to try the transaction again a couple weeks later.


Micky J 04.03.07 at 7:21 am

Dear Icann,
I’m telling you for the 1000th time. There is a glitch in RF system for about 1 month and all people that have the “secure range ip” function enabled can’t login to their accounts! We will loose our domain names because we can’t access the control panel.
There must be thousands of clients in this situation. Please take measures, I’m not able to login for weeks… and I’m not the only one in this desperate situation. Keep in mind: “secure range ip” problem must be solved as soon as possible. Thank you…

Geniese James 04.03.07 at 7:49 am

Thanks for posting such useful information. I know you are doing all you can with such a horrible situation.

Andy 04.03.07 at 9:01 am

Thanks for this information. What will happen to domain names set to expire in the next few weeks? Will they also be retained and continue to function normally until this entire issue is resolved?

Thanks for all you’re doing!

Andy Melichar 04.03.07 at 9:05 am

Please, ICANN… what is happening with expiring domain names? I have been told by RegisterFly that they were unable to renew my domain name. This weekend my domain went into pendingDelete status. I was under the impression that this would not be allowed to happen? I have contacted Paul Levins and Kieren several times, I have contacted RegisterFly, and I have received no response from anyone. Will my domain be one of the thousands that are lost because of the lack of follow through by ICANN?

Mike Zupke 04.03.07 at 10:10 am

We have heard a few complaints about the SecureRangeIP feature. This is obviously not an ICANN-created feature, so I can only speak to what we’ve heard from users and Registerfly. If you enabled SecureRangeIP in your account, Registerfly restricted your access to the account so you could only make changes via a specifc IP address or range of IP addresses. The practical effect is that, if you no longer use the same IP address, you are locked out of your account.

To resolve your particular problem, contact compliance@registerfly.com and ask them to disable the SecureRangeIP feature on your account. (When you write, be sure to provide your name, email address on file, control panel/user id, and domain names, so they can assist you.) I will also ask them to look into determining whether there is a larger problem with this feature that can be fixed quickly.

Mike Zupke 04.03.07 at 10:16 am

Most names that expire (and are not transferred out) will go into auto-renew grace for a period of up to 45 days and then RGP (redemption grace period). During auto-renew grace, names continue to resolve and function. In RGP, names do not resolve, so any website or email accounts that are associated with the name will not function properly. After the 30 day RGP period, expired names go into PendingDelete. Normally PendingDelete lasts 5 days, but the registries have extended that indefinitely to allow Registerfly customers an opportunity to regain control of their names after Registerfly’s accreditation is terminated.
From what we can tell, at least one registry (PIR – .org) prevents deletion a little differently. PIR keeps names active, even after expiration, so those names should continue to function, even post expiration.

Mike Zupke 04.03.07 at 10:18 am

If your name is registered with Registerfly as registrar (as opposed to eNom), it will stay in PendingDelete. The registries have assured us that names will not be permanently deleted due to Registerfly’s failure to fund its registry accounts.

Mike Zupke 04.03.07 at 10:19 am

One more detail:
Names in auto-renew grace can still be transferred out. Names in RGP or PendingDelete cannot.

Jeremy 04.03.07 at 11:34 am

It is nice to know that our domains are supposedly safe from delete… However, how long is ICANN going to allow domains to sit in the “RedemptionPeriod” at RF before the registrant can have the oppurtunity to move it out ? RF expired one of my domains a full TWO YEARS early and now its stuck in the “redemptionperiod”. So, how long does it sit like that before something is done ? How long before I’m allowed to take it out since it doesn’t belong there in the first place ?

Micky J 04.03.07 at 12:05 pm

No,no,no. You haven’t understand. You are not able to login even if you login from the same secure IP range. That’s the difference.

Andy 04.03.07 at 12:05 pm

Thanks for the replies on this.

I have 4 domains that are still locked out. RegFly gave me the auth codes for them, but the whois information is still pointing to RegFly. I can’t change the whois information, so the requests for transfer are going into never-never land.

Strangely, a whois on the domains shows the following status on all of them:

Status: clientDeleteProhibited
Status: clientTransferProhibited
Status: clientUpdateProhibited

I was informed that this means a transfer has already been initiated, though over 2 weeks ago when I tried to renew (before knowing about this mess), I got a message that the domain’s status didn’t allow for transfer… I remember hearing that RegFly was going to be transferring all the domains they had re-sold to themselves (rather than Enom, for example), so I’m wondering if they had transferred these domains to themselves within the past month or so… otherwise, why would these domains have that status? Is there anything else that can be done to extract these domains? I’m guessing there are many others in a very similar situation, so I’m hoping this will be useful information for many folks…

Mike Zupke 04.03.07 at 12:10 pm

The names are locked (not pending transfer). Accordingly, you will need to have Registerfly update your Whois data and unlock the names. If you can’t do that from the control panel, you’ll need to email compliance@registerfly.com.

Mike Zupke 04.03.07 at 12:11 pm

Got it, and I have already asked them to look into this. In the mean time, you should still contact them and ask them to disable the securerangeip service for your account.

Mike Zupke 04.03.07 at 12:15 pm

I know this is frustrating. Please understand there are a lot of contingencies beyond our control: E.g. whether Kevin Medina cooperates, the speed and outcome of the lawsuit we filed, the timing of the arbitration hearing, etc.

So I’m sorry there isn’t a precise answer. If Registerfly does the right thing, we’d be talking about days. If the stall tactics continue, longer.

Jeremy 04.03.07 at 12:25 pm

Understandable answer, however, because of Kevin Medina’s past behaviour, there should be no expectation on the part of ICANN that he will cooperate.

This situation is raising serious questions about the stability of the current system. When there is no ability to enforce the terms of domain registrations because the oversight is basically nonexistent, we as registrants are rightly going to be worried.

Perhaps it is time that the DoC is called in on this since clearly this is a case of a US company going off into left field…

Will 04.03.07 at 12:32 pm

In the situation where a bulk transfer is the course of action, what would happen if RegisterFly refused or was unable to supply accurate registrant data.

Let’s say I have a domain with RegisterFly to which I can no longer influence. Let’s also say that the public WHOIS data is either ‘protected’ or otherwise not what it should be (i.e. my details). If RegisterFly is unable or unwilling to provide accurate information about the registrant, what will happen to my domain?


Mike Zupke 04.03.07 at 12:47 pm

We’re suing Registerfly to get the necessary data. If that fails, or if the data is somehow unusable, we will do what we can to recreate as much of it as possible. Given the pending litigation, that’s probably about all I can say at the moment. I will post more when there is news on our restraining order request.

Will 04.03.07 at 1:03 pm

Thanks for your reply, Mike.

“… we will do what we can to recreate as much of it as possible…”

It concerns me that you don’t sound particularly confident.

On a more general note, does ICANN get involved with registrant data at any point during the normal lifetime of a domain registration i.e. does ICANN capture/store any registrant data?

Mike Zupke 04.03.07 at 1:12 pm

I wish we could be more confident about the data. There is potential for real harm here and that’s why we’re in court.
Unfortunately, the Registerfly situation demonstrates pretty clearly one of the risks of using a whois privacy service that many people are apparently unaware of. ICANN is proposing that changes be made to make whois privacy services more safe, but ultimately, for there to be a change in policy, it must be made through a bottom-up community-based policy development process. We will, of course, continue to work with the various constituencies and policy development bodies to improve protections available to registrants.
ICANN has not previously performed registrar data escrow services like what you described, but this is something we are working to change as quickly as possible. There are nearly 900 registrars and millions more gTLD domain names, so as you might imagine, it’s a complicated project.

Kamil Iskra 04.03.07 at 1:27 pm

While I do understand that ICANN can’t perform the bulk transfer of all RegisterFly’s domains until the accreditation is terminated, I frankly don’t understand why a transfer can’t be made for the names that would have already expired and are currently in pendingDelete or a similar status (as you mentioned above, some registries actually kept them active).

If RegisterFly didn’t renew a domain name on time, than they should have lost any saying about the given domain, shouldn’t they? Hence, it should be possible for ICANN to legally transfer the name to another registrar, and for the rightful owner to renew it.

I do realise that this would be a logistical problem due to the largely incorrect whois data, but let’s be honest: given RegisterFly’s record, ICANN is likely to face the same problem with the bulk transfer anyway.

Will 04.03.07 at 1:34 pm

“ICANN has not previously performed registrar data escrow services like what you described, but this is something we are working to change as quickly as possible. There are nearly 900 registrars and millions more gTLD domain names, so as you might imagine, it’s a complicated project.”

I don’t doubt that for a second, Mike.

Until registrant data is made more centralised i.e. the registries serve as the masters of the registrant data, I can’t see how this sort of disaster is going to be prevented in the future at one registrar or another.

Thanks for taking the time to respond to my questions.

Mike Zupke 04.03.07 at 1:54 pm

If a name expired but was kept active (i.e. not in RGP or pendingDelete), you may indeed transfer it. It’s basically the same as auto-renew grace. As far as the registry is concerned, a name in one of these states is like any other active name.

As for names in RGP or pendingDelete, there are technical obstacles that prevent transfer. Currently, the SRS (Shared Registration System) is not set up to allow transfers of names that are in either state. In addition, Registerfly, like many other registrars, does not populate Whois for domain names in either of these states. This makes it impossible for a “gaining registrar” to get authorization for the transfer from either the registrant or admin contact (as described above).

Kamil Iskra 04.03.07 at 2:19 pm

Let me rephrase it: what I’m suggesting is that ICANN performs a small-scale version of the bulk transfer process, just for the domains that, I’m assuming, RegisterFly already lost any legal control over, due to its own inaction, i.e., those that would have expired by now were it not for the registries.

Your points about SRS etc. are interesting, but I think they are largely irrelevant for a bulk transfer. If there are currently technical obstacles, you will have to solve them for the large-scale bulk transfer anyway, so why not fix the problems now and test the whole system on a smaller set of domains first? That’s exactly what I’m trying to suggest here.

repb 04.03.07 at 3:26 pm

One question not yet addressed

What would happen to domains in RGP and pending deleted after the bulk transfer?

In other words will the registrant have to pay any of those hefty fees that regsitrars impose to have the name redeemed?

Will ICANN impose, in the process of choosing a new regsitrar, that all domains ins these status can be bring to live whithout the regsitrant having to pay a cent for it?

In the current situation I think it would be much fair if the registries ste the REGISTRY-LOCK status on all pendingDelete domains. I can see no legal or technical reason to prevent them to doing this so could you please shed some light on why this isn’t happening?

repb 04.03.07 at 3:38 pm

Yet another question.

Are the provisons in section 6.c (“Registrant Auth_Info Code Assistance”) of Appendix G of the .org Registry Agreement still in place?

If so what are the specifics actions a regsitrant has to perform?

Note for those ( like me 10 minutes ago ) that do not know the text. Apeendix G, section 6.c reads:

“If, for any reason, a registrant has difficulty obtaining the Auth_Info Code for their domain, PIR will provide a mechanism to assist them in obtaining their code from their sponsoring registrar. This facility will give the sponsoring registrar an additional access method for the Auth_Info Code by providing the code automatically to the registrar upon request by the registrant, with notification to the registrar and registrant that such code has been sent by PIR.”

Shaun 04.03.07 at 4:00 pm

Can I recommend this wiki? It’s independant and trying to help sort out the awful mess with domain ownership information (but doesn’t directly help with transfers). http://dns.wikia.com

Dave Zan 04.03.07 at 5:56 pm

Current technical standards prevent the transfer of domain names among registrars for those in RGP and PD. IIRC, RGP was in discussion over a year before it was finally implemented, but there was probably little to no consideration over a worst-case scenario like this one.

One certainly can always “temporarily do away with that”. But that’s after a way has been devised to make that as smooth as possible with little to no chances of error.

Whether registrants will have to pay the fee is up to the registrar. Do realize they have to weigh the costs and benefits of doing so, the typical “what’s in it for us?” like many of us demand.

I’m sure a lot of people want ICANN to not impose any fees or so. But they have to consider different and even competing interests here, namely those of the registrar/s.

As to your last question, bottom line is they can easily do what people want. But given that people want this and others want that, a balance is sought to consider all interests involved.

Carlos Mario Carvajal 04.03.07 at 6:01 pm

I payed three times my domain coldetec.com, two to registerfly and one to enom:
Mark guzman (eNom) say me:”Unfortunately if you paid registerfly, we (eNom) received no money from them for any of this”.

I payed three times my domain coldetec.com:

first time: jan-27-2007 to registerfly, report number 299 with my Mastercard for us$12.99 for our domain coldetec.com.
second time:jan-31-2007 to registerfly, report number 329 with my mastercad for us$120 newly for our domain account and a hosting.
thirth time: mar-28-2007 enom processed a payment with my mastercad for us$19.98.

Mark guzman (eNom) say me:”Unfortunately if you paid registerfly, we (eNom) received no money from them for any of this”.

why do i pay to everyone and i do not receive any answer?
whre is may money?

Charles 04.03.07 at 8:33 pm

Mike – Once again, thanks to all at ICANN for their efforts.

A few suggestions, as this process moves forward.

I’m sure many of us have kept records of all of our transfers out of Registerfly to Enom, GoDaddy and others. My clients had a total of approx 900 names there before we initiated transfers over the past few months. We still have approx 300 there with long expiration dates and have taken screenshots and prints as proof should that ever become necessary. Many are in the RRP status with absolutely no response from Registerfly despite numerous requests through ICANN and directly.

It’s fairly apparent that the data Registerfly has is, at best, a ‘roll-back’ …as most of our domains still show on their ‘panel’ as still being there, despite being moved and reflected as such by the who-is information.

We would be more than happy to make this database available to ICANN as I’m sure many others would.

Not only should this ease the time and expense at ICANN but it will prevent bulk transfers of names that already have been moved and set-up… unless, of course, you have a method of checking each and every domain name against the current who-is data.

As the picture and time-line becomes clearer, I would suggest that you reach out to all of us for this information (as well as all of our complete ‘stories’ for your files, meetings, and discussions … once those domain names are in ‘safe’ hands … to prevent this from happening again) Many of us are hesitant to put our last names to these posts as who knows what Kevin will do next. I would assume he still maintains control of the who-is information for the domains stilll there, even if there is NO ‘protectly’ on them ?

Mike Zupke 04.04.07 at 3:59 am

This is, unfortunately, one of the complications of using a reseller instead of dealing directly with a registrar. Further complicating matters is the fact that there are resellers (like Registerfly) who are also accredited registrars, and when you register a name with them, you may not have any idea with whom you are registering – even if you read the fine print.

So obviously I don’t have enough facts to tell you what to do, but I say: if you paid eNom, they owe you some kind of explanation about what they charged you for.

Mike Zupke 04.04.07 at 4:10 am

I have heard from others that it seems like Registerfly may not be operating on the most current data. People have observed that domains were missing from their control panels, trouble tickets missing, etc. To date, we have heard no explanation about this from Registerfly.

This is obviously very troubling and it’s why we have invoked our right to audit Registerfly’s records going back to the beginning of their accreditation. (By the way, to date, Kevin continues to allow his registrar to violate its accreditation agreement by denying our access to do the audit; this incredibly selfish behavior is exactly why we’re in court).

As for your suggestion, I can’t predict the future, but in general, I think it would be wise to make and retain as much documentation as you can. At this time, we are not requesting that you provide it to us though.

Mike Zupke 04.04.07 at 4:12 am

One last thing. If there’s a bulk transfer, only the names on Registerfly’s credential (as recorded by the registries) will be transferred. It doesn’t matter what names Rfly *thinks* it has.

Mike Zupke 04.04.07 at 4:22 am

I think you’re looking at the 2002 org agreement. The current (2006) agreement can be found at:

FMX 04.04.07 at 5:43 am

To those in need of their EPP code, please read on:

I tried mailing 4 different people at Registerfly and I had no replies. Then I tried the ticket system (make sure the ticket is under “Obtaining authorisation codes for your domain”) and within 15 minutes I had my authcode replied to me. It is worth a shot.

Anonymous 04.04.07 at 6:41 am

I would appreciate it greatly if someone from ICANN would answer the following questions as I would like a correct answer.

1. What exactly is auth code RRP? What does it mean?

2. I feel like “Old MacDonald’ – here a Who, there a Who. How exactly does the WhoIs work? Why are there so many? Which one is the correct WhoIs? Please explain.

comment removed 04.04.07 at 7:40 am

[comment removed as off topic]
In order for this to remain a helpful resource for Registerfly customers, kindly ensure that comments are on topic.


Mike Zupke 04.04.07 at 7:50 am

In answer to #1:
RRP is not a valid auth code. It’s a protocol (that is no longer used for gTLDs), and apparently Registerfly is populating customer control panels with these letters in instances where it has not yet created an auth code.

In answer to #2:
Ordinarily, a registrar’s whois service is the most up to date. If you have command line access, you can query Registerfly’s whois service via whois.registerfly.com. If you have no idea what I just said, you can get the whois from http://www.registerfly.com/whois/ . Of course, this is only the case for names at Registerfly.

In general, if you’re looking for whois for a domain name and you don’t yet know who the registrar is, you should query the registry’s whois service or use ICANN’s, which is at:
From there, you will get the web and port 43 (command line) addresses for the registrar’s own whois service.

Mike Zupke 04.04.07 at 7:51 am

Thanks for sharing this suggestion.

kmfkm 04.04.07 at 8:31 am

You’re going to need extra staff when you get the RF database. I’ve transferred all mine out, and my account still showed them. Now RegFly has seized my account and if they could — they will change the whois to their thieving, lying selves. Fortunately, my domains are now at eNom and GoDaddy.

Are we sure the abject theft Kevin has done over the past few years doesn’t qualify for jail time? Not just this civil-law contract namby-pamby ICANN is forced to deal with them through.

Jail time for Kevin.

nicola 04.04.07 at 9:01 am

What if I have done everything you suggest to do, i mean everything and i have made 16 attempts for support now with no response, do i just keep on waiting another 5 days, send request, wait 5 more days send request, wait 5 more days, send request and on and on and on. I have Registerfly on my email white list, they are NOT getting blocked by spam, i am not getting any support. I’ve done everything you suggested i do step by step and nothing. I’ve tried emails, phone, fax, support systems, BBB complaint, Icann complaint, is there anyone that can help me, why are we being ignored??

Janet 04.04.07 at 9:03 am

Before October 28th, 2006 .com’s and .net’s were allowed to transfer without an auth code. Why can’t ICANN ask Verisign to lift this requirement in this one instance, for this one registrar, so those customers can transfer away? Many people are stuck at RegFly simply because they have no auth code, or an invalid one. At least let those transfer, then go back to the auth code requirement in the future. Obviously this won’t solve all the problems but will allow many with a .com/.net to leave the sinking ship.

Mike Zupke 04.04.07 at 9:11 am

Keep at ‘em. In particular, continue to use compliance@registerfly.com . The other places might be of some help, but the only people who can unlock, give auth codes, etc., are the people who answer compliance@registerfly.com .

Mike Zupke 04.04.07 at 9:22 am

VeriSign began requiring auth codes at the end of October 2006 because it migrated from RRP to EPP (two different protocols). Without getting into all the details, one effect of this was that auth codes became technically required in transfers. (In other words, VSN didn’t just make up a rule on 28 Oct; this is more complicated than just that.)

Setting aside the technical challenges of temporarily not requiring auth codes, such a move could have potentially significant security consequences. Although a nuissance for some people, auth codes are probably a good idea right now to mitigate against damage caused by potential mismanagement of records, etc., at Rfly. When we get control of the data, things may be different.

Finally, even if the registries temporarily did away with auth codes in this limited circumstance, most customers would still be unable to transfer because their names are locked (requiring intervention by Rfly).

comment removed 04.04.07 at 9:24 am

[comment removed]

This is the place to ask questions and offer constructive advice.



nicola 04.04.07 at 9:39 am

i have been sending to that email!!

nicola 04.04.07 at 9:54 am

i see icann is also forwarding to email robert.oneill@registerfly.com as well as the regular email of compliance@registerfly.com

has this been more succesful for people or still the same issues of keep emailing but no reponses? Whos is Robert oNeill?

repb 04.04.07 at 11:01 am


I will post the question ( which BTW i believe is quite pertinent! ) to another forum.

Anyway thanks for the clarification.


Mike Zupke 04.04.07 at 11:18 am

Interesting idea. We will need to have some discussions with the registries to see how feasible this might be.

Rolandas Miseikis 04.04.07 at 12:24 pm

For what it’s worth, I can confirm that RegisterFly started issuing auth codes. I had two remaining domains stuck with RRP codes. After creating a new support ticket under “Obtaining Authorisation codes for your domain” I got a reply with codes within 20 minutes. Now the only problem I have with RegisterFly is that my account still contains all domains that have been transferred out. I hope the bulk transfer process will not affect these domains.

comment removed 04.04.07 at 1:40 pm

[comment removed]

This is the place to ask questions and offer constructive advice.



repb 04.04.07 at 1:58 pm

I’m sure that every affected registrant would want that. I can’t see this as an issue of competing interests but instead of delivering justice. Don’t you??

As for the last question i am also sure that every affected registrant would prefer to have their domain kept alive than is a “zombie” state. Wouldn’t you??

Alan DeRossett 04.04.07 at 2:42 pm

What is the Icann fee amount?

I’m charged .22 cents from some registars and .25 cents from RegisterFly.com

Alan DeRossett

Mike Zupke 04.04.07 at 2:59 pm

For gTLD registrations between 1 July 2006 and 30 June 2007, the fee is US$0.22 per year. Of course, since Registerfly isn’t actually processing transactions, we won’t see any of the quarters they charged their customers in our name. (We invoice registrars based on actual transactions, as measured by the registries. Registerfly apparently can’t process any transactions because they haven’t funded their registry accounts.)

nicola 04.04.07 at 3:01 pm

Interesting… i emailed registerfly today stating i have made a video of my update attempts in the RF systems to show that it is not user error but registerfly system error, and that domains stuck were for various reasons (1) bad auth (2) no auth (3) can’t unlock as it keeps bouncing back to lock (4) shows unlocked in RF but isn’t in whois data (5) can’t update contact info get RF error and so on… I explained it was my 16th attempt to contact them and also i said i would be happy to provide them with a copy of my video upon request. And wouldn’t you know it i got 6 emails from RF today to confirm/accept transfer of 6 more domains (6 of the 14 that were listed in the email) coincidence…maybe, who knows!

I sent the emails to compliance@registerfly.com, robert.oneill@registerfly.com, transfer-questions@icann.org


Cindy 04.04.07 at 3:13 pm

Two Questions:

As pending delete is not technically a restorable state as the Redemption Period is, what will happen to those names once this Registerfly issue is resolved?

Also, if there is a bulk transfer done to a registrar of ICANN’s choosing, will the 60 day hold be implemented on transfers out to a new registrar?

Mike Zupke 04.04.07 at 3:39 pm

Q1: You are correct that pendingDelete is technically not a restorable state. Of course, there would be no point in holding all of the deleted names in pendingDelete if that wasn’t changed, so we’re working on finding the cleanest way to answer that technical problem.

Q2: The 60-day no-transfer period that applies after a transfer is not mandated by ICANN, and I don’t believe it is mandated by any of the registry-registrar agreements (although I’m no expert on RRAs).

The 60-day no-transfer period is used by some registrars after an ordinary inter-registrar transfer. Among other things, the policy can help to undo domain name hijackings. In the past, we have encouraged registrars not to impose a no-transfer rule following a bulk transfer, but these circumstances are unique, so we (and the gaining registrar) will need to assess all of the facts at the time of the transfer before making a decision. Our primary interest is to protect the registrants.

Andy 04.05.07 at 9:47 am

Well, Regfly has sent me authcodes and unlocked my domains (though one of them still says “Status: clientDeleteProhibited” — is that anything to be concerned about?).

Unfortunately, all my whois info still points to regfly (the *@spamfly.com email addresses, in particular).

All the domains show an unlocked status, and that ProtectFly is turned off. However, when I try to update the info from the regfly control panel, I get a “Error. Domain Name not found.” error (though it still sends an email that the info was changed, even though it was not).

Has anyone else had this situation, and had it get resolved? (i.e. has anyone had regfly actually change the whois info)?

SG 04.05.07 at 10:08 am

Between ICANN and RegisterFly, there is a Registry (Verisign, PIR, Afilias…). The Registry has the technical capability to unlock a domain name or to renew it. Of course it is not their job to do that but an exceptional situation requires an exceptional action. Why do the Registries don’t help Registerfly’s customer?

Bigfoot 04.05.07 at 10:09 am

Transferring with a ‘PUSH’ within the Registerfly system sometimes releases whois data (not always). As advised elswhere, create a new account at RF using a different e-mail address for contacts, then use their ‘Change Ownership’ system to ‘Push’ the domain to the new account. This has worked for me for some domains. Sometimes I’ve needed to ‘Push’ to a third account to be able to ‘unlock’ the domain. It hasn’t worked for some as well, but worth a try on a sample if you’ve got a large number in this state.

O. E. Cruiser Small 04.05.07 at 10:15 am

ICANN – the E-Mail address of compliance@registerfly.com is not working – all the E-mail I send to this adress is coming back !!!!

Please note the following…

I’m sorry to have to inform you that your message could not
be delivered to one or more recipients. It’s attached below.

If you do so, please include this problem report.

The mail system

: host mx1.emailsrvr.com[] said: 554
5.7.1 : Sender address rejected: ACL
from_senders_likelyspam (in reply to RCPT TO command)

I gues it’s time to instigate a Lawsuit against ICANN and RegisterFly together ! Maybe that might instil them to do something about all this !

Mike Zupke 04.05.07 at 10:20 am

From the message you pasted, it looks like Registerfly’s email server thinks you are a spammer. Do you think a lawsuit is going to fix that? Why don’t you try sending from a different email address or sending fewer messages? It seems like, rather than take initiative and help yourself, you’d rather blame everyone else.

Mahmoud 04.05.07 at 1:41 pm

What about domains with incomplete whois information?
They returns :
gc:sc:Unable to establish session for domain-name.ext

from registerfly.com whois

and incomplete whois from others
(without any contact information, just the DNS servers)

I have been contacting registerfly for more than a month, communicating with different people there and it seems none of them know how to fix it.

Mike Zupke 04.05.07 at 1:49 pm

We have seen some problems where Registerfly has failed to populate Whois, but they’ve generally been able to correct them when we bring it to their attention. I’ve emailed you to get some more information…

Mahmoud 04.05.07 at 3:24 pm

Domains not found probably means that your domains are registered in enom.com through registerfly as a reseller.

If the status is OK, you can still transfer them. Email confirmation is not required.

If these domains are in Enom.com (check the whois), you can contact Elida Flores elida.flores(at)enom(dot)com she could be able to help and give you access to your domains.

Sam Flanders 04.05.07 at 8:34 pm


My domain 4email.biz is valid through 2010. That is the good news. The bad news is that when I transferred this domain from Godaddy Software to Registerfly, the transfer did not complete properly, and the admin contact and other contact data was never populated — It is completely blank on my Regiserfly control panel display. A whois of 4email.biz shows registerfly’s corporate NJ HQ and the admin email support@registerlfy.com. This domain is not locked – it just never got filled in with the correct contact info. I emailed rfly at compliance, and they apparently tried to update the record today, but it was not successfull. I just get an error message every time I try to fill in the admin data.

My question: How are you going to know that I am the owner of this domain when you complete the bulk transfer? I have taken screenshots from my registerfly account showing the transfer completion and the blank admin data, but I don’t know what else to do. Because of the way authcodes work, there will never be a way for me to receive the beginning of the authorization scenario, even if I am able to get the authcode for 4email.biz from neulevel (since the system will send to support@registerfly.com, rather than registerfly1@4email.biz). Incidentally, I have been able to get 5 of 6 domains back to Goddaddy, but his one is a tough nut.

Andy 04.05.07 at 10:12 pm

Thanks for the comment. Unfortunately, they are all registered at registerfly (I had a few at enom, and already extracted them).

So I’m still hoping that regfly updates the whois info since I can’t get the “approve this transfer” emails due to the spamfly email addresses…

Mike Zupke 04.06.07 at 4:36 am

clientDeleteProhibited is the status that keeps your name from deleting due to Registerfly’s failure to fund the registry. (Note: some registries use different status indicators, so others should not panick if they don’t see clientDeleteProhibited.) It has nothing to do with transfers.

Your whois record will need to be more or less valid in order to transfer because of the FOA issue described above. If the spamfly address forwards to your email address, you should be ok. Since it appears Rfly allowed this domain to expire and be registered elsewhere, I wouldn’t count on that so you should probably update your email address in Whois. As an alternative, your “gaining registrar” can send you an FOA through alternative means (other than email) so you should check with them to see what they will allow.

Mike Zupke 04.06.07 at 4:45 am

What, exactly, was their explanation? I think you should ask them to try again.

comment removed 04.06.07 at 5:44 am

[comment removed]

This is the place to ask questions and offer constructive advice.

Sam Flanders 04.06.07 at 6:41 am

I have had no communiation from the company, despite dozens of attempts to communiate with them. I knew of the attempt to change the contact information because their system sends out an automated security alert when anyone attempts to change the admin info. They attempted the change 3 times yesterday.

comment removed 04.06.07 at 8:43 am

[comment removed]

This is the place to ask questions and offer constructive advice.

Comments on this entry are closed.