Stop “Call In” Practice by March — Register.com Must
Transfer authorization code process will be easier under fresh ICANN policy.
Under ICANN’s fresh Policy on Transfer of Registrations between Registrars, which goes into effect March 15, Register.com will no longer be able to require clients to call the firm to request transfer authorization codes. These codes are used to transfer domains to a different domain registrar. (See Register.com’s Client Service Lie)
The policy states “Registrars may not employ any mechanism for complying with a Registered Name Holder’s request to obtain the applicable “AuthInfo Code” that is more restrictive than the mechanisms used for changing any aspect of the Registered Name Holder’s contact or name server information.”
In other words, if a registrar allows clients to change contact information or name server information online, it must allow them to request and receive transfer authorization codes online.
I could see a registrar trying to require a call to change the registered name holder’s contact information under the guise of security. But the policy states “OR” name server information, so unless a registrar requires clients to call in to change name servers, they will have a difficult time finding a loophole in this provision. Register.com is the only major registrar I know of that forces its clients to call to get a transfer code. Smaller registrars — counting many of those participating in expired domain sites — sometimes have arduous procedures as well.
