I have 2 questions about GoDaddy?

[Name Trader]

1) Is it possible to receive a push of a domain from another GoDaddy member without adding a 60 Day hold. I remember doing this in the past, but don't recall how I did this. Is this still possible? How to do this? @Joe Styler

2) Does GoDaddy have any sales of NGTLD's (expiring or members sales)? I've tried many times to use their search form (the one with all the tick boxes), but I always fail to find any NGTLD's for sale. What am I doing wrong?

 

[dirk]

We cant do that the losing registrant has to pick it's part of a change ICANN made to help reduce domain theft I believe.

Thanks for the input.... I do spot an 'I believe' so you're not 100% sure .

Seriously though, GoDaddy having a lot of aftermarket business would gain more permanent clients if the push process was as easy as some as the registrars mentioned before.

A couple of years ago it was a plus if you were selling a domain at GD. That isn't the case anymore in my experience.

So work your magic and get the word out to the techs at GD

 

[Name Trader]

Yes it is correct, you as the changer of the info pick if you want the update to lock the domain or not and you accept the change.

So we do have the option to NOT lock the domain when changing the whois data? What is this guessing game with you sending the confirmation question multiple times, with only 1 of those emails, going to a link which allows us to NOT lock the domain. As described by @NameDeck. For example. If you send 4 emails and only one of these emails has the ability to not lock the domain, we might just give up, if it's always the last email. Is there any way from telling these emails apart, so we only need to click once, and not multiple times? Or send the ability to NOT accept a lock always in the first email? Or even better. Always send an email with the ability to NOT accept a lock. There is no rhyme or reason, why it should only be in one of your emails, and not all.

 

[dirk]

So we do have the option to NOT lock the domain when changing the whois data? What is this guessing game with you sending the confirmation question multiple times, with only 1 of those emails, going to a link which allows us to NOT lock the domain. As described by @NameDeck. For example. If you send 4 emails and only one of these emails has the ability to not lock the domain, we might just give up, if it's always the last email. Is there any way from telling these emails apart, so we only need to click once, and not multiple times? Or send the ability to NOT accept a lock always in the first email? Or even better. Always send an email with the ability to NOT accept a lock. There is no rhyme or reason, why it should only be in one of your emails, and not all.

Yeah it strange. When I put those images together I only got one email though.

I checked my trash, previous time it was 3, 2 in English and one in my native language.

Maybe they made some changes again.

 

[Domainstore]

Thanks for the info.
I forget sometimes a lot also.

 

[Joe Styler]

So we do have the option to NOT lock the domain when changing the whois data? What is this guessing game with you sending the confirmation question multiple times, with only 1 of those emails, going to a link which allows us to NOT lock the domain. As described by @NameDeck. For example. If you send 4 emails and only one of these emails has the ability to not lock the domain, we might just give up, if it's always the last email. Is there any way from telling these emails apart, so we only need to click once, and not multiple times? Or send the ability to NOT accept a lock always in the first email? Or even better. Always send an email with the ability to NOT accept a lock. There is no rhyme or reason, why it should only be in one of your emails, and not all.

I guess you have never dealt with the government before I am not going to go look this up because I dont have the time, you can if you want or someone here more familiar with the ICANN rules off the top of their head can chime in. It's been about a year since I looked at the policy side of this in depth. You can look for ICANN change of Registrant policy or something similar in Google.

I remember there are specific emails we must email and I believe some we either can include or must include. Anyway there are at least two that I know off the top of my head must be sent and it may be up to four. We need to send to the gaining and losing registrant on the WHOIS change, i.e. the new and the old WHOIS owner. If I remember the rules right only the old or losing Registrant can choose the lock status - lock or unlock after change, and only the new Registrant can accept it with the lock or reject it.

This is where it gets a bit fuzzier, we either can or must send the emails to the Account holder as well. If all of these people are you then you are going to get three of four emails. I think we can alert the account holder as well and not must but we chose to because it helps make it an easier process for customers, especially those that do not have access to an old email address or something.

It is ICANN mandated and the process is more or less mandated as well in that you are definitely going to get multiple emails. Personally I think the process is a bit cumbersome, especially for a casual user who doesn't know what a registrant is or something. Having said that, I do appreciate the underlying reason for it as an effort to protect the registrant from having their domains stolen. I also appreciate that we are dealing with a lot of stakeholders and various countries and cultures around the World when ICANN is making decisions for the entire Internet like this and that coming to a conclusion that works for everyone isn't always very easy.

We have changed our process multiple times over the past year as well in response to customer feedback and are trying to get to a place where it is easy for anyone to change their account or registrant and still be in compliance with ICANN.

 

[Name Trader]

I guess you have never dealt with the government before I am not going to go look this up because I dont have the time, you can if you want or someone here more familiar with the ICANN rules off the top of their head can chime in. It's been about a year since I looked at the policy side of this in depth. You can look for ICANN change of Registrant policy or something similar in Google.

I remember there are specific emails we must email and I believe some we either can include or must include. Anyway there are at least two that I know off the top of my head must be sent and it may be up to four. We need to send to the gaining and losing registrant on the WHOIS change, i.e. the new and the old WHOIS owner. If I remember the rules right only the old or losing Registrant can choose the lock status - lock or unlock after change, and only the new Registrant can accept it with the lock or reject it.

This is where it gets a bit fuzzier, we either can or must send the emails to the Account holder as well. If all of these people are you then you are going to get three of four emails. I think we can alert the account holder as well and not must but we chose to because it helps make it an easier process for customers, especially those that do not have access to an old email address or something.

It is ICANN mandated and the process is more or less mandated as well in that you are definitely going to get multiple emails. Personally I think the process is a bit cumbersome, especially for a casual user who doesn't know what a registrant is or something. Having said that, I do appreciate the underlying reason for it as an effort to protect the registrant from having their domains stolen. I also appreciate that we are dealing with a lot of stakeholders and various countries and cultures around the World when ICANN is making decisions for the entire Internet like this and that coming to a conclusion that works for everyone isn't always very easy.

We have changed our process multiple times over the past year as well in response to customer feedback and are trying to get to a place where it is easy for anyone to change their account or registrant and still be in compliance with ICANN.

Hi Joe,

I certainly wasn't intending you to need to lookup the rules up on ICANN again. I take your word for it that GoDaddy would not be asking for stuff if it is not compulsory by ICANN. But my point about the emails sent to the Registrant email address. Why do some emails to the registrant have the option to opt out of lock, and on other emails for the same transaction, do not include this option (ref: @NameDeck above). IMHO, ALL emails to the registrant for the same transaction should include both options. Or the email with the option to opt out of the lock should be easily identifiable as such.

 

[tonyk2000]

I remember there are specific emails we must email

This opens an interesting question. For many years (before the current ICANN policy), GoDaddy copied whois details from an old registrar for domains transferred-in. This included domainsale transactions, where the buyer elected to receive the domain by starting a registrar transfer to GoDaddy. Even though the buyers were supposed to update whois to theirs, many never bothered to. I recently received a renewal reminder (!) from GoDaddy for domain I sold years ago, the domain is currently with GD and is privacy protected. So it must still have my whois, even though I do not really own it neither technically nor legally. So, what will happen should the buyer finally decide to update whois someday? The system will send me an email to confirm. After many years, I do not remember who purchased it, it may also be that he subsequently resold it etc, so I simply cannot act on such a such a (potential) request today. How is such a situation supposed to be handled? I mean on GD level. A possible solution for the real owner might be another registrar transfer, which would work if he manages to download csv with authcode (not requesting it by email, since in this case I will receive the code - and, similarly, I would be unable to do anything with it). Any other solutions?
@Joe Styler - what do you think?

 

[Joe Styler]

Hi Joe,

I certainly wasn't intending you to need to lookup the rules up on ICANN again. I take your word for it that GoDaddy would not be asking for stuff if it is not compulsory by ICANN. But my point about the emails sent to the Registrant email address. Why do some emails to the registrant have the option to opt out of lock, and on other emails for the same transaction, do not include this option (ref: @NameDeck above). IMHO, ALL emails to the registrant for the same transaction should include both options. Or the email with the option to opt out of the lock should be easily identifiable as such.

My guess off the top of my head would be that one email is meant for the registrant and the other is meant for the account contact - your default account info at the account and not domain level. If they are both the same email address that would explain it.

 

[Joe Styler]

This opens an interesting question. For many years (before the current ICANN policy), GoDaddy copied whois details from an old registrar for domains transferred-in. This included domainsale transactions, where the buyer elected to receive the domain by starting a registrar transfer to GoDaddy. Even though the buyers were supposed to update whois to theirs, many never bothered to. I recently received a renewal reminder (!) from GoDaddy for domain I sold years ago, the domain is currently with GD and is privacy protected. So it must still have my whois, even though I do not really own it neither technically nor legally. So, what will happen should the buyer finally decide to update whois someday? The system will send me an email to confirm. After many years, I do not remember who purchased it, it may also be that he subsequently resold it etc, so I simply cannot act on such a such a (potential) request today. How is such a situation supposed to be handled? I mean on GD level. A possible solution for the real owner might be another registrar transfer, which would work if he manages to download csv with authcode (not requesting it by email, since in this case I will receive the code - and, similarly, I would be unable to do anything with it). Any other solutions?
@Joe Styler - what do you think?

That is where the multiple contacts come in to play that we are either allowed to or must email. So in this case we would email you and them and their account email and only two of them would have to approve the change. The way it works though would protect him if - and I know you would not do this, I am only making a hypothetical example here, you are the registrant still and you emailed in and said look I am the registrant that is my domain please give it to me. There would be a change at that point, the losing party would be notified because of this ICANN rule and he can say, wait a minute, no I don't accept this WHOIS change. Then he could go dispute this and presumably keep his domain. There are more steps and caveats but big picture, quickly here this would prevent a domain theft which is what they put the policy in place for.

 

[dirk]

This opens an interesting question. For many years (before the current ICANN policy), GoDaddy copied whois details from an old registrar for domains transferred-in. This included domainsale transactions, where the buyer elected to receive the domain by starting a registrar transfer to GoDaddy. Even though the buyers were supposed to update whois to theirs, many never bothered to. I recently received a renewal reminder (!) from GoDaddy for domain I sold years ago, the domain is currently with GD and is privacy protected. So it must still have my whois, even though I do not really own it neither technically nor legally. So, what will happen should the buyer finally decide to update whois someday? The system will send me an email to confirm. After many years, I do not remember who purchased it, it may also be that he subsequently resold it etc, so I simply cannot act on such a such a (potential) request today. How is such a situation supposed to be handled? I mean on GD level. A possible solution for the real owner might be another registrar transfer, which would work if he manages to download csv with authcode (not requesting it by email, since in this case I will receive the code - and, similarly, I would be unable to do anything with it). Any other solutions?
@Joe Styler - what do you think?

If the domain is in your account, you are the one who will receive the owner change approval email.

They send the email to both the current account holder and the domain registrant email address.

If you accept the change yourself (as they send it to the current account owner email) right away, the email sent to the registrant owner email will be accessible but when they try to confirm it shows as invalid.

So the first one to make it to the confirmation page basically is in charge (you can opt out there).

After this is confirmed they will send another confirmation to the new registrant email address to accept as well. This would be your email.

Still following?

On top of that: I've recommended before in this thread that you can freely change your Administrative email, which should be the one auth codes go to. It does not impose a 60 day lock.

However, it looks like they send the auth code to both the registrant email AND the administrative email when they're not the same so be careful if you use this as a last resort. The old owner will receive the code as well.

 

[Name Trader]

That is where the multiple contacts come in to play that we are either allowed to or must email. So in this case we would email you and them and their account email and only two of them would have to approve the change. The way it works though would protect him if - and I know you would not do this, I am only making a hypothetical example here, you are the registrant still and you emailed in and said look I am the registrant that is my domain please give it to me. There would be a change at that point, the losing party would be notified because of this ICANN rule and he can say, wait a minute, no I don't accept this WHOIS change. Then he could go dispute this and presumably keep his domain. There are more steps and caveats but big picture, quickly here this would prevent a domain theft which is what they put the policy in place for.

I have about 5 or 6 of these examples. I receive every year renewal notices and such. So what is your suggestion to get the new owner to change the whois to himself? Ask GoDaddy to give me the domain? Or is there a less fractious way to do this? Since I don't actually want these domains back. I just don't want my whois on those domains that don't belong to me. I think I have even reported these domains to Godaddy for wrong whois. But I don't see anything happening, although I may have just given up because the procedure was just too onerous.

 

[Name Trader]

My guess off the top of my head would be that one email is meant for the registrant and the other is meant for the account contact - your default account info at the account and not domain level. If they are both the same email address that would explain it.

OK. So which one of those 2 emails is allowing to opt out of the domain lock and which one isn't? And shouldn't they both be the same, allowing both to opt in or out of the lock? Shouldn't this need correcting? Is there any way to tell these emails apart? I can understand and follow your explanation, except @NameDeck is saying he is receiving 3 or 4 of these emails? How does that happen?

 

[tonyk2000]

I just don't want my whois on those domains that don't belong to me

Exactly! In an (unlikely) event of UDRP, we the previous owners will become the Respondents. As it is what GD will disclose and confirm to WIPO/NAF.

 

[dirk]

I checked some of my older emails and it looks like the 'flood' of emails only happened when someone pushed the domain and I changed whois right away on the acceptance page.

Maybe that's because technically it gets pushed first, whois changed after? So the domain would already be in my account upon registrant change, hence the extra emails sent to my account email. Getting two separate emails with the same content but one English and one in my native language also adds to the number I guess.

Wouldn't it be easier to have something in place like Namesilo or Namecheap? You do get notifications (just one from the top of my head) but you can set your account to autoaccept and use your preferred registrant info by default. Just a thought.

I would think they comply to ICANN regulations so it can be done. Might not be an easy task for a backed like GDs though.


Bottom line, what bothers most people is the uncertainty of the process being flawless. That's the biggest holdup. Take that away and I'm sure you'd receive more love

 

[Joe Styler]

I have about 5 or 6 of these examples. I receive every year renewal notices and such. So what is your suggestion to get the new owner to change the whois to himself? Ask GoDaddy to give me the domain? Or is there a less fractious way to do this? Since I don't actually want these domains back. I just don't want my whois on those domains that don't belong to me. I think I have even reported these domains to Godaddy for wrong whois. But I don't see anything happening, although I may have just given up because the procedure was just too onerous.

The short answer is nothing. Not much you can do besides reporting it as invalid whois. We cant go change the WHOIS and neither can you. So beyond us and you telling the owner to update it there isn't much short of a court order that will force them to change it. I can take you through all the processes and procedures and rules around it and how we need to tell people to update their whois already, etc but the bottom line is at the end of the day you can't do anything more than you did short of a court order.

 

[tonyk2000]

Not much you can do besides reporting it as invalid whois.

I probably won't. I respect my (old) customers, and, since they did not bother before, it may well be that they will not understand what the problem is, or will not respond in timely fashion, and GD may block their domain... And if the domain is under privacy - then whois is technically correct (domains by proxy).

 

[Name Trader]

The short answer is nothing. Not much you can do besides reporting it as invalid whois. We cant go change the WHOIS and neither can you. So beyond us and you telling the owner to update it there isn't much short of a court order that will force them to change it. I can take you through all the processes and procedures and rules around it and how we need to tell people to update their whois already, etc but the bottom line is at the end of the day you can't do anything more than you did short of a court order.

How do we contact the owner?

 

[Joe Styler]

Didn't you sell them the domain? You should have contact info from when you sold it to them otherwise I'm not sure why they have your info on the WHOIS for their domain.

 

[Name Trader]

Didn't you sell them the domain? You should have contact info from when you sold it to them otherwise I'm not sure why they have your info on the WHOIS for their domain.

Not if they bought thru GoDaddy/Afternic, we don't know who the buyer is. IIRC.

 

[Joe Styler]

Yeah you would or should have. For the last year or so we have been updating the WHOIS on the move to the buyer. It has been longer than that on the Afternic side. Before that on the GoDaddy auction side there was a link in the sold section that allowed you to contact the buyer. To be frank though, what makes you think they will care even if you do contact them? If you sold it with us not only did we contact them when they bought it to urge them to change the WHOIS (under the older system, as I said the new flow updates the WHOIS by default), but we also send out mandated reminders to them about it at least once a year. Beyond that if you reported it to invalid whois and they see the info is bad they suspend the domain so the customer can't use it until they resolve the WHOIS issue. They also reach out, often times by phone as well in addition to the other times we reached out above. I'm not saying this in the tone of a smart a**, but as a guy who used to run a few departments here and knows that we had a hard enough time getting people to accept the domains they paid thousands for into their accounts let alone getting them to update the WHOIS. This is precisely why over time we moved to ways where could "force" the domain to the new owner and use the new WHOIS from their info. Beyond that it is not usually an easy task to get someone to change their info. The right step for you would be to report invalid whois and then let the department reach out. As I initially said, bottom line is you can't force someone to change the WHOIS short of a court order.