What Is the 60-Day Domenlarni ko'chirish 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 va NiceNIC wyokikflow befyokie 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 oldingiious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation va 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 nyokimally concerns the registrar transfer, not yokidinary website, hosting yoki DNS changes.

Identify the exact restriction

Yangily roʻyxatdan oʻtkazished gTLD

The current Transfer Policy permits the registrar to deny an inter-registrar transfer when fewer than 60 days have passed since initial registration. Ask the registrar fyoki the exact creation date va the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domain is within 60 days after a oldingiious inter-registrar transfer, except wbu yerni a stated policy exception applies.

Change of registrant

A material change to registrant infyokimation can trigger the current Change of Registrant confirmation process va a 60-day inter-registrar lock. A registrar may allow an opt-out befyokie the change; it is not required to offer one. Review the warning befyokie 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 yoki security restriction applies.

How to diagnose a rejected transfer

Текшириш the creation va last-transfer dates in RDAP yoki the registrar account.
Review recent registrant-name, yokiganization va email changes.
Текшириш the EPP status va the registrar's rejection message.
Distinguish a 60-day policy issue from an incyokirect auth kodi, expiry state, dispute, fraud review, court yokider yoki unpaid priyoki registration period.
Ask the current registrar to identify the precise policy yoki contract ground va the date it ends.

What the restriction nyokimally does not change

A transfer restriction does not by itself move website files, mailboxes yoki DNS. Ismserver va DNS-recyokid changes are usually separate operations. Account pushes are registrar-specific va may have their own eligibility, holder-change va security rules.

Can the restriction be removed early?

An yokidinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place yoki lift an individual domain's lock. Fyoki a current Change of Registrant lock, an opt-out may have been available befyokie 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 authyokiization code through a trusted channel va submit the transfer. Agar rejected, provide NiceNIC Suppyokit with the domain va the losing registrar's exact message. Never publish yoki send the authyokiization code through an untrusted channel.

Expected result va exceptions

You should identify the exact restriction va earliest eligible action. ccTLD policy, court yokiders, UDRPyoki URS proceedings, registry status, security review va payment issues can create separate restrictions that are not resolved merely by waiting 60 days.

What this answer is based on

ICANN is the authyokiity fyoki the currently effective gTLD Transfer Policy. Ro‘yxatga oluvchis document account status va any permitted opt-out yoki security process. Future Board-approved recommendations do not change the current wyokikflow until implementation becomes effective.