4 ms·
I also ran into a problem with GoDaddy when trying to transfer a domain name that was protected by Domains by Proxy. I first got a notification that I needed to
by jarin 15y ago
I also ran into a problem with GoDaddy when trying to transfer a domain name that was protected by Domains by Proxy. I first got a notification that I needed to enter into a new agreement, so I did. Then I got a notification that I needed to cancel my private registration, so I did. Then I got this:
"The transfer of MYDOMAIN.ME from Go Daddy to another
registrar could not be completed for the following
reason(s):
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)."
So it looks like they're auto-rejecting domain transfers if you're using Domains by Proxy?
- mattvot 15y agoYeh, This has been the case for a while. It is because they cannot verify the owner, as the whois info is hidden behind DBP. I've been trying to cancel my DBP subscriptions, to return my details to whois and transfer the domain. They don't make it easy. I lost my account details, and am trying to retrieve my account. I filled in their form and attached my drivers license scan ... got an email today saying they need a scan of some ID :/
- soult 15y agoThey are locking you in. Either you turn off whois privacy, making your name forever connectable to the domain thanks to such databases as whois.sc, or you stay at GoDaddy. Forever.
- chexov 15y agoSame happend to me. I had to login to DBP (same username and password as GD), cancel the protection, than ask my new registrar (Gandi) to restart the transfer. It seems to have worked, at least now I am in the 'waiting period' for the transfer to finalize.
- gregholmberg 15y agoI transferred two domains away from GoDaddy that were protected by Domains by Proxy. They did require that the WHOIS guard be dropped, even though both registrars offered a WHOIS-protecting service. It did feel like GoDaddy was moving the goalposts. Since I had no deadline and no feeling of urgency, I just allowed the entire process to play out naturally. There were periods when I was busier elsewhere and didn't press the issue for a month or two at a time, but I spent the better part of sixteen months getting both transfers completed. Update: I bought a standard membership to DomainTools to see if the info ever leaked. It looks like the patient approach paid off, and that the exposed WHOIS info was not crawled during the transfers. Taking the time to make sure both ends of the transfer were prepared was worth the effort, but I think it's probably luck that kept the info from being picked up.
- soult 15y agoDomaintools may be the best-known whois database, but it isn't the only one and not all of them are as easy to check against.
- aeden 15y agoPersonally I think this should be considered a violation of their agreement with ICANN. There is nothing wrong with providing privacy protection on Whois data, but they should not be rejecting transfers nor should they be blocking legitimate email delivery.
- cobrabyte 15y agoThis happened to me, as well. It took me forever to disable the Domains by Proxy stuff. I must have had 35 different DBP accounts that held all my domains. There's no simple way to get the login information for the DBP accounts, either. It was a 4-step process for each of those 35 accounts. And, here I was thinking I was the one doing the punishing. GoDaddy put me in my place.