Trapped at GoDaddy?

[-db-]

First off, let me say I have nothing against GoDaddy. However, the majority of my names are not registered there, and I'm trying to simplify my life by moving all my names to one place.

So, I tried to transfer a couple names that I recently bought from other domainers, but I get a notification saying the names can't be transferred out of GoDaddy because they were moved from one GoDaddy account to another within the past 60 days. And of course, they were indeed moved because ownership change.

The names are set to expire before 60 days is up, so it appears I will be forced to renew at GoDaddy.

This is crazy. It's not the normal "registered within 60 days" rule that all registrars have. These names have been registered since 2002. This appears to be a GoDaddy imposed rule of their own making and design.

Am I missing something? Am I really stuck? No way around it?

 

[Redleg]

I believe that's normal practice at most registrars, not just GD..
An ownership change is regarded the same was as a fresh registration when it comes to the 60 days transfer rule..

 

[-db-]

An ownership change is regarded the same was as a fresh registration..

Ahhh... I was not aware of that. I guess I've never run into the situation before.

Thanks for the reply Redleg.

 

[RJ]

No, this is a policy specific to GoDaddy... :td: to them.

 

[Redleg]

You're welcome..

1. Go Daddy's Role in this transaction
......
.....
The domain name may not be transferred to another registrar within 60 days of the completion of the change of Registrant transaction (the "Transfer Prohibition Period"). In the event the domain name is subject to another change of Registrant within the Transfer Prohibition Period, the 60 day Transfer Prohibition Period will begin again upon completion of the subsequent change of Registrant transaction.

http://www.godaddy.com/gdshop/legal_agreements/show_doc.asp?se=+&pageid=DOMAIN_NC

And I believe this not only applies to account changes, but if you update the domains Admin contact name and/or e-mail address as well..
(60 new days before you can transfer away.. )

No, this is a policy specific to GoDaddy... to them.

It is?? Then to them as well...

 

[LeeRyder]

I think the tactic is not to prevent you from leaving, but to provide a cushion to domain owners who's name might have been hijacked. The thinking is that GD might believe that if a stolen domain isnt discovered within 60days, it wont be or it hasnt been stolen.

 

[dgridley]

And that makes sense...

I think the tactic is not to prevent you from leaving, but to provide a cushion to domain owners who's name might have been hijacked. The thinking is that GD might believe that if a stolen domain isnt discovered within 60days, it wont be or it hasnt been stolen.

 

[jim]

Big

And I believe this not only applies to account changes, but if you update the domains Admin contact name and/or e-mail address as well..
(60 new days before you can transfer away.. )
...

BIG One there

Quote: Dear Jim,

Thank you for contacting customer support. Changing the name servers and phone number for the domain will not start the 60 days. Changing the name, including just the middle initial, or company in the contact information will start the 60 day period. Please let us know if we can help you in any other way

 

[Wesley]

Gar GoDaddy makes me sick. I registered the one domain I personally purchased (my others were from trading stuff away and from buying with NP$ here =P) and have always regretted it. Then their commercial during the superbowl. Geez, can you say cheap?

 

[-db-]

No, this is a policy specific to GoDaddy... :td: to them.

I was just thinking... surely I would have run into this before at other registrars, because I've bought and sold a lot of names. Well crap. I guess in this case, I really am stuck.

I think the tactic is not to prevent you from leaving, but to provide a cushion to domain owners who's name might have been hijacked. The thinking is that GD might believe that if a stolen domain isnt discovered within 60days, it wont be or it hasnt been stolen.

Yeah, I can understand that. Still though, I wish there was a way for rightful owners to bypass it.

Oh well, thanks for the replies everybody.

 

[1rrr1]

Too bad that there are such things as domain hijacking in this world, therefore there are these stupid rules to try to stop it.

 

[kw31]

The rule sucks for me ...
I know it's for our own protection, but when I want to sell a domain I regged for less than a month it sucks when I have to wait for another month!

 

[Grrilla]

I think the tactic is not to prevent you from leaving, but to provide a cushion to domain owners who's name might have been hijacked. The thinking is that GD might believe that if a stolen domain isnt discovered within 60days, it wont be or it hasnt been stolen.

I tend to agree. I've probably been a bit overly paranoid about this, as I have had alot of recent difficulty in "prying" names away from several registrars- registrars other than Gddy, and when you are trying to get access to names that you have paid for ownership rights to, it sure can *feel* like the registrar is conspiring against your attempt at transferring names away from them, or moving off of their name servers, (which are often using your domain as a dierctory page w/ their own affiliate links.)
However, I still continue to believe that there are company procedures and *particularly* some site navigational schemes, that are set up to make it difficult on users and that strongly *deter* the customer from transfering away.
I have literally spent a half hour bouncing around at a couple of sites, trying to get to the right place to make DNS, lock status, and informational changes for *all* contact data necessary to set up a transfer. Once logged into a user CP, I can see no obvious reason for name management to be as difficult as it has been made to be, at some of these sites.

 

[IdahoFarmer]

Moniker.com imposed the same limitations on me.

 

[William9]

What were the extensions of the names Godaddy refused transfers?

 

[jaydub]

I have no problem with it...It is inconvenient however...
It provides protection for both sides...If I sell a name to you, you can't transfer it out & then cancel the CC payment to your account leaving me high & dry or having to go through the enormous amount of time hassle to reclaim the name.....
I have transferred names out of GD with no problems when there are no conflicts to there Reg/Transfer terms...I agreed to the terms, I guess I gotta' live with 'em.
If you are buying a name from someone, that is reg'd at GD, and you want it out of there, ask them not to push it (then there is no ownership change, unless they have just purchased it)....Then you initiate the transfer to your registrar and all they have to do is approve the transfer when it comes to them...I have done this many times when names might be at a registrar I am not to familiar or pleased with.

Jim

 

[rtonia]

Namecheap doesn't do that ... or does it?

 

[armstrong]

Its a reasonable rule, but I don't see how they can do this. If your domain is unlocked, and you request a transfer to a different registrar, isn't GD required by the current ICANN rules to process the request? If GD can get away with this, then what's to stop some obscure Pool-affiliated registrar from imposing a more onerous time limit, like one year?

 

[Dave_Z]

Moniker.com imposed the same limitations on me.

That's actually Moniker's "niche", so to speak. They have the most number of
security measures I've seen so far.

It's simply a matter of taking time to understand how. Read their fine prints,
ask them questions, etc.

Its a reasonable rule, but I don't see how they can do this. If your domain is unlocked, and you request a transfer to a different registrar, isn't GD required by the current ICANN rules to process the request?

This might explain why: http://icann.org/transfers/policy-12jul04.htm:

Upon denying a transfer request for any of the following reasons, the Registrar of Record must provide the Registered Name Holder and the potential Gaining Registrar with the reason for denial. The Registrar of Record may deny a transfer request only in the following specific instances:

1. Evidence of fraud
2. UDRP action
3. Court order by a court of competent jurisdiction
4. Reasonable dispute over the identity of the Registered Name Holder or Administrative Contact
5. No payment for previous registration period (including credit card charge-backs) if the domain name is past its expiration date or for previous or current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Record prior to the denial of transfer.
6. Express written objection to the transfer from the Transfer Contact. (e.g. - email, fax, paper document or other processes by which the Transfer Contact has expressly and voluntarily objected through opt-in means)
7. A domain name was already in “lock status” provided that the Registrar provides a readily accessible and reasonable means for the Registered Name Holder to remove the lock status.
8. A domain name is in the first 60 days of an initial registration period.
9. A domain name is within 60 days (or a lesser period to be determined) after being transferred (apart from being transferred back to the original Registrar in cases where both Registrars so agree and/or where a decision in the dispute resolution process so directs).

If GD can get away with this, then what's to stop some obscure Pool-affiliated registrar from imposing a more onerous time limit, like one year?

Like most if not all things, every advantage has a disadvantage.

 

[-db-]

Well, how about this.....

Both the old owner (who the name was purchased from) and the new owner contact them to verify that everything is legitimate, and even provide some sort of extra proof if they request. Do you guys think they should let domains be transferred away then?

I'm not asking if they will. I'm just asking if they should, in your opinion.

P.S. - Hey there William. In regards to your question, they were .US domains.