: Behaviour of domains when transferred, that do not use auth codes I am currently working on a feature for an existing project that enables the user to initiate a transfer out of domains. As

@Si4351233

Posted in: #Dns #Domains #DomainTransfer

I am currently working on a feature for an existing project that enables the user to initiate a transfer out of domains. As stated by this Google Spreadsheet, which is I hope somewhat correct, most TLDs do in fact use auth codes. The API I am working with has a property in the domain object called TransferLockEnabled. This is a non-required property when working with a domain and controls, as semantically obvious, if a domain can be transferred or not.

So at the moment I can easily set this to false which in the response object provides me with an auth code. So for domains that use an auth code it works just fine.

Problem is, if a TLD doesn't use auth codes, for example .uk, I am not aware of what happens in the backend. To my little knowledge it triggers an email being sent to either the admin or the owner handle of the domain (or both).

I am somewhat familiar with the domain name system, but not much more than any other web developer, so I'd appreciate any help.

How do domains, that don't use an auth code, behave when initiating a transfer out. Does someone just start a transfer in and that triggers an email, etc., being sent? How does it differ from other domains?

Vote Up Vote Down

Login to post a comment!