From HEXONET Wiki
Line 10: | Line 10: | ||
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. | 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: | + | :Confirmation: |
− | :a. The old registrant or its respective designated agent confirms through a checkbox at the point of registrant change. | + | ::a. The old registrant or its respective designated agent confirms through a checkbox at the point of registrant change. |
− | :b. The new registrant or its respective designated agent confirms through a checkbox at the point of registrant change. | + | ::b. The new registrant or its respective designated agent confirms through a checkbox at the point of registrant change. |
− | :c. Old or new registrant or their respective designated agent can explicitly confirm through an email within fourteen (14) days sent by the registrar of record. | + | ::c. Old or new registrant or their respective designated agent can explicitly confirm through an email within fourteen (14) days sent by the registrar of record. |
==How does the New IRTP Work?== | ==How does the New IRTP Work?== | ||
Line 22: | Line 22: | ||
:c. The new registrant can also be a DA for the old registrant (typically obtained from prior registrant before transfer of a domain to new registrant's registrar). | :c. The new registrant can also be a DA for the old registrant (typically obtained from prior registrant before transfer of a domain to new registrant's registrar). | ||
+ | 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: | ||
− | + | :a. Can be requested by the old registrant or their respective DA at the time of change of registrant request. | |
+ | :b. Can be requested by the new registrant or their respective DA at the time of confirmation, however, this will trigger an email to the old registrant, who then must accept opting out of the transfer lock by providing a securely generated code. | ||
Revision as of 21:26, 14 November 2016
Contents |
What is the New Inter-Registrar Transfer Policy (IRTP)?
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.
How does the New IRTP Work?
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:
- a. The old registrant or its respective designated agent confirms through a checkbox at the point of registrant change.
- b. The new registrant or its respective designated agent confirms through a checkbox at the point of registrant change.
- c. Old or new registrant or their respective designated agent can explicitly confirm through an email within fourteen (14) days sent by the registrar of record.
How does the New IRTP Work?
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:
- a. The registrar of record can be a DA (may be requested or via updated Registrant Agreement) for either the old and/or new registrant.
- b. A reseller can be a DA (may be requested or via updated Registrant Agreement) for either the old and/or new registrant.
- c. The new registrant can also be a DA for the old registrant (typically obtained from prior registrant before transfer of a domain to new registrant's registrar).
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:
- a. Can be requested by the old registrant or their respective DA at the time of change of registrant request.
- b. Can be requested by the new registrant or their respective DA at the time of confirmation, however, this will trigger an email to the old registrant, who then must accept opting out of the transfer lock by providing a securely generated code.
ICANN has reviewed the policies that govern domain transfers in the gTLD and nTLD spaces and has come up with a new Transfer Policy which includes a new process: Registrant Transfer (Change of Registrant).
This new Transfer Policy will become effective December 1, 2016. A change of registrant have to be requested with a TradeDomain command.
Following new parameters are created:
Designated Agent (DA) of the new registrant: X-CONFIRM-DA-NEW-REGISTRANT = 1
Designated Agent (DA) of the old registrant: X-CONFIRM-DA-OLD-REGISTRANT = 0 | 1
TRADEDOMAIN
[COMMAND]
COMMAND = TradeDomain DOMAIN = <DOMAIN>
REQUIRED
OWNERCONTACT0 = <CONTACT> X-CONFIRM-DA-NEW-REGISTRANT = 1 X-CONFIRM-DA-OLD-REGISTRANT = 1
[RESPONSE]
DESCRIPTION = Command completed successfully; realtime domain trade succeeded CODE = 200
Information
The domain will locked for transfer for sixty (60) days after a successful execution of the TradeDomain command.
STATUSDOMAIN
[COMMAND]
COMMAND = StatusDomain DOMAIN = <DOMAIN>
[RESPONSE]
CODE = 200 DESCRIPTION = Command completed successfully PROPERTY[STATUS][0] = ACTIVE PROPERTY[STATUS][1] = clientTransferProhibited ... PROPERTY[CURRENT-REGISTRANT-NAME][0] = ... PROPERTY[CURRENT-REGISTRANT-ORGANIZATION][0] = ... PROPERTY[CURRENT-REGISTRANT-EMAIL][0] = ... ... PROPERTY[TRANSFERLOCK][0] = 1 PROPERTY[TRANSFERLOCK-EXPIRATIONDATE][0] = YYYY-MM-DD HH:MM:SS PROPERTY[TRADE-TRANSFERLOCK-EXPIRATIONDATE][0] = YYYY-MM-DD HH:MM:SS ...
MODIFYDOMAIN
A removal of the transferlock via a ModifyDomain command is not possible for sixty (60) days after a successful change of registrant without the OPT-OUT option.
[COMMAND]
COMMAND = ModifyDomain DOMAIN = <DOMAIN> ...
OPTIONAL
TRANSFERLOCK = 0
[RESPONSE]
CODE = 552 DESCRIPTION = Object status does not allow for operation; Change of Registrant TRANSFERLOCK in place until YYYY-MM-DD HH:MM:SS
TRADEDOMAIN with OPT-OUT
To avoid the sixty (60) day transferlock, you have the option to request the TradeDomain command with the additional parameter X-REQUEST-OPT-OUT-TRANSFERLOCK = 1. The activation of this parameter triggers an email. The old registrant will receive an email requesting the confirmation of the change of registrant. This email have to be approved within fourteen (14) days to complete the TRADE request and avoid the sixty (60) days transferlock.
[COMMAND]
COMMAND = TradeDomain DOMAIN = <DOMAIN>
REQUIRED
OWNERCONTACT0 = P-ABC123 X-CONFIRM-DA-NEW-REGISTRANT = 1 X-REQUEST-OPT-OUT-TRANSFERLOCK = 1
OPTIONAL
X-CONFIRM-DA-OLD-REGISTRANT = 0
[RESPONSE]
DESCRIPTION = Command completed successfully; trade pending - non-real-time CODE = 200 PENDING = 1