Revision as of 22:52, 14 November 2016

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.

Trademark Clearinghouse
Overview
Name	Trademark Clearinghouse
Acronym	TMCH
Document Downloads
Downloads	1) TMCH Guidelines 1.2 2) Declaration Forms for... Use Trademark Agents License Holders Marks Protected under Statute or Treaty Court Validated Trademarks Registered Trademarks (Transfer) Marks Protected under Statute or Treaty (Transfer) Court Validated Trademarks (Transfer)
Legal Documents
Agreements	TBA
Others	TBA

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.

What is a Designated Agent (DA) and Who Can Become One?

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.

How Does this Policy Affect Me?

I am a Direct Customer and not a Reseller

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:

1. If you are the old registrant only and you submit a material change of registrant through the Control Panel, an additional confirmation notice will be presented to you at the time of submission. You or your DA must confirm thechange of registrant as the old registrant. Additionally, you must also have explicit prior approval from the new registrant, effectively making you the DA of the new registrant. Therefore, submission without this prior approvalfrom the new registrant will automatically fail.
2. If you are the new registrant only (after a domain has been sold or transferred to you) and you submit a material change of registrant, an additional confirmation notice will be presented to you at submission. You or your DA must confirm the change of registrant as the new registrant. Also, if you have received explicit DA status from the old registrant, you can also confirm for the old registrant as well.
3. If you are both the old and new registrant, then you can provide confirmation for both registrants at the same time.
4. If you are a owner of a domain name (current registrant) for which a change of registrant submission has occurred, you may receive a change of registrant email. If you do not respond to this email within fourteen (14) days, the change of registrant request will expire and be cancelled.
5. Unless opt-ed out by the old registrant, a change of registrant will result in a sixty (60) day transfer lock when completed.
6. A material change of registrant for a domain contact handle involving one or more gTLD domain names will be reflected on the Control Panel only, but will not be submitted to the registry (whois data will not change).
7. If you receive a change of registrant confirmation email that you object to or were not expecting, please contact our support team immediately.

I am a Reseller

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:

1. Resellers must update their terms of service and registrant agreement to reflect the new IRTP before or on December 1, 2016.
2. Resellers must add additional terms to their registrant agreement allowing them to act as Designated Agents on behalf of their customers.
3. Resellers submitting material change of registrant requests as DA, upon request, shall provide verifiable documentation that they have obtained DA status from the respective registrant for a domain name.
4. Additonal affects on different types of resellers:

i. Control Panel Resellers with Sub-user Customers. Whenever your customer evokes a material change of registrant, an additional confirmation notice will be presented to the sub-user at submission in the Control Panel, as described above in the "I am a Direct Customer and not a Reseller, how does this Policy affect me?" section.

ii. Control Panel Resellers Only. You have obtained verifiable DA status from them to act on behalf of the registrant of a domain name. This will allow the reseller to submit a change of registrant request for their customer in the Control Panel.

iii.Module Resellers (WHMCS, AWBS, Plesk). You have obtained verifiable DA status to act on behalf of the new registrant of a domain name. Since the various module platforms have not updated in response to the IRTP, you are required to do the following:

• Login to the Control Panel and navigate to Manage Account > My Settings > Domain Settings. Under the "gTLD Inter-Registrar Transfer Policy" section first read the terms, implement the legal changes, and finally verify your Designated Agent status and your wish to alter the ModifyDomain command for IRTP compliance.
• Whenever your customer evokes a material change of registrant, the reseller must submit the change as the DA for the new registrant.::* The prior (old) registrant will always be sent a confirmation email, and they will have fourteen (14) days to confirm the change.
• The opt-out of the sixty (60) transfer lock is always enabled for module resellers.

iv.API Resellers. You have obtained verifiable DA status to act on behalf of the new registrant of a domain name. The registrant or the DA must have obtained prior approval to act on behalf of the new registrant, therefore, the reseller can then submit a TradeDomain command with the following three x-flag options:

• X-CONFIRM-DA-NEW-REGISTRANT = 1
• X-CONFIRM-DA-OLD-REGISTRANT = 0 or 1
• X-REQUEST-OPT-OUT-TRANSFERLOCK = 0 or 1

1. Your customers may receive a change of registrant confirmation email in which they will have fourteen (14) days to approve and complete the change of registrant. Failure to confirm a change of registrant within this time will invalidate the transaction.
2. A material change of registrant for a domain contact handle involving one or more gTLD domain names will be reflected on the Control Panel only, but will not be submitted to the registry (whois data will not change).
3. If your customers receive a change of registrant confirmation email that they were not expecting or have were not aware of, please contact our support team immediately.

I am a Registrar Operations Center Client (RegistrarOC)

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:

1. Registrars may want to update their terms of service and registrant agreement to reflect the new IRTP before or on December 1, 2016.
2. Registrars may want to add additional terms to their registrant agreement allowing them to act as Designated Agents on behalf of their customers.
3. Whenever your customer makes a material change of registrant to a domain name, first they must have obtained prior approval to act on behalf of the new registrant. Then a TradeDomain command can be submitted with the following three x-flags and options:
   • X-CONFIRM-DA-NEW-REGISTRANT = 1
   • X-CONFIRM-DA-OLD-REGISTRANT = 0 or 1
   • X-REQUEST-OPT-OUT-TRANSFERLOCK = 0 or 1
4. Your customers may receive a change of registrant confirmation email in which they will have fourteen (14) days to approve and complete the change of registrant. Failure to confirm a change of registrant within this time will invalidate the transaction.
5. A material change of registrant for a domain contact handle involving one or more gTLD domain names will be reflected on the Control Panel only, but will not be submitted to the registry (whois).
6. If your customers receive a change of registrant confirmation email that they were not expecting or were unaware of, please contact us immediately.

Frequently Asked Questions - General

What is a "Material Change of Registrant" and will even a small change, like correcting a typo, trigger the confirmation process?

The new ICANN transfer policy requires confirmation if there are any changes to the registrant:

• first name
• last name
• organization name
• email address
• administrative contact email address, only if there is no registrant email address

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.

Who can initiate a change of registrant?

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.

Who can confirm a change of registrant?

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.

What if I am both the old and the new registrant?

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.

What happens if either the old or new registrant denies confirmation?

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

What happens if the old registrant confirmation is not received within fourteen (14) days?

The change of registrant request will be denied and a brand new change of registration request will have to be initiated.

What happens if the new registrant does not have access to their email address?

If the new registrant has a problem with their email, then simply resubmit using a new email address for the new registrant.

What happens if the old registrant does not have access to their email address?

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.

What happens when a second change of registrant request is made before a prior one is yet to be completed?

The first request is cancelled.

After a change of registrant is completed, what happens?

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.


If I purchase a domain through the aftermarket or privately and the prior registrant does not approve the change of registrant what happens?

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.

Does this new transfer policy apply to country-code top-level domains (ccTLDs)?

No, it only applies to generic top-level domains (gTLDs) governed by ICANN.

How does this new policy affect domain names using WhoisTrustee privacy service?

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.

What happens if I change a contact handle that is bound to a gTLD domain name?

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.

API Documentation

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

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