{
 "source": "ICANN Transfer Policy, updated 21 February 2024 (required from 21 August 2025 at the latest), with the ICANN registrant FAQ, RFC 5730, RFC 5731 and RFC 9154; changes adopted by the ICANN Board on 7 June 2026 from the GNSO Transfer Policy Review Final Report (not in force)",
 "urls": {
  "policy": "https://www.icann.org/en/contracted-parties/accredited-registrars/resources/domain-name-transfers/policy",
  "transfers": "https://www.icann.org/transfers/",
  "faq": "https://www.icann.org/resources/pages/name-holder-faqs-2017-10-10-en",
  "board_resolution": "https://www.icann.org/en/board-activities-and-meetings/materials/approved-resolutions-regular-meeting-of-the-icann-board-07-06-2026-en",
  "scorecard": "https://www.icann.org/en/system/files/files/policy-development-consolidated-scorecards-21sep26-en.pdf",
  "implementation": "https://www.icann.org/policy/implementation",
  "final_report": "https://gnso.icann.org/sites/default/files/policy/2025/correspondence/tpr-team-to-gnso-council-04feb25-en.pdf",
  "rfc9154": "https://www.rfc-editor.org/rfc/rfc9154"
 },
 "fetched": "2026-09-27",
 "in_force": {
  "version": "Updated 21 February 2024 to reflect changes required to implement the Registration Data Policy. Contracted parties may implement this updated Policy beginning on 21 August 2024 and must implement no later than 21 August 2025.",
  "required_from": "2025-08-21",
  "previous": "Transfer Policy (Effective 1 December 2016 through 20 August 2025)"
 },
 "rules": {
  "authinfo_days": 5,
  "unlock_days": 5,
  "losing_notice_hours": 24,
  "auto_approve_days": 5,
  "registry_nack_days": 5,
  "lock_created_days": 60,
  "lock_transfer_days": 60,
  "lock_cor_days": 60,
  "gaining_foa_days": 60,
  "cor_confirm_max_days": 60,
  "cor_process_days": 1,
  "teac_hours": 4,
  "undo_days": 5,
  "max_term_years": 10,
  "tdrp_months": 12,
  "cor_notice_days": 1,
  "undo_dispute_days": 14,
  "extension_years": 1
 },
 "clauses": {
  "I.A.1.1": "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. Registrars 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.",
  "I.A.3.4": "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.",
  "I.A.3.5": "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.",
  "I.A.3.6": "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.",
  "I.A.3.7": "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:",
  "I.A.5.2": "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.",
  "I.A.5.4": "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.",
  "I.A.6.1": "6.1 Upon receipt of the \"transfer\" command from the Gaining Registrar, Registry Operator MUST (1) verify that the \"AuthInfo\" code provided by the Gaining Registrar is valid in order to accept an inter-registrar transfer request and MUST (2) transmit an electronic notification to both Registrars. In the case of those Registries that use electronic mail notifications, the response notification may be sent to the unique email address established by each Registrar for the purpose of facilitating transfers. Registry Operator SHALL follow best practices in generating and updating the \"AuthInfo\" code to facilitate a secure transfer process.",
  "I.A.6.2": "6.2 The Registry Operator shall complete the requested transfer unless, within five (5) calendar days, Registry Operator receives a NACK protocol command from the Registrar of Record.",
  "I.A.6.3": "6.3 When the Registry's database has been updated to reflect the change to the Gaining Registrar, Registry Operator will transmit an electronic notification to both Registrars. The notification may be sent to the unique email address established by each Registrar for the purpose of facilitating transfers or such other email address agreed to by the parties.",
  "I.A.8": "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.",
  "I.A.4.6.3": "4.6.3 Messages sent via the TEAC communication channel must generate a non-automated response by a human representative of the Gaining Registrar. The person or team responding must be capable and authorized to investigate and address urgent transfer issues. Responses are required within 4 hours of the initial request, although final resolution of the incident may take longer.",
  "I.A.6.4": "6.4 The Registry Operator shall undo a transfer if, after a transfer has occurred, the Registry Operator receives one of the notices as set forth below. In such case, the transfer will be reversed and the Registrar of Record field reset to its original state. The Registry Operator must undo the transfer within five (5) calendar days of receipt of the notice except in the case of a Registry dispute decision, in which case the Registry Operator must undo the transfer within fourteen calendar days unless a court action is filed. The notice required shall be one of the following:",
  "II.C.1.5": "1.5 Process the Change of Registrant within one (1) day of obtaining the confirmations described above;",
  "II.C.1.6": "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:",
  "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."
 },
 "deny": {
  "may": [
   {
    "id": "I.A.3.7.1",
    "text": "Evidence of fraud."
   },
   {
    "id": "I.A.3.7.2",
    "text": "Reasonable dispute over the identity of the Registered Name Holder."
   },
   {
    "id": "I.A.3.7.3",
    "text": "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."
   },
   {
    "id": "I.A.3.7.4",
    "text": "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."
   },
   {
    "id": "I.A.3.7.5",
    "text": "The transfer was requested within 60 days of the creation date as shown in the registry RDDS record for the domain name."
   },
   {
    "id": "I.A.3.7.6",
    "text": "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."
   }
  ],
  "must": [
   {
    "id": "I.A.3.8.1",
    "text": "A pending UDRP proceeding that the Registrar has been informed of."
   },
   {
    "id": "I.A.3.8.2",
    "text": "Court order by a court of competent jurisdiction."
   },
   {
    "id": "I.A.3.8.3",
    "text": "Pending dispute related to a previous transfer pursuant to the Transfer Dispute Resolution Policy."
   },
   {
    "id": "I.A.3.8.4",
    "text": "URS proceeding or URS suspension that the Registrar has been informed of."
   },
   {
    "id": "I.A.3.8.5",
    "text": "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."
   }
  ],
  "must_not": [
   {
    "id": "I.A.3.9.1",
    "text": "Nonpayment for a pending or future registration period."
   },
   {
    "id": "I.A.3.9.2",
    "text": "No response from the Registered Name Holder."
   },
   {
    "id": "I.A.3.9.3",
    "text": "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."
   },
   {
    "id": "I.A.3.9.4",
    "text": "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."
   },
   {
    "id": "I.A.3.9.5",
    "text": "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."
   }
  ]
 },
 "cor": {
  "fields": [
   "Prior Registrant name",
   "Prior Registrant organization",
   "Prior Registrant email address"
  ],
  "material": [
   {
    "id": "II.A.1.3.1",
    "text": "A change to the Registered Name Holder's name or organization that does not appear to be merely a typographical correction;"
   },
   {
    "id": "II.A.1.3.2",
    "text": "Any change to the Registered Name Holder's name or organization that is accompanied by a change of address or phone number;"
   },
   {
    "id": "II.A.1.3.3",
    "text": "Any change to the Registered Name Holder's email address."
   }
  ],
  "material_def": "\"Material Change\" means a change which is not a typographical correction. The following will be considered material changes:",
  "typo_examples": [
   {
    "field": "Name",
    "from": "oJhn Smith",
    "to": "John Smith"
   },
   {
    "field": "Name",
    "from": "Jane Kgan",
    "to": "Jane Kang"
   },
   {
    "field": "Organization",
    "from": "Example, Icn.",
    "to": "Example, Inc."
   },
   {
    "field": "Organization",
    "from": "ExampleCorp.",
    "to": "Example Corp."
   }
  ],
  "must_deny": [
   {
    "id": "II.B.2.1",
    "text": "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;"
   },
   {
    "id": "II.B.2.2",
    "text": "The Change of Registrant was not properly authorized by the Prior Registrant and the New Registrant, further to Section II.C below;"
   },
   {
    "id": "II.B.2.3.1",
    "text": "A pending UDRP proceeding that the Registrar has been informed of;"
   },
   {
    "id": "II.B.2.3.2",
    "text": "A pending URS proceeding that the Registrar has been informed of;"
   },
   {
    "id": "II.B.2.3.3",
    "text": "A pending TDRP proceeding;"
   },
   {
    "id": "II.B.2.3.4",
    "text": "A court order by a court of competent jurisdiction, prohibiting a Change of Registrant, that the Registrar has been informed of."
   }
  ],
  "not_apply": [
   {
    "id": "II.B.3.1",
    "text": "the registration agreement expires;"
   },
   {
    "id": "II.B.3.2",
    "text": "the registration agreement is terminated by the Registrar;"
   },
   {
    "id": "II.B.3.3",
    "text": "the Registrar or Registry Operator updates the Prior Registrant's information pursuant to a court order;"
   },
   {
    "id": "II.B.3.4",
    "text": "the Registrar updates the Prior Registrant's information in the implementation of a UDRP decision;"
   },
   {
    "id": "II.B.3.5",
    "text": "the Registrar updates the Prior Registrant's information in accordance with the Expired Domain Deletion Policy;"
   },
   {
    "id": "II.B.3.6",
    "text": "the Registrar updates the Prior Registrant's information in response to an abuse complaint."
   }
  ],
  "process": [
   {
    "id": "II.C.1.1",
    "text": "Confirm the domain name is eligible for Change of Registrant further to Section II.B;"
   },
   {
    "id": "II.C.1.2",
    "text": "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 mechanism 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);"
   },
   {
    "id": "II.C.1.3",
    "text": "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);"
   },
   {
    "id": "II.C.1.4",
    "text": "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);"
   },
   {
    "id": "II.C.1.5",
    "text": "Process the Change of Registrant within one (1) day of obtaining the confirmations described above;"
   },
   {
    "id": "II.C.1.6",
    "text": "Notify the Prior Registrant and New Registrant before or within one day of the completion of the Change of Registrant. The notification must:"
   }
  ],
  "lock": {
   "id": "II.C.2",
   "text": "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."
  }
 },
 "faq": {
  "expired": "You have the right to transfer an expired domain. Registrars are not allowed to deny a transfer due to expiration or nonrenewal",
  "rgp": "the name must be restored by your current registrar before it can be transferred",
  "fee": "Registrars are allowed to set their own prices for this service so some may choose to charge a fee. However, a transfer cannot be denied due to non-payment of this transfer fee.",
  "get_code": "Your registrar may allow you, via an online interface tool, to generate and manage your own AuthInfo code. If not, you will need to contact your registrar directly to obtain it. Your registrar must provide you with the AuthInfo code within five (5) calendar days of your request."
 },
 "errp_rgp": "During the Redemption Grace Period, the registry must disable DNS resolution and prohibit attempted transfers of the registration.",
 "landing_scope": "All ICANN-accredited registrars and unsponsored gTLD registry operators are required to follow this policy.",
 "cctld": "Because ccTLDs are managed locally, the rules and policies for registering domain names vary across ccTLDs.",
 "rfc9154_lengths": [
  {
   "bits": 128,
   "charset": 94,
   "length": 20
  },
  {
   "bits": 128,
   "charset": 36,
   "length": 25
  }
 ],
 "adopted": {
  "board_date": "2026-06-07",
  "resolution": "2026.06.07.04",
  "resolution_text": "Resolved (2026.06.07.04), the Board adopts the Recommendations, and directs ICANN's President and CEO, or his designee(s), subject to prioritization, to implement the Recommendations, taking into account the ICANN org Feasibility Assessment and any additional operational, technical, legal, security, or resource considerations identified during implementation.",
  "status": "Currently in the planning/resourcing process.",
  "status_date": "2026-09-21",
  "effective_date": null,
  "six_months": "Policies within a bundle are announced together, which triggers a window of at least six months for contracted parties to update their operations to ensure compliance with the new policies.",
  "rules": {
   "lock_created_hours": 720,
   "lock_transfer_hours": 720,
   "tac_ttl_hours": 336,
   "tac_issue_hours": 120,
   "auto_approve_hours": 120,
   "completion_notice_hours": 24,
   "cord_notice_hours": 24,
   "cor_lock": false,
   "lock_created_days": 30,
   "lock_transfer_days": 30,
   "tac_ttl_days": 14
  },
  "texts": {
   "fr_rec3": "The Working Group recommends that the Registrar MUST restrict the RNH from transferring a domain name to a new Registrar for 720 hours from the Creation Date in RDDS.",
   "fr_rec4": "The Working Group recommends that the Transfer Policy and all related policies MUST use the term \"Transfer Authorization Code\" or \"TAC\" in place of the currently used term \"AuthInfo Code\" and related terms.",
   "fr_rec9": "The TAC MUST be valid for 336 hours from the time it is set at the Registry, enforced by the Registry.",
   "fr_rec18": "The Registrar MUST restrict the RNH from transferring a domain name to a new Registrar for 720 hours from the completion of an inter-Registrar transfer.",
   "fr_rec26_4": "The Working Group recommends eliminating from the future Change of Registrant Data Policy the requirement that the Registrar impose a 60-day inter-Registrar transfer lock following a Change of Registrant.",
   "fr_rec27": "the Registrar MUST send a Change of Registrant Data notification to the RNH without undue delay, but no later than 24 hours after the Change of Registrant Data occurred.",
   "fr_rec26_3": "The Working Group recommends eliminating from the future Change of Registrant Data Policy the requirement that the Registrar request and obtain confirmation from both the Prior Registrant and the New Registrant prior to processing a Change of Registrant Data",
   "fr_rec15": "The Working Group recommends eliminating from the Transfer Policy the requirement that the Gaining Registrar send a Gaining FOA.",
   "fr_rec17_5": "The Transfer Confirmation MUST NOT include a mechanism for immediately approving the inter-Registrar transfer."
  }
 }
}