Godaddy now requires you to change your password every 6 months
godaddy.com
godaddy.com
I'm so glad I switched all my domains away from godaddy 6 months ago to Dynadot. They've been awesome, their interface isnt cluttered to hell, and the people respond to emails quickly.
Forcing periodic password changes is a terrible solution. Most people just increment a counter each time: mysecretpassword123 -> mysecretpassword124. I'd much prefer to instead give users access to a log of all of their activity.
I've had some bad experiences with Enom over the years to say the least.
I deal with business owners daily who have no idea who their domain is with, let alone their username or password. At least this will force them to touch their domain at least once/year.
Security policies like this make things worse, not better. The only way most people know to remember a password that changes regularly is to email it to themselves or post-it it to their monitor.
I know on every site I have to do this with I end up forgetting the password (somehow they seem to be coupled with strange character count and type requirements), and I have to rescue my password anyway. Might as well just have a login page that says "enter your email address and click 'send' to log in" and then have it send the cookie to you you continue with.
Site security can not be stronger than the weakest attack vector. Now that the login vector is so difficult they might as well remove it and just use the "Change Password" vector as the only way in.
As others have mentioned, I've always hated the complicated forced 60-day lock-in with GoDaddy. I"ve tried to avoid them like the plague and use BlueHost.com instead. Zero hassle, great customer service (and no, I'm not affiliated with either in any way)
I moved my domains over to NameCheap. They seem kind of amateurish at times, but they get the job done, and I haven't seen any major horror stories about them. I was using Dynadot for a while, but the recent 3-day downtime with no status updates rubbed me the wrong way.
* Evidence of fraud * Uniform Domain-Name Dispute Resolution Policy (UDRP) action * Court order * Reasonable dispute over the identity of the person authorizing the transfer * Domain name is on hold due to payment owed for a previous registration period * Express written objection from the domain name holder * Domain name is in 'Lock' status (Registrars must provide a readily accessible and reasonable means for name holders to remove the lock status. Contact your registrar for assistance.) * Domain name is within 60 days of initial registration * Domain name is within 60 days of a previous transfer
It is _GoDaddy's_ amendment to those points that adds the 60 day wait on registrant information changes. From ICANN:
2. A registrant change to Whois information is not a valid reason to deny a transfer request.
http://www.icann.org/en/announcements/proposed-advisory-19se...
The problem is GoDaddy forced users to click the link that they have to abide by the 60-day policy in order to update their contact information, which they claim falls under the point:
* Express written objection from the domain name holder
which is obviously a stretch under the most lenient arguments.
My only wish at this point is that name.com had an API like Enom.
I'm NOT asking about how long the record takes to become active and propagate. Just the UI.
I switched to Dynadot and havent had a bad experience. Their interface is simple, quick, and clean. The pricing makes sense, and their people are friendly and helpful. YMMV.
I registered a domain with them yesterday - but have separate hosting, so don't need to buy more of it from them. I'm unable to do anything beyond change DNS servers (no custom mx records, for example).
When I contact their support about something, it usually gets a prompt (within 10 minutes) response. But when it deals ith deleting domains, they take forever to respond. And they refuse to let you delete/cancel a domain. Even though ICANN's policy lets you do so for 5 days with the grace period. Since the ICANN still hasn't changed the policy AFAIK.