BIN purchases at godaddy (1 Viewing)

Yes, that's correct. When you "push" the domain to another Namespro account only a domain update (the RANT changes) occurs and no locks are placed. The new owner of the domain now has full control (including access to the authorization code) and can now have the domain transferred in to any other RAR (or they could sell the domain to another individual and provide them the auth code to complete a transfer).

Thank you for participating Richard *THUMBSUP*

Thanks Richard!

richard.schreier said:

There is no CIRA imposed lock if a domain name RANT is changed while the domain remains at the same RAR.

Click to expand...

Thanks Richard.

Yeah, this was the same issue that I had with Rebel a while back - where they also lock your domain after a registrant change. That one was initially said to be 60 days, then changed to 7 days. I just wanted to get an official statement of that. It just annoys me that a registrar can decide to make up their own rules and lock my name. I don't think a registrar should be allowed do that.

Unfortunately, their support people don't know enough about .ca domains and I just get canned but clearly wrong answers. If they want to lock it be default, fine, but if I request it to be unlocked they should do it. Its not like they don't know who I am, I've been a customer for as long as they've been in existence.

In the end, it's not a big deal - this time, just annoying.

richard.schreier said:

I'm not 100% sure but I think COM operates on the basis of a change in RANT as well and as a result many RARs have adopted a standard lock as part of their architecture.

Click to expand...

The main reason the registrant changes for a .COM transfer is that the registry is still a thin registry, and thus the registry does not hold any of the contact data. So any transfer to another registrar is technically also a change of the contacts on the domain.

Verisign was supposed (and had started) the transition to a "thick registry" (that would have held the contact data), but this transition was stopped due to GDPR.

The 60-day lock after Registrant changes is an ICANN requirement across gTLDs, but it's enforced by registrars, whereas the 60-day lock for new registrations is enforced by the registry:
https://www.icann.org/resources/pages/ownership-2013-05-03-en

ICANN said:

After 1 December 2016, registrars must impose a lock that will prevent any transfer to another registrar for sixty (60) days following a change to a registrant's information. Registrars may (but are not required to) allow registrants to opt out of the 60-day lock prior to the change of registrant request.

Click to expand...

I'm assuming that a ccTLD isn't strictly governed by ICANN policies for gTLDs, otherwise CIRA would have followed their lead across the board, but it seems CIRA has taken ICANN's policies as more of a compatibility guideline, clearly there is much good there to start with. But I'm glad CIRA didn't follow along 100%, as I think everyone appreciates the instant transfers we get from CIRA the best - we are quite spoiled in that way.

What is interesting with the two domains I purchased is that they aren't actually locked as per the whois results. I just get the following:

Domain Status: ok https://icann.org/epp#ok

Click to expand...

However, when I try to request an auth code, I get this message:

This domain was registered, transferred or underwent a change of registrant less than 60 days ago.

ICANN (the worldwide organization in charge of maintaining and coordinating domain names) doesn’t allow registrar transfers within 60 days of the these events:
New domain registration
Transfer between different registrars
Change to registrant contact information
You’ll be able to transfer this domain away on or after March 14, 2022.

Click to expand...

So they're not using the built in lock mechanism, they're just refusing to give me the auth code - and saying that it is ICANN mandated.

So [notify]FM[/notify] and [notify]richard.schreier[/notify], just what exactly is a CIRA certified registrar's obligation? To follow ICANN rules or CIRA's rules?

rlm said:

So [notify]FM[/notify] and [notify]richard.schreier[/notify], just what exactly is a CIRA certified registrar's obligation? To follow ICANN rules or CIRA's rules?

Click to expand...

CIRA has their own rules and obligations - as you already said, ccTLDs are not regulated by ICANN. ccTLDs are however part of the ICANN community and provide valuable input and may also partially decide to follow similar rules to ICANN rules.

Some registrars seem to apply ICANN rules across the board though. This may partially be related to the challenges of connecting to so many different TLDs with different rules, but of course, that doesn't relieve the registrar from following the ccTLD rules as well.

[notify]rlm[/notify] .CA Registrars are obligated to follow CIRAs rules per the registry agreement. The only clause related to the authorization code is Article 5 Registrar Obligations sub-clause (cc) which simply says:

"provide the Registrant with any and all information, materials, approvals, and authorization codes required to effect and/or facilitate a change of Registrar when requested by the Registrant;"

What you are getting is not uncommon where the logic implemented by the registrar is applied to all strings for ease of programming. We see similar issues with transfer protocols (and "ack"ing) which in CA do not exist, transfers are immediate. You need to contact your RARs support team and ask for the auth code on the phone, bypass the automatic response.

Thanks for the thorough answers guys. Appreciated.

[Rant mode On]
Ugh - man I hate godaddy. Today, a seller was pushing in 13 domains I purchased. Trying to accept those domains was a royal pain in the ass. Jumped through all the forms to assign contacts multiple times - always just got mysterious errors with no explanation, like where a form had greyed out boxes expecting you to fill in stuff despite the fact it was greyed out. After tricking the forms into allowing me to proceed by checking/unchecking certain boxes, I could at least get a "next" button to un-grey itself. Making it to the end of 13 domains (even though I selected the "apply to all" button), I get to the end and it just hamster wheels, eventually dies, and says call support. So while waiting on hold for 30 minutes, I try again, multiple times. Nothing works. Then I get support on the phone finally and they just tell me to do the same crap I already did, of course. After a couple more failures, she wants screen shots. After sending screen shots, she finally believes me that its not me. Then she wants screenshots from the email Godaddy sent to the old owner to prove that there was no button or link to approve the changes (which there wasn't, just a list of the domains that were being changed). I try again, no dice. Support person doesn't know what to do other than try again. So I try again, magically it works. As soon as she said "I now see the domains in your account" I heard dial tone. Well that was courteous! I would never ever purposely use GoDaddy to hold my .CA's.
[/Rant mode off]

I agree completely Rob.
And as I mentioned in another thread..GD still doesn’t get the RANT change right. I still get expiration notices for names I sold a year ago or many years ago, meaning I am still listed in some of the registrant info. Never have liked that. I move out of GD asap when I have purchased names from a seller there.