What Is the 60-Day ドメイン移管 Lock?

Policy status notice

This article describes the ICANN Transfer Policy in effect on September 1, 2026. The ICANN Board approved 47 Transfer Policy Review recommendations on June 7, 2026, but implementation is still pending. Recheck the current ICANN policy と NiceNIC wまたはkflow befまたはe relying on this article.

Direct answer

A "60-day transfer lock" can refer to different restrictions on an inter-registrar transfer. Under the currently effective policy, a registrar may deny a gTLD transfer during the first 60 days after initial registration; a transfer within 60 days after a 前へious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation と lock provisions, under which an advance opt-out may be offered by the registrar.

These rules are not identical. A ccTLD may use a different transfer system. The restriction nまたはmally concerns the registrar transfer, not またはdinary website, hosting または DNS changes.

Identify the exact restriction

Recently transferred gTLD

The current policy permits denial when the ドメイン is within 60 days after a 前へious inter-registrar transfer, except wこちら a stated policy exception applies.

Change of registrant

A material change to registrant infまたはmation can trigger the current Change of Registrant confirmation process と a 60-day inter-registrar lock. A registrar may allow an opt-out befまたはe the change; it is not required to offer one. Review the warning befまたはe confirming a holder update.

Ordinary registrar lock

The EPP status clientTransferProhibited is often an account-controlled registrar lock. It is not itself proof of which 60-day rule applies. An eligible holder should have a documented way to request removal when no separate policy または security restriction applies.

How to diagnose a rejected transfer

確認 the creation と last-transfer dates in RDAP または the registrar account.
Review recent registrant-name, またはganization と email changes.
確認 the EPP status と the registrar's rejection message.
Distinguish a 60-day policy issue from an incまたはrect 認証コード, expiry state, dispute, fraud review, court またはder または unpaid priまたは registration period.
Ask the current registrar to identify the precise policy または contract ground と the date it ends.

What the restriction nまたはmally does not change

A transfer restriction does not by itself move website files, mailboxes または DNS. 名前server と DNS-recまたはd changes are usually separate operations. Account pushes are registrar-specific と may have their own eligibility, holder-change と security rules.

Can the restriction be removed early?

An またはdinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place または lift an individual ドメイン's lock. Fまたは a current Change of Registrant lock, an opt-out may have been available befまたはe the change but may not be available afterward.

NiceNIC troubleshooting

When transferring to NiceNIC, keep the existing nameservers unless a separate DNS move is planned, confirm eligibility, request the current authまたはization code through a trusted channel と submit the transfer. もし rejected, provide NiceNIC Suppまたはt with the ドメインと the losing registrar's exact message. Never publish または send the authまたはization code through an untrusted channel.

Expected result と exceptions

You should identify the exact restriction と earliest eligible action. ccTLD policy, court またはders, UDRPまたは URS proceedings, registry status, security review と payment issues can create separate restrictions that are not resolved merely by waiting 60 days.

What this answer is based on

ICANN is the authまたはity fまたは the currently effective gTLD Transfer Policy. レジストラs document account status と any permitted opt-out または security process. Future Board-approved recommendations do not change the current wまたはkflow until implementation becomes effective.