While you and I were sleeping (unaware) ICANN, for no particularly sound reason, has been discussing changes to the domain name transfer process that will remove a security measure - a step in the domain name transfer-away process - that currently allows a domain registrant to reject a transfer IF there is evidence that the domain transfer code was hijacked, i.e., intercepted and used by a thief to steal the domain.
The evidence of theft and/or deception would be evidence that the domain is being transferred to a domain registrar that is not the registrar the current domain registrant was advised that his / her buyer intended to transfer the domain name to.
Confirming the destination or "agreed recipient registrar" is the one that has deployed the transfer code IS a step - asking my domain registrar to confirm the destination registrar BEFORE putting through the transfer - that I routinely employ. It offers additional assurance that everything is proceeding as agreed - in the often difficult to trace world of digital transactions.
George Kirikos has been doing a superb job in representing the interests of domain holders by providing information and insights to the ICANN body responsible for deciding whether to make this change. Here's his latest article, summarizing his actions and insights:
[
freespeech.com ] (registrars-continue-to-threaten-to-weaken-domain-name-transfer-security)
I would urge anyone who has an interest - direct or as an agency - in protecting domain names to make you thoughts and concerns known.
