Starting December 1, 2016, ICANN's new transfer policy modifies the way registrant information can be changed for gTLD domain names. The new policy affects resellers, registrars, and service providers who sell gTLD domain names, as well as all domain name owners (registrants). This page and subsequent email provide full notice of the impending policy changes.
The Inter-Registrar Transfer Policy (IRTP) governs domain name transfers between ICANN registrars. The new provisions in the IRTP now specifically include changes to domain ownership (changes to the registrant). This means that any time a material change to a domain name's registrant first name, last name, or email address occurs, a sequence of confirmations, approvals, and possibly emails are now required for registrant information to be modified. Please keep in mind that now even small changes to a domain name's registrant first name, last name, organization, and email address may trigger the validation process. This new policy takes effect on December 1, 2016.
Whenever there is a material change to a domain name's registrant first name, last name, or email address, as well as, in some cases, administrative contact email (if there is no registrant email), confirmation must be provided by both the old registrant entity and the new registrant entity or a designated agent for the respective old or new registrant. Failure to provide confirmation from either party will cancel the change of registrant and all registrant information will remain that of the prior registrant.
Confirmation:
Registrants (old or new) can explicitly authorize an individual or entity to approve a change of registrant on their behalf. Though anyone or any entity can be a DA, explicit and verifiable authorization must be given. In practical terms, here are examples of a DA:
Other Confirmations, Locks, and Notifications
Once the registrant change has been completed successfully, both the old and new registrants are sent an email notice to confirm the changes. Additionally, the domain is locked and transferring to another registrar is not allowed for sixty (60) days in order to protect against domain theft. However, opting out of the sixty (60) day lock is possible:
This new policy takes effect on December 1, 2016
New Transfer Policy Timeline
Starting December 1, 2016, it will no longer be possible to change the registrant of a domain name with a simple domain modification request. When making a material change to the registrant of a domain name, the following will occur:
Starting December 1, 2016, it will no longer be possible for your customers to change the registrant of a domain name with a simple domain modification request. Depending on your reseller platform and how you are connected to us, you must implement the following:
Starting December 1, 2016, it will no longer be possible for your customers to change the registrant of a domain name with a simple domain modification request. As a Registrar Operations Center client, please be aware of the following changes to the platform:
A.The new ICANN transfer policy requires confirmation if there are any changes to the registrant:
Any change, even small changes, may require the confirmation process to take effect. Keep in mind that small changes likely mean that the old registrant and the new registrant are the same individual (entity), therefore, confirmation checks can be provided directly at the point of submission, as well as opting out of the sixty (60) day lock.
A. There are four entities that can submit a change of registrant. Either the old or new registrant can initiate the process through their respective registrars. Additionally, designated agents for either the old or new registrants can also initiate the change of registrant process on behalf of their registrant customer.
A. Both the old and new registrant must confirm. Designated agents for either the old or new registrants can also confirm on behalf of their respective registrant customer.
A. Both the old and new registrant must confirm, therefore, the one registrant can confirm for both. This will bypass the confirmation email process and automatically complete the change of registrant. Opting-out of the post sixty (60) day transfer lock at submission is recommended for this scenario, which will trigger an email to the old registrant email.
A. A: If the old registrant does not confirm the change of registrant within fourteen (14) days, the domain name registrant information (whois data) will remain the same, that of the old registrant. The new registrant (or their DA) must always give confirmation, which is obtained by the old registrant or their DA beforehand or automatically provided by the new registrant's DA at submission
A. The change of registrant request will be denied and a brand new change of registration request will have to be initiated.
A.If the new registrant has a problem with their email, then simply resubmit using a new email address for the new registrant.
A. If the old registrant's email is not working, then the old registrant or a designated agent of the old registrant needs to change the old email address first. As both the old and new registrant (or DA), please confirm for both and most importantly, DO NOT opt-out of the sixty (60) day transfer lock (conversely opting-out would trigger a transfer opt-out email to the old non-working email that can't be confirmed). Again, please note that after this change of registrant to a working email address, the domain name will be locked for sixty (60) days before it can be transferred to a new registrar.
A. The first request is cancelled.
A. Both the old and new registrant are notified by email that the change of the registrant has completed. A sixty (60) day transfer lock is applied unless it is opted-out by the old registrant at the time of submission or confirmed through a separate opt-out email.
A. Contact the aftermarket provider in case of such problems. However, for private domain purchases, you can ask for explicit approval from the old registrant that either you or your registrar be the old registrant's designated agent. This explicit and verifiable assignment as the designated agent of the old registrant will allow you or your registrar to confirm on behalf of the old registrant at the point of change of registrant submission.
A. No, it only applies to generic top-level domains (gTLDs) governed by ICANN.
A. Any domain using WhoisTrustee will only be affected if the underlying escrowed registrant data has a material change. Turning on or off privacy services does not change the registrant and therefore does not constitute a material change.
A. Any contact handle used by a gTLD domain name can be updated and changed locally. The changes are only on the local system and will not be submitted to the registry for registrant contacts. Domains from now on be individually modified through a change of registrant specifically for a single domain name.
A.There are alternate ways for obtaining verifiable DA status from your customers. The one universal way we ask of our resellers and registrars is you update your terms of service and registrant agreement to reflect the new IRTP on or before December 1, 2016. The additional terms you are required to add will allow you (reseller or registrar) to act as Designated Agents on behalf of your customers. Also, recorded proof that you sent out notice to your customers of the changes to your registrant agreement is highly recommended.