ICANN OwnerChange

From TLDinfo
Jump to: navigation, search

Contents

ICANN Policy Changes for OwnerChanges

ICANN has announced the implementation of amendments to the Inter-Registrar Transfer Policy (IRTP), which is being renamed as the "Transfer Policy." In addition to rules related to inter-registrar transfers, the updated Transfer Policy now sets policy requirements for transfers between registrants, also described as OwnerChanges. It will also impose new conditions for the expiration of the Form of Authorization (FOA) used by registrars in inter-registrar transfers.

The amended Transfer Policy is applicable to all generic top-level domains (gTLDs) and ICANN-accredited registrars. CcTLDs are not affected.

These new requirements will take effect and will be enforced by ICANN beginning on December 1, 2016.

A redline version of the policy showing changes can be found here.
An updated version of the Transfer Policy can be found here.

The official ICANN announcement can be found here.


Definition of OwnerChange

Since the ICANN Transfer Policy also carries the name Inter-Registrar Transfer Policy (IRTP) and covers transfers from one registrar to another as well as transfers from one registrant to another, we decided to label the latter as OwnerChange, making it easier to comprehend. Both descriptions, OwnerChange and IRTP can occur, but we try to use only OwnerChange.

Within this context, an OwnerChange is a change to relevant fields of an OwnerContact handle.

The following fields are relevant for an OwnerChange:

  • firstname
  • middlename
  • lastname
  • organization
  • email

All other fields of an OwnerContact handle can be updated as usual using the ModifyDomain command, for example the address or telephone number. It will not trigger a confirmation mail.

FOA Mode or Designated Agent Mode

For RRPproxy Resellers the policy changes for gTLD OwnerChanges are implemented in two different variants. The default implementation will use a FOA (Form Of Authorisation) confirmation process, where both the old and the new domain owner receive a separate mail and need to confirm the OwnerChange. We're also referring to this method as the FOA Mode and it is set as default for all RRPproxy Resellers.

Aside from the default FOA Mode RRPproxy Resellers will also be able to opt for the optional Designated Agent Mode. With this mode, changes to the relevant registrant whois data elements Name, Organisation and E-Mail will be processed instantaneously. In effect, no technical changes apply at reseller and registrant level and adopting the new policy is very easy for RRPproxy Resellers. However, it is required that the Registration Agreement of Key-Systems is passed on to registrants, in order to opt for the Designated Agent Mode.


Information on FOA Mode

The default FOA Mode introduces a FOA (Form Of Authorisation) confirmation process, where both the old and the new domain owner need to confirm the owner change. This process can be compared with the FOA confirmation process that applies for gTLD transfers.

In general, the new policy requirements include the following:

  1. "Change of Registrant" and "OwnerChange" are now defined terms, meaning a material change to the registrant's name, organization or email address, or the administrative contact's email address if there is no registrant email address.
  2. Registrars must use a secure mechanism to confirm that both the prior registrant and new registrant have consented to any Change of Registrant.
  3. Registrars must notify the prior registrant and new registrant of a Change of Registrant and provide the notice described in the policy which includes, for example, an explanation of the request, information on how to approve of cancel the change of registrant, etc.
  4. Registrars must process the Change of Registrant within one (1) day of receiving the confirmation of Change of Registrant from the prior registrant and the new registrant.
  5. Registrars must impose a 60-day inter-registrar transfer lock following a Change of Registrant but registrars may allow registered name holders to opt out of the lock prior to any Change of Registrant request.
  6. The Form of Authorization used by gaining registrars, labeled "Initial Authorization for Registrar Transfer" shall expire under the following circumstances:
    • A period of 60 days has passed since the FOA was sent by the gaining registrar (unless the registrar allows automatic renewal of FOAs).
    • The domain name expires before the transfer is completed.
    • A Change of Registrant is completed.
    • The inter-registrar transfer is completed.


Information on Designated Agent Mode

The new ICANN transfer policy authorises Designated Agents of the old and new registrants to confirm and perform requested changes and to receive the notification regarding the transfer lock resulting from the modification. We have therefore included paragraph 1.9 in our Registration Agreement that explicitly designates Key-Systems and our Resellers as Designated Agents of the old registrant and (in accordance with section 1.7) the new registrant, thereby authorising us to immediately confirm requested owner changes.

Reseller must include the Registration Agreement of Key-Systems in its own terms of service or business processes to ensure that both old and new registrants have explicitly designated Reseller and Key-Systems as Designated Agents in accordance with ICANN policy. At the time they accept an update request, Resellers must also inform their customers that an update of the ownership data will result in a 60-day transfer lock (II.C.1.1.3 of the ICANN transfer policy).

If this optional Designated Agent process is activated by Reseller in the RRPproxy web interface, Key-Systems and Reseller will act as explicitly authorised Designated Agents of both the old and new registrant. This process replaces the FOA process and thus the requirement to obtain the confirmation from both the old and new registrant prior to executing the update.

Updates to the registrant whois information authorised by Key-Systems or Reseller as Designated Agents will always result in a lock of the affected domain names against transfers for 60 days, as only the old registered name holder at the time of the request can opt out of this lock. To allow the old registrant to opt out, the FOA confirmation process must be used, which can be activated for individual modification requests by sending the appropriate API parameter when initiating the modify request.


Integrate the New Policy

  • The first and most important step is to make sure you include the Registration Agreement of Key-Systems in your terms and conditions or business processes. This document needs to be available to all your new and existing customers whenever they submit a domain-related request.
  • Make yourself familiar with the new workflows, especially if you're using our API and/or the FOA Mode to handle OwnerChanges as of December 1st 2016.
  • Make sure the new processes will be integrated in your business logic properly. Please let us know if you need information on any issue that might arise.
  • Choose an option, how to handle requests for OwnerChanges: Using the FOA Mode (default), or using the Designated Agent Mode.

As of December 1st 2016 the new ICANN OwnerChange policy will take effect and will be enforced by ICANN.


Testing in OT&E

The new FOA Mode is available for testing in our OT&E. Please be aware, that when testing the OwnerChanges in our OT&E, OwnerChange FOA emails will be sent to the reseller email address stated for your OT&E account instead of the registrant email address.


Contact Verification

An OwnerChange approve or reject verifies the contact automatically (Skips Contact Verification Mail).

Reseller Settings

The Reseller Settings for ICANN OwnerChanges can be found in the RRProxy Web Interface at "Account" -> "Settings" -> tab "ICANN Transfer".

  • ICANNTRANSFER-ownerchange-mode
Choose between FOA Mode (default) and Designated Agent Mode.
  • ICANNTRANSFER-ownerchange-transferlock-override
Registrant can opt-out the transfer lock (Yes=1|No=0).
Only applicable if FOA Mode is selected.
  • ICANNTRANSFER-ownerchange-emailsender
Sets the FROM address of the ICANN-OwnerChange email. Default: noreply@emailverification.info
  • ICANNTRANSFER-ownerchange-emailsubject
Sets the SUBJECT of the ICANN-OwnerChange email. Default: ICANN inter-registrant transfer
  • ICANNTRANSFER-ownerchange-confirmationlink
Sets the confirmation link which is displayed in the ICANN-OwnerChange email. Default: https://icann-transfers.key-systems.net/
  • ICANNTRANSFER-ownerchange-infopagelink
Sets the info page link which is displayed in the ICANN-OwnerChange email. Default: https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en#II.A
  • ICANNTRANSFER-ownerchange-freetext0 .. 2
Sets the freetext which is displayed in the ICANN-OwnerChange email


Example API Command for Reseller Settings:

 [COMMAND]
 command=setproperty
 ICANNTRANSFER-ownerchange-mode = FOA|DESIGNATED_AGENT
 ICANNTRANSFER-ownerchange-transferlock = 0|1
 ICANNTRANSFER-ownerchange-transferlock-override = 0|1
 ICANNTRANSFER-ownerchange-emailsender = noreply@emailverification.info
 ICANNTRANSFER-ownerchange-emailsubject = ICANN inter-registrant transfer
 ICANNTRANSFER-ownerchange-confirmationlink = https://icann-transfers.key-systems.net/
 ICANNTRANSFER-ownerchange-infopagelink = https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en#II.A
 ICANNTRANSFER-ownerchange-freetext0..2 =
 ICANNTRANSFER-ownerchange-footer0..2 = Your ICANN accredited registrar
 EOF

Enabling the Designated Agent Mode for your RRPproxy Reseller account

When enabling this option you confirm that:

  • By initiating an order through Key-Systems and/or by executing electronic actions the customer declares that he has the proper authority to place orders either for himself or as properly authorised representative of his organisation and that he agrees to the terms and conditions, contractual terms and registration agreements in all parts.
  • You have included the Registration Agreement of Key-Systems in your own terms of service or business processes to ensure that both old and new registrants have explicitly designated you and Key-Systems as Designated Agents in accordance with ICANN policy.
  • You will request Domain Registrations, Transfers and OwnerChanges on behalf of your clients only after the respective registrant(s) have agreed to the Registration Agreement of Key-Systems and thus designated you and Key-Systems as Designated Agents in accordance with ICANN policy.
  • Upon request, you are able to present proof that a registrant of a specific domain has agreed to your terms and conditions that include the Registration Agreement of Key-Systems. Examples for proofs are a log including timestamp (time, date, domain, registrant contact details, registrant IP address), a copy of a written and signed contract, or a screenshot of an agreement including its confirmation (including time, date, domain, registrant contact details, registrant IP address, date/time of confirmation). These proofs can be requested by us if ICANN is requesting them during an audit.

After confirming these points all current and future domains of your registrants in your RRPproxy Reseller account will be managed with you and Key-Systems as their Designated Agent for ICANN OwnerChanges.

For further information on TAC and Registration Agreement, please refer to our FAQ: How can I make sure my clients and registrants can agree to the Registration Agreement of Key-Systems?


OwnerChange Procedures in FOA Mode

These procedures outline the technical OwnerChange process in FOA Mode.

  1. Request OwnerChange via ModifyDomain.
  2. Send FOA Mail to Registrant.
  3. Registrants approve OwnerChange via Link. The option for the Old Registrant to opt out of the 60-day transferlock will be displayed on the website, if applicable.
  4. Send DOMAIN_MODIFICATION::MODIFICATION_SUCCESSFUL event to Reseller.
  5. Send Confirmation Mail to Old and New Registrant.


Old and new registrant approve OwnerChange

   Old Registrant      New Registrant            Reseller                   RRPProxy               Registry
---------------------------------------------------------------------------------------------------------------

1. Request OwnerChange ------------------------> ModifyDomain ------------> ModifyDomain

2. FOA-Mail <-------------------------------------------------------------- Send FOA

3.                     FOA-Mail <------------------------------------------ Send FOA
 
4. Approve OwnerChange ------------------------> Website -----------------> ActivateOwnerChange

5.                     Approve OwnerChange ----> Website -----------------> ActivateOwnerChange

6.                                                                          Finish OwnerChange --> ModifyDomain

7.                                               MODIFICATION_SUCCESSFUL <- Create Event

Old or new registrant deny OwnerChange

   Old Registrant      New Registrant            Reseller                RRPProxy               Registry
-------------------------------------------------------------------------------------------------------------

1. Request OwnerChange ------------------------> ModifyDomain ---------> ModifyDomain

2. FOA-Mail <----------------------------------------------------------- Send FOA

3.                     FOA-Mail <--------------------------------------- Send FOA

4a. Deny OwnerChange --------------------------> Website --------------> ActivateOwnerChange
--- or ---
4b.                    Deny OwnerChange ------>  Website --------------> ActivateOwnerChange

5.                                               MODIFICATION_FAILED <-- Reject OwnerChange


OwnerChange expires after 14 days

   Old Registrant      New Registrant            Reseller                RRPProxy               Registry
-------------------------------------------------------------------------------------------------------------

1. Request OwnerChange ------------------------> ModifyDomain ---------> ModifyDomain

2. FOA-Mail <----------------------------------------------------------- Send FOA

3.                     FOA-Mail <--------------------------------------- Send FOA

4.                                               MODIFICATION_FAILED <-- Reject OwnerChange


A second OwnerChange cancels the first OwnerChange request

   Old Registrant      New Registrant            Reseller                RRPProxy               Registry
-------------------------------------------------------------------------------------------------------------

1. Request OwnerChange ------------------------> ModifyDomain ---------> ModifyDomain

2. FOA-Mail <----------------------------------------------------------- Send FOA

3.                     FOA-Mail <--------------------------------------- Send FOA

4.                     Request OwnerChange ----> ModifyDomain ---------> ModifyDomain

5.                                               MODIFICATION_FAILED <-- Cancel first Request

6. FOA-Mail <----------------------------------------------------------- Send new FOA

7.                     FOA-Mail <--------------------------------------- Send new FOA


Bulk OwnerChange FOA-Bundle

When the first request for a OwnerChange is received the FOA is sent immediately. On the second request within 5 minutes the FOA send waiting if other requests follow. If no requests received for 5 minutes all request send to registrant in one bulk FOA Mail.

   Old Registrant      New Registrant            Reseller                RRPProxy               Registry
-------------------------------------------------------------------------------------------------------------

1. 1st Request OwnerChange --------------------> ModifyDomain ---------> ModifyDomain

2. FOA-Mail <----------------------------------------------------------- Send FOA Request 1

3.                     FOA-Mail <--------------------------------------- Send FOA Request 1

4. 2nd Request OwnerChange --------------------> ModifyDomain ---------> ModifyDomain

5. 3rd Request OwnerChange --------------------> ModifyDomain ---------> ModifyDomain

6. nth Request OwnerChange --------------------> ModifyDomain ---------> ModifyDomain

7.  FOA-Mail <---------------------------------------------------------- Send Bulk FOA Request 2-n

8.                     FOA-Mail <--------------------------------------- Send Bulk FOA Request 2-n

... ...                ...                                               ... 


Old and New Registrant email address are the same

   Old Registrant      New Registrant            Reseller                   RRPProxy               Registry
---------------------------------------------------------------------------------------------------------------

1. Request OwnerChange ------------------------> ModifyDomain ------------> ModifyDomain

2. FOA-Mail <-------------------------------------------------------------- Send FOA

3. Approve OwnerChange ------------------------> Website -----------------> ActivateOwnerChange

4.                                                                          Finish OwnerChange --> ModifyDomain

5.                                               MODIFICATION_SUCCESSFUL <- Create Event

OwnerChange Procedures in Designated Agent Mode

This procedure outlines the technical OwnerChange process in Designated Agent Mode.

  1. Request OwnerChange via ModifyDomain.
  2. As long as Key-Systems and Reseller act as Designated Agent for both, Old and New Registrant, modifications are carried out instantly.
    1. Otherwise: Use parameter TriggerFOA=1 and send FOA EMail to Old/New Registrant.
    2. Registrant approves owner change via Link.
  3. Send DOMAIN_MODIFICATION::MODIFICATION_SUCCESSFUL event to reseller.
  4. Send information mail to Old and New Registrant.

Compared to the FOA Mode, the workflow is significantly simpler in Designated Agent Mode, as all modifications and thus the OwnerChange is automatically approved.

OwnerChange Request, Key-Systems and Reseller act as Designated Agent for both, Old and New Registrant

   Old Registrant      New Registrant            Registrar                  RRPProxy               Registry
---------------------------------------------------------------------------------------------------------------

1. Request OwnerChange ------------------------> ModifyDomain ------------> ModifyDomain

2.                                                                          Finish OwnerChange --> ModifyDomain

3.                                               MODIFICATION_SUCCESSFUL <- Create Event

4.  Information Mail <------------------------------------------------- Send Confirmation Mail

5.                    Information Mail <------------------------------- Send Confirmation Mail

TransferLock Removal for losing registrant

This feature needs to be enabled by SetProperty / ICANNTRANSFER-OWNERCHANGE-REMOVE-TRANSFERLOCK = 1. It adds a link to the Designated Agent confirmation email, which enables the losing registrant, to remove the transfer lock and to skip the 60 day transfer lock phase.

Metaregistry API Examples

In general, all commands can apply both for the default FOA Mode as well as for the Designated Agent Mode. However, in Designated Agent Mode and as long as both Old and New Registrant have explicitly designated Key-Systems and you as our Reseller as Designated Agents, all OwnerChanges will be carried out immediately.

In Designated Agent Mode it is possible to override the Designated Agent Mode for single OwnerChanges and to apply the FOA Mode.


ModifyDomain

To initate an OwnerChange.

[COMMAND]
command = ModifyDomain
domain = example.com
ownercontact0 = P-ABC2
TriggerFOA = 0|1      <---- Optional. Triggers sending of FOA Mail, even in Designated Agent Mode.
EOF
[RESPONSE]
code = 200
description = Command completed successfully; OwnerChange pending confirmation
property[ownerchange status][0] = REQUESTED
EOF
  • TRIGGERFOA = 1 forces the system to send FOA mails, even if the reseller account uses the Designated Agent Mode
  • TRIGGERDA = 1 forces the system to use the designated agent mode for the relevant operation, even if the reseller account uses FOA Mode. This setting needs to be enabled within the reseller properties (Account --> Settings --> ICANN Transfer).

CheckOnly

Precheck for material changes

  • The CHECKONLY=1 parameter can be used to check if a change of the owner contact is a material change and the FOA process is mandatory, without performing any changes to the domain.
[COMMAND]
command = ModifyDomain
domain = example.tld
ownercontact0 = P-ABC1
checkonly = 1
EOF
  • Response on material change:
[RESPONSE]
code = 200
description = Command completed successfully; Check only
property[ownerchange status][0] = REQUESTED
EOF
  • Response on non-material change:
[RESPONSE]
code = 200
description = Command completed successfully; Check only
EOF

ActivateOwnerChange

ActivateOwnerChange is used to finish an OwnerChange using the respective "action" parameter.

Approve: To approve an OwnerChange request.
Deny: To reject an OwnerChange request.
Cancel: To cancel a pending OwnerChange request.
  • Approve OwnerChange request. Only works with respective trigger code. Transferlock can be set optionally.
[COMMAND]
command = ActivateOwnerChange
action = APPROVE
trigger = 1234567890
transferlock = 1
EOF


  • Reject OwnerChange request. Only works with respective trigger code.
[COMMAND]
command = ActivateOwnerChange
action = DENY
trigger = 1234567890
EOF


  • Cancel OwnerChange request. Only works with respective domain name.
[COMMAND]
command = ActivateOwnerChange
domain = example.com
action = CANCEL
EOF


StatusDomain

StatusDomains responses now additionally show information of a pending OwnerChange.

OwnerChange status values
  • REQUESTED - OwnerChange is requested but none has been confirmed
  • LOSING_APPROVED - The losing registrant has approved
  • GAINING_APPROVED - The gaining registrant has approved
[RESPONSE]
code = 200
description = Command completed successfully
property[domain][0] = example.com
...
property[status][0] = pendingUpdate
property[ownerchange status][0] = REQUESTED
EOF


QueryOwnerChangeList

Gives you an overview about all pending OwnerChanges.

[COMMAND]
command = QueryOwnerChangeList
EOF
[RESPONSE]
code = 200
description = Command completed successfully
property[column][0] = domain
property[column][1] = status
property[column][2] = requested date
property[column][3] = expire date
property[column][4] = losing registrant
property[column][5] = gaining registrant
property[domain][n] = example.com
property[status][n] = REQUESTED
property[requested date][n] = 2000-01-01 00:00:00
property[expire date][n] = 2000-01-15 00:00:00
property[losing registrant][n] = P-ABC1
property[gaining registrant][n] = P-ABC2
...

StatusOwnerChange

To explicitly check the status of an OwnerChange in detail.

[COMMAND]
command = StatusOwnerChange
domain = example.com
EOF
[RESPONSE]
code = 200
description = Command completed successfully
property[domain][0] = example.com
property[status][0] = REQUESTED
property[requested date][0] = 2000-01-01 00:00:00
property[expire date][0] = 2000-01-15 00:00:00
property[losing registrant][0] = P-ABC1
property[gaining registrant][0] = P-ABC2
EOF


ModifyContact

  • Material change with modify contact
[COMMAND]
command = ModifyContact
contact = P-ABC1
firstname = Max
lastname = Mustermann
organization = Example Inc
email = mail@example.com
EOF
[RESPONSE]
code = 200
description = Command completed successfully
property[ownerchange status][0] = REQUESTED
  • For handles which are linked as owner with a GTLD, "ownerchange status = REQUESTED" is returned, indicating that the IRTP process is started. This will happen, if at least one 'material' field is modified. Non material changes can still be done without triggering the IRTP process.

ModifyContact checkonly

MATERIAL CHANGE:

[COMMAND]
command=ModifyContact
contact=P-ABC1
email=notverified21@ks.de
checkonly=1
EOF
[RESPONSE]
code = 200
description = Command completed successfully; Check only
runtime = 0.028
queuetime = 0
property[ownerchange status][0] = REQUESTED
property[validated][0] = 1

NO MATERIAL CHANGE:

[COMMAND]
command=ModifyContact
contact=P-ABC1
email=notverified22@ks.de
checkonly=1
EOF
[RESPONSE]
code = 200
description = Command completed successfully; Check only
runtime = 0.028
queuetime = 0
property[validated][0] = 1

StatusContact

  • StatusContact also returns the current ownerchange status.
[COMMAND]
command = StatusContact
contact = P-ABC1
EOF
[RESPONSE]
code = 200
description = Command completed successfully
runtime = 0.008
...
property[ownerchange status][0] = REQUESTED|LOSING_APPROVED|GAINING_APPROVED
EOF

ResendNotification

  • Resend the ICANN OwnerChange FOA Mail to losing, gaining or both owner contacts
[COMMAND]
command = ResendNotification
type = OwnerChange
object = example.com | P-ABC1
recipient = losing|gaining|both
EOF

The resubmission of the email through the web interface will soon be available.

Resend DA email

With this feature, the reseller can resend the designated agent email by himself.

Attention.png This can trigger several emails, for example, if there were several IRTP changes for one domain-/contactobject.


Events

Trade Domain Failed (DOMAIN_MODIFICATION::MODIFICATION_FAILED)

[RESPONSE]
code = 200
description = Command completed successfully
property[date][0] = 2016-11-28 14:25:31.0
property[class][0] = DOMAIN_MODIFICATION
property[subclass][0] = MODIFICATION_FAILED
property[object id][0] = testdomain.com
property[data][0] = domain:testdomain.com
property[data][1] = jobid:7331577
property[data][2] = cltrid:9F9F44A4-94E8-4A1D-87A3-C4162D4C6883
property[data][3] = svtrid:F458F82E-4169-41C9-ACBF-408AAF7D8102
property[data][4] = ownerchange_status:gaining_denied|losing_denied|gaining, losing denied|user cancelled|expired
property[data][5] = reason:ownerchange failed
property[data][6] = gaining_registrant:P-ABC2
property[data][7] = losing_registrant:P-ABC1
property[data][8] = domain:testdomain.com
property[info][0] = ownerchange%20failed
EOF
  • OwnerChange status values: gaining_denied|losing_denied|gaining, losing denied|user cancelled|expired


Trade Domain Success (DOMAIN_MODIFICATION::MODIFICATION_SUCCESSFUL)

[RESPONSE]
code = 200
description = Command completed successfully
property[date][0] = 2016-11-18 16:32:41.0
property[class][0] = DOMAIN_MODIFICATION
property[subclass][0] = MODIFICATION_SUCCESS
property[object id][0] = testdomain.com
property[data][0] = domain:testdomain.com
property[data][1] = jobid:524526142
property[data][2] = cltrid:EE9B83F4-7A68-4256-843D-1A6CBA266995
property[data][3] = svtrid:32DD089F-2D8C-4A67-9FEC-87AC6F5C4B1F
property[data][4] = domain:test12342342.com
property[data][5] = gaining_registrant:P-ABC2
property[data][6] = ownerchange_status:successful
property[data][7] = losing_registrant:P-ABC1
property[data][8] = reason:ownerchange successful
property[info][0] = ownerchange%20successful
EOF

Trade Contact Failed (CONTACT_MODIFICATION::MODIFICATION_FAILED)

[RESPONSE]
code = 200
description = Command completed successfully
property[date][0] = 2016-11-25 12:14:00.0
property[class][0] = CONTACT_MODIFICATION
property[subclass][0] = MODIFICATION_FAILED
property[object id][0] = P-ABC2
property[data][0] = contact:P-ABC2
property[data][1] = jobid:524526367
property[data][2] = cltrid:05B4522D-7C7E-4552-9EA8-1E083A8F8690
property[data][3] = svtrid:0CFEC847-475F-4043-83B9-6601917D9C0C
property[data][4] = gaining_registrant:P-ABC2
property[data][5] = ownerchange_status:registry operation failed|gaining_denied|losing_denied|gaining, losing denied|user cancelled|expired
property[data][6] = reason:ownerchange failed: 531 Authorization failed
property[info][0] = ownerchange%20failed%3a%20531%20Authorization%20failed
EOF

Trade Contact Success (CONTACT_MODIFICATION::MODIFICATION_SUCCESSFUL)

[RESPONSE]
code = 200
description = Command completed successfully
property[date][0] = 2016-11-24 15:03:34.0
property[class][0] = CONTACT_MODIFICATION
property[subclass][0] = MODIFICATION_SUCCESS
property[object id][0] = P-ABC2
property[data][0] = contact:P-ABC2
property[data][1] = jobid:524526284
property[data][2] = cltrid:1EE66338-4F10-427A-B1A7-78DD25594300
property[data][3] = svtrid:63F2FBFC-263E-48F2-A687-6350EE82CB61
property[data][4] = ownerchange_status:successful
property[data][5] = gaining_registrant:P-ABC2
property[data][6] = reason:ownerchange successful
property[info][0] = ownerchange%20successful
EOF

Mail Templates

Below are our default mail templates used for the ICANN OwnerChange procedure. The FOA Mail is sent to the Old and New Registrant for confirmation and requires that either FOA Mode is activated, or the parameter TriggerFOA = 0|1 is used for a particular OwnerChange in Designated Agent Mode. Minor customizations (e.g. email sender address, three free text fields) can be done through the account settings.

In addition, it is possible to implement your completely customized template in our system. We charge a one time fee per template. The template is checked by us for compliance with the ICANN guidelines. Please contact our support team if interested in this service.


FOA Mail

From: [%EMAILSENDER%]
Subject: [%EMAILSUBJECT%]
Type: text/plain
charset: UTF-8
Encoding: 8bit

Dear registrant of [%IF DOMAIN%][%DOMAIN%][%ELSE%](please see full list of names at the end of this email)[%END%],

In accordance with the Section II of the ICANN Inter-Registrar Transfer policy (see [https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en]) we kindly ask you for your cooperation to allow/deny the following changes:

Requested changes to be made to the registered domain holder:
[%FOREACH c IN CHANGES%][%c%]
[%END%]

If you would like to *proceed* with the changes to the domain name your *confirmation is required* by [%CONFIRMATIONENDDATE%].
After the above mentioned date (or in the event an involved party explicitly denies the request) the owner change will be considered failed and will not be executed. [Please note that both contacts must approve the requested change.]

If you would like the modifications to be carried out please click on the link below:
[%CONFIRMATIONLINK%]/?type=ownerchange&transferlock=[%TRANSFERLOCK%]&transferlockoverride=[%TRANSFERLOCK_OVERRIDE%]&trigger=[%TRIGGER%]&action=APPROVE

In case the changes have NOT been authorized by you please click on the following link to REJECT the owner change or modifications to the registrant contact.
[%CONFIRMATIONLINK%]/?type=ownerchange&transferlock=[%TRANSFERLOCK%]&transferlockoverride=[%TRANSFERLOCK_OVERRIDE%]&trigger=[%TRIGGER%]&action=DENY

[%IF INFOPAGELINK%]
More information can be found on our registrant change info page at the following link:
[%INFOPAGELINK%]
[%END%]

All acting persons declare by clicking on any of aforesaid links that they are bound to the sponsoring registrars terms and conditions (as shown on the registrar website) as well as ICANN policies.

[%IF FREETEXT0%][%FREETEXT0%][%END%]
[%IF FREETEXT1%][%FREETEXT1%][%END%]
[%IF FREETEXT2%][%FREETEXT2%][%END%]

Best regards,
[%IF FOOTER0%][%FOOTER0%][%ELSE%]Your ICANN accredited registrar
[%END%]
[%IF FOOTER1%][%FOOTER1%][%END%]
[%IF FOOTER2%][%FOOTER2%][%END%]

[%IF DOMAINS%]
=========
/ List of domain names affected by this
[%FOREACH d IN DOMAINS%][%d%]
[%END%]/ Full List End
[%END%]


Information Mail

The Information Mail is sent to the Old and New Registrant after the OwnerChange has been finished.

From: [%EMAILSENDER%]
Subject: [%EMAILSUBJECT%]
Type: text/plain
charset: UTF-8
Encoding: 8bit

Dear registrant of [%IF DOMAIN%][%DOMAIN%][%ELSE%](please see full list of names at the end of this email)[%END%],

In accordance with the Section II of the ICANN Inter-Registrar Transfer policy (see [https://www.icann.org/resources/pages/transfer-policy-2015-09-24-en]) we kindly inform you of the following changes that have been made to the registrant details of the domain name[s] listed below:

Changes to the domain owner data:
[%FOREACH c IN CHANGES%][%c%]
[%END%]

Please contact your service provider in case you wish to undo this modification request.

[%IF TRANSFERLOCK%]In accordance with the abovementioned policy the domain has been locked against transfers for 60 days.
[%END%]

[%IF INFOPAGELINK%]
More information can be found on our registrant change info page at the following link:
[%INFOPAGELINK%]
[%END%]

[%IF FREETEXT0%][%FREETEXT0%][%END%]
[%IF FREETEXT1%][%FREETEXT1%][%END%]
[%IF FREETEXT2%][%FREETEXT2%][%END%]

Best regards,
[%IF FOOTER0%][%FOOTER0%][%ELSE%]Your ICANN accredited registrar
[%END%]
[%IF FOOTER1%][%FOOTER1%][%END%]
[%IF FOOTER2%][%FOOTER2%][%END%]

[%IF DOMAINS%]
=========
/ List of domain names affected by this
[%FOREACH d IN DOMAINS%][%d%]
[%END%]/ Full List End
[%END%]

FAQ

Other registrars allow later removal of 60-day lock through owner's approval. Why don't you offer this option?

Unfortunately this is not possible. To our understanding, this would violate ICANN Policy. See also paragraph C 2 of the ICANN Policy at https://www.icann.org/resources/pages/transfer-policy-2016-06-01-en

Will another OwnerChange be possible during the 60-day lock phase?

Yes, this is possible.

Is the 60-day lock changing after an OwnerChange during the the 60-day lock phase?

In Designated Agent Mode the lock will be reset to full 60 days.
In FOA Mode the lock period is not changed and the remaining lock time persists.

Where can I find the Registration Agreement of Key-Systems?

The English and German variant of the Registration Agreement of Key-Systems is directly linked at several pages:
- in the footer of the old RRPproxy Web Interface (Registration Agreement)
- in the footer on rrpproxy.net (Registration Agreement)
- in the footer of our portal site key-systems.net (Registration Agreement)

How can I make sure my clients and registrants can agree to the Registration Agreement of Key-Systems?

In general, the Terms and Conditions as well as the Registration Agreement of Key-Systems and relevant appendices have to be forwarded to your registrants and they need to agree to them. We already introduced a new version of the Registration Agreement of Key-Systems in October which holds paragraph 1.9 including Designated Agent:
Both Registrar as well as Customers authorized by registered name holder shall be considered designated agents of registered name holder with regard to the management and registration of a domain name with regard to ICANN, registry or other parties involved in the registration process.
To make it even a bit more convenient, our FOA mails for regular inter-registrar transfers ask registrants to agree to our Terms and Conditions. Our Terms and Conditions already reference to our Registration Agreement in paragraph 1.7:
By initiating an order through Key-Systems and/or by executing electronic actions the customer declares that he has the proper authority to place orders either for himself or as properly authorized representative of his organisation and that he agrees to the terms and conditions, contractual terms and registration agreements in all parts.
If including our TAC and Registration Agreement in your own TAC is not possible we can advise to integrate them in your business processes and to make these documents and agreements available to the registrant on a case-by-case basis. For example, during checkout. This way you do not need to change your General Conditions and Special Conditions for Domain Names and you can make sure the clients have access to all necessary documents.

What if the email address of the Old Registrant is invalid or not working any more (i.e., the FOA Mail sent to Old Registrant can not be approved)?

If OwnerChange is requested but former email address is unreachable: This requires a special form, which can be generated through our formgenerator. A signed copy of this form plus document proving signature and contact relation must be supplied to your sponsoring registrar for review. Please fax the documents to +49 (0)6894 93 96 865 or send by email to fax@rrpproxy.net.

Please make sure that all documents are compiled into a single .pdf file, with the form showing the barcode as first page.

I'm working in Designated Agent Mode but what if I can not grant, that a single Registrant has not assigned me and Key-Systems as Designated Agents?

For such occasions we will provide you with the option to handle individual cases with the FOA Mode through a special parameter.

Using FOA Mode, will the 60-day lock always be applied after a successful OwnerChange? (Similar to Designated Agent Mode, where the 60-day lock is always applied after a successful OwnerChange.)

It depends if the New Registrant opts out of the 60-day lock and on your general settings.
The Old Registrant can opt out of the 60-day lock by clicking the respective link in the FOA Mail.
In general, if ICANNTRANSFER-ownerchange-transferlock-override is set to 0, New Registrants can never opt out of the 60-day transfer lock, the option is not available in FOA Mails.

Which email address is used by default for FOA Mails?

The default sending email-address is noreply@emailverification.info. It will be shown in your account settings in the ICANN Transfer section and you will be able to replace it with a custom address.

Which TAC URL is used by default for FOA Mails?

The default TAC URL is https://www.key-systems.net/en/terms-und-conditions. It will be shown in your account settings in the ICANN Transfer section and you will be able to replace it with a custom URL.

Which TLDs are affected?

All gTLDs are affected by the ICANN OwnerChange policy.

Personal tools
Namespaces

Variants
Actions
Resources
new gTLDs
Products
New Users
General
Tools