Transfer Policy

Effective as of August 21, 2025

Inter-Registrar Transfer

Holder-Authorized Transfers

Registrar Requirements

Registered Name Holders are able to transfer their domain name registrations between Registrars provided that the Gaining Registrar's transfer process meets the standards of this Transfer policy and that such transfer is not prohibited by ICANN or Registry policies.

1.1 Transfer Authorities

The Registered Name Holder is the only party that has the authority to approve or deny a transfer request to the Gaining Registrar. Registrar may use Registration Data from either the Registrar of Record or the relevant Registry for the purpose of verifying the authenticity of a transfer request; or from another data source as determined by a consensus policy.

Gaining Registrar Requirements

For each instance where a Registered Name Holder requests to transfer a domain name registration to a different Registrar, the Gaining Registrar shall, unless otherwise specified below:

2.1 Obtain express authorization from the Registered Name Holder. Hence, a transfer may only proceed if confirmation of the transfer is received by the Gaining Registrar from the Registered Name Holder.

2.1.1 The authorization must be made via a valid Standardized Form of Authorization (FOA). There are two different FOAs available at the ICANN website. The FOA labeled "Initial Authorization for Registrar Transfer" must be used to request an authorization for a registrar transfer from the Registered Name Holder. The FOA labeled "Confirmation of Registrar Transfer Request" must be used by the Registrar of Record to request confirmation of the transfer from the Registered Name Holder. The FOA shall be communicated in English, and any dispute arising out of a transfer request shall be conducted in the English language. Until such time as a secure method for transferring data is required by ICANN to be offered, if the Gaining Registrar is unable to gain access to then-current Registration Data for a domain name subject of a transfer, the Gaining Registrar is not required to obtain a Form of Authorization from the Registered Name Holder. Additionally, the Gaining Registrar must require the Registered Name Holder to independently re-enter Registration Data with the Gaining Registrar. In such instance, the Gaining Registrar is not required to follow the Change of Registrant Process as provided in Section II.C. of this Policy.

2.1.2 Our Registrar shall not rely on a physical process to obtain this authorization.

2.1.2.1 If the Gaining Registrar relies on a physical authorization process, then the Gaining Registrar assumes the burden of obtaining reliable evidence of the identity of the Registered Name Holder and maintaining appropriate records proving that such evidence was obtained. Further the Gaining Registrar also assumes the burden for ensuring that the entity making the request is indeed authorized to do so. The acceptable forms of physical identity are:

Notarized statement
Valid Drivers license
Passport
Article of Incorporation
Military ID
State/Government issued ID
Birth Certificate

In the event that the Gaining Registrar relies on an electronic process to obtain this authorization the acceptable forms of identity would include:

Electronic signature in conformance with national legislation, in the location of the Gaining Registrar (if such legislation exists).
Consent from an individual or entity that has an email address or phone number matching the Registered Name Holder email address or phone number.

2.1.3.2 The Registrar of Record may not deny a transfer request solely because it believes that the Gaining Registrar has not received the confirmation set forth above.

2.1.3.3 A transfer must not be allowed to proceed if no confirmation is received by the Gaining Registrar. The presumption in all cases will be that the Gaining Registrar has received and authenticated the transfer request made by a Registered Name Holder.

2.2 Request, by the transmission of a "transfer" command as specified in the Registrar Tool Kit, that the Registry Operator database be changed to reflect the new Registrar.

2.2.1 Transmission of a "transfer" command constitutes a representation on the part of the Gaining Registrar that the requisite authorization has been obtained from the Registered Name Holder where required pursuant to Section I.A.2.

2.2.2 The Gaining Registrar is responsible for validating the Registered Name Holder requests to transfer domain names between Registrars. However, the Registrar of Record must still transmit an FOA in accordance with Section I.A.3 ("Obligations of the Registrar of Record") of this policy.

2.2.3 The FOA labeled "Initial Authorization for Registrar Transfer" shall expire under the following circumstances:

2.2.3.1 a period of sixty (60) days has passed since the FOA was issued by the Gaining Registrar, unless the Gaining Registrar allows automatic renewal of the FOA and the Registered Name Holder has expressly opted in to the automatic renewal;

2.2.3.2 the domain name expires before the inter-registrar transfer is completed;

2.2.3.3 a Change of Registrant is completed further to Section II.C.

2.2.3.4 the inter-registrar transfer is completed.

2.2.4 If the FOA expires pursuant to one of the aforementioned circumstances described in I.A.2.2.3.1 – I.A.2.2.3.4, prior to submitting the "transfer" request to the registry, in order to proceed with the transfer, the Gaining Registrar must re-authorize the transfer request via a new FOA, where the FOA is required pursuant to Section I.A.2.

Obligations of the Registrar of Record

3.1 A Registrar of Record shall confirm the intent of the Registered Name Holder when a notice of a pending transfer is received from the Registry by notifying the Registered Name Holder of the transfer. The Registrar of Record must do so in a manner consistent with the standards set forth in ICANN Transfer policy.

3.2 In order to ensure that the form of the request employed by the Registrar of Record is substantially administrative and informative in nature and clearly provided to the Registered Name Holder for the purpose of verifying the intent of the Registered Name Holder, the Registrar of Record must use the FOA.

3.3 The FOA shall be communicated in English, and any dispute arising out of a transfer request shall be conducted in the English language. Registrars may choose to communicate with the Registered Name Holder in additional languages. However, the Registrar choosing to exercise such option is responsible for the accuracy and completeness of the translation into such additional non-English version of the FOA. Further, such non-English communications must follow the processes and procedures set forth in this policy. This includes but is not limited to the requirement that no Registrar shall add any additional information to the FOA used to obtain the consent of the Registered Name Holder in the case of a transfer request. In the event the Registered Name Holder preapproves a transfer, the Registrar of Record has the option of sending a modified version of the FOA, which informs the Registered Name Holder that the preapproved transfer has been initiated. This requirement does not preclude the Registrar of Record from marketing to its existing customers through separate communications.

3.4 The FOA should be sent by the Registrar of Record to the Registered Name Holder as soon as operationally possible, but must be sent not later than twenty-four (24) hours after receiving the transfer request from the Registry Operator.

3.5 Failure by the Registrar of Record to respond within five (5) calendar days to a notification from the Registry regarding a transfer request will result in a default "approval" of the transfer.

3.6 In the event that a Registered Name Holder listed in the RDDS has not confirmed their request to transfer with the Registrar of Record and the Registrar of Record has not explicitly denied the transfer request, the default action will be that the Registrar of Record must allow the transfer to proceed.

3.7 Upon denying a transfer request for any of the following reasons, the Registrar of Record must provide the Registered Name Holder and the potential Gaining Registrar with the reason for denial. The Registrar of Record may deny a transfer request only in the following specific instances:

3.7.1 Evidence of fraud.

3.7.2 Reasonable dispute over the identity of the Registered Name Holder.

3.7.3 No payment for previous registration period (including credit card charge-backs) if the domain name is past its expiration date or for previous or current registration periods if the domain name has not yet expired. In all such cases, however, the domain name must be put into "Registrar Hold" status by the Registrar of Record prior to the denial of transfer.

3.7.4 Express objection to the transfer by the authorized Registered Name Holder. Objection could take the form of specific request (either by paper or electronic means) by the authorized Registered Name Holder to deny a particular transfer request, or a general objection to all transfer requests received by the Registrar, either temporarily or indefinitely. In all cases, the objection must be provided with the express and informed consent of the authorized Registered Name Holder on an opt-in basis and upon request by the authorized Registered Name Holder, the Registrar must remove the lock or provide a reasonably accessible method for the authorized Registered Name Holder to remove the lock within five (5) calendar days.

3.7.5 The transfer was requested within 60 days of the creation date as shown in the registry RDDS record for the domain name.

3.7.6 A domain name is within 60 days (or a lesser period to be determined) after being transferred (apart from being transferred back to the original Registrar in cases where both Registrars so agree and/or where a decision in the dispute resolution process so directs). "Transferred" shall only mean that an inter-registrar transfer has occurred in accordance with the procedures of this policy.

3.8 The Registrar of Record must deny a transfer request in the following circumstances:

3.8.1 A pending UDRP proceeding that the Registrar has been informed of.

3.8.2 Court order by a court of competent jurisdiction.

3.8.3 Pending dispute related to a previous transfer pursuant to the Transfer Dispute Resolution Policy.

3.8.4 URS proceeding or URS suspension that the Registrar has been informed of.

3.8.5 The Registrar imposed a 60-day inter-registrar transfer lock following a Change of Registrant, and the Registered Name Holder did not opt out of the 60-day inter-registrar transfer lock prior to the Change of Registrant request.

3.9 Instances when the requested change of Registrar may not be denied include, but are not limited to:

3.9.1 Nonpayment for a pending or future registration period.

3.9.2 No response from the Registered Name Holder.

3.9.3 Domain name in Registrar Lock Status, unless the Registered Name Holder is provided with the reasonable opportunity and ability to unlock the domain name prior to the Transfer Request.

3.9.4 Domain name registration period time constraints, other than during the first 60 days of initial registration, during the first 60 days after a registrar transfer, or during the 60-day lock following a Change of Registrant pursuant to Section II.C.2.

3.9.5 General payment defaults between Registrar and business partners / affiliates in cases where the Registered Name Holder for the domain in question has paid for the registration.

3.10 The Registrar of Record has other mechanisms available to collect payment from the Registered Name Holder that are independent from the Transfer process. Hence, in the event of a dispute over payment, the Registrar of Record must not employ transfer processes as a mechanism to secure payment for services from a Registered Name Holder. Exceptions to this requirement are as follows:

3.10.1 In the case of non-payment for previous registration period(s) if the transfer is requested after the expiration date, or

3.10.2 In the case of non-payment of the current registration period, if transfer is requested before the expiration date.

Registrar Coordination are provided by ICANN Transfer Policy.

Requirements for the "ClientTransferProhibited" Status and "AuthInfo" Codes

5.1 Subject to ICANN specifications or policies and any applicable laws or regulations, Registrar must follow the requirements set forth below. Registrar may only set a domain name in "ClientTransferProhibited" status upon registration or subsequent request by the Registered Name Holder, provided, however, that the Registrar includes in its registration agreement (obtaining the express consent of the Registered Name Holder) the terms and conditions upon which it prohibits transfer of the domain name. Further, the Registrar must remove the "ClientTransferProhibited" status within five (5) calendar days of the Registered Name Holder's initial request if the Registrar does not provide facilities for the Registered Name Holder to remove the "ClientTransferProhibited" status.

5.2 Registrars must provide the Registered Name Holder with the unique "AuthInfo" code and remove the "ClientTransferProhibited" within five (5) calendar days of the Registered Name Holder's initial request if the Registrar does not provide facilities for the Registered Name Holder to generate and manage their own unique "AuthInfo" code and to remove the "ClientTransferProhibited" status.

5.3 Registrars may not employ any mechanism for complying with a Registered Name Holder's request to remove the "ClientTransferProhibited" status or obtain the applicable "AuthInfo Code" that is more restrictive than the mechanisms used for changing any aspect of the Registered Name Holder's contact or name server information.

5.4 The Registrar of Record must not refuse to remove the "ClientTransferProhibited" status or release an "AuthInfo Code" to the Registered Name Holder solely because there is a dispute between the Registered Name Holder and the Registrar over payment.

5.5 Registrar-generated "AuthInfo" codes must be unique on a per-domain basis.

5.6 The "AuthInfo" codes must be used solely to identify a Registered Name Holder, whereas the FOAs still need to be used for authorization or confirmation of a transfer request, as described in Section I.A.2 and Section I.A.4 of this policy.

5.7 Registrar SHALL follow best practices in generating and updating the "AuthInfo" code to facilitate a secure transfer process.

Registry Requirements are provided by ICANN Transfer Policy.

Records of Registration

Each Registrar shall require its customer, the Registered Name Holder, to maintain its own records appropriate to document and prove the initial domain name registration date.

Effect on Term of Registration

The completion by Registry Operator of a holder-authorized transfer under Section I.A shall result in a one-year extension of the existing registration, provided that in no event shall the total unexpired term of a registration exceed ten (10) years.

ICANN-Approved Transfers are provided by ICANN Transfer Policy.

Transfer Dispute Resolution Policy

Procedures for handling disputes concerning inter-registrar transfers are set forth in the Transfer Dispute Resolution Policy. Procedures in this policy must be followed by the applicable Registry Operators and ICANN accredited Registrars.

Inter-Registrant Transfer

Definitions

This policy uses the following terms:

1.1 "Change of Registrant" means a Material Change to any of the following:

1.1.1 Prior Registrant name

1.1.2 Prior Registrant organization

1.1.3 Prior Registrant email address

1.2 "Designated Agent" means an individual or entity that the Prior Registrant or New Registrant explicitly authorizes to approve a Change of Registrant on its behalf.

1.3 "Material Change" means a change which is not a typographical correction. The following will be considered material changes:

1.3.1 A change to the Registered Name Holder's name or organization that does not appear to be merely a typographical correction;

1.3.2 Any change to the Registered Name Holder's name or organization that is accompanied by a change of address or phone number;

1.3.3 Any change to the Registered Name Holder's email address.

1.4 "Prior Registrant" means the Registered Name Holder at the time a Change of Registrant is initiated.

1.5 "New Registrant" means the entity or person to whom the Prior Registrant proposes to transfer its domain name registration.

Availability of Change of Registrant

In general, registrants must be permitted to update their Registration Data and transfer their registration rights to other registrants freely.

A Registrar must deny a Change of Registrant request under the following circumstances:

2.1 The domain name registration agreement has expired, and the Registered Name Holder no longer has the right to renew or transfer the domain name to another registrar, as provided for in Section 2.2.5 of the Expired Registration Recovery Policy;

2.2 The Change of Registrant was not properly authorized by the Prior Registrant and the New Registrant, further to Section II.C below;

2.3 The domain name is subject to a domain name related dispute, including but not limited to:

2.3.1 A pending UDRP proceeding that the Registrar has been informed of;

2.3.2 A pending URS proceeding that the Registrar has been informed of;

2.3.3 A pending TDRP proceeding;

2.3.4 A court order by a court of competent jurisdiction, prohibiting a Change of Registrant, that the Registrar has been informed of.

In the following circumstances, the Change of Registrant process described in Section II.C below does not apply:

3.1 the registration agreement expires;

3.2 the registration agreement is terminated by the Registrar;

3.3 the Registrar or Registry Operator updates the Prior Registrant's information pursuant to a court order;

3.4 the Registrar updates the Prior Registrant's information in the implementation of a UDRP decision;

3.5 the Registrar updates the Prior Registrant's information in accordance with the Expired Domain Deletion Policy;

3.6 the Registrar updates the Prior Registrant's information in response to an abuse complaint.

Change of Registrant Process

To process a Change of Registrant from the Prior Registrant to a New Registrant, the Registrar must do all of the following:

1.1 Confirm the domain name is eligible for Change of Registrant further to Section II.B;

1.2 Obtain confirmation of the Change of Registrant request from the New Registrant, or a Designated Agent of the New Registrant. The Registrar must use a secure mechanism5 to confirm that the New Registrant and/or their respective Designated Agents have explicitly consented to the Change of Registrant. In obtaining the confirmation, the Registrar must inform the New Registrant or its Designated Agent, if applicable, that the New Registrant must enter into a registration agreement with the Registrar (a link to the registration agreement itself can be provided). The Registrar must also inform the New Registrant or Designated Agent, if applicable, that the request will not proceed if it is not confirmed in a number of days set by the Registrar, not to exceed sixty (60) days);

1.3 Inform the Prior Registrant or its Designated Agent that if its final goal is to transfer the domain name to a different registrar, the Prior Registrant is advised to request the inter-registrar transfer before the Change of Registrant to avoid triggering the 60-day lock described in Section II.C.2 (unless the Registrar gave the Prior Registrant the option to opt out of the 60-day lock, and the Prior Registrant opted out the 60-day lock);

1.4 Upon or after informing the Prior Registrant or its Designated Agent, if applicable, as described in II.C.1.3 above, obtain confirmation of the Change of Registrant request from the Prior Registrant, or the Designated Agent of the Prior Registrant. The Registrar must use a secure mechanism to confirm that the Prior Registrant and/or their respective Designated Agents have explicitly consented to the Change of Registrant. In obtaining the confirmation, the Registrar must inform the Prior Registrant or Designated Agent, if applicable, that the Change of Registrant request will not proceed if it is not confirmed in a number of days set by the Registrar, not to exceed sixty (60) days);

1.5 Process the Change of Registrant within one (1) day of obtaining the confirmations described above;

1.6 Notify the Prior Registrant and New Registrant before or within one day of the completion of the Change of Registrant. The notification must:

1.6.1 always be sent to both the New Registrant and Prior Registrant before or within one day of the Change of Registrant being performed;

1.6.2 explain the request that was received and list the domain(s) in question;

1.6.3. include contact information for questions.

1.6.4. advise the Prior Registrant and New Registrant of the 60-day inter-registrar transfer lock as described in Section II.C.2 or advise the Prior Registrant that it previously opted out of the 60-day inter-registrar transfer lock as described in Section II.C.2.

The Registrar must impose a 60-day inter-registrar transfer lock following a Change of Registrant, provided, however, that the Registrar may allow the Registered Name Holder to opt out of the 60-day inter-registrar transfer lock prior to any Change of Registrant request.

The Registrar allow the Registered Name Holder to opt out of the 60-day inter-registrar transfer lock prior to any Change of Registrant request. The Registered Name Holder explicitly opts out of any 60-day inter-registrar transfer lock that would otherwise be imposed under the Transfer Policy due to any such Change of Registrant. In addition, the Registered Name Holder explicitly authorizes the Registrar and/or the registrar of record to act as its “Designated Agent” (as defined in the Transfer Policy) to approve each “Change of Registrant” (as defined in the Transfer Policy) on its behalf. Such approval will happen automatically and, thereafter, the appropriate notices sent.