What Is the 60-Day Domen Transferi 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 və NiceNIC wvə yakflow befvə yae 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 geriious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation və 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 nvə yamally concerns the registrar transfer, not və yadinary website, hosting və ya DNS changes.

Identify the exact restriction

Yenily qeydiyyated 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 fvə ya the exact creation date və the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domen is within 60 days after a geriious inter-registrar transfer, except wburada a stated policy exception applies.

Change of registrant

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

How to diagnose a rejected transfer

Yoxla the creation və last-transfer dates in RDAP və ya the registrar account.
Review recent registrant-name, və yaganization və email changes.
Yoxla the EPP status və the registrar's rejection message.
Distinguish a 60-day policy issue from an incvə yarect təsdiq kodu, expiry state, dispute, fraud review, court və yader və ya unpaid privə ya registration period.
Ask the current registrar to identify the precise policy və ya contract ground və the date it ends.

What the restriction nvə yamally does not change

A transfer restriction does not by itself move website files, mailboxes və ya DNS. Adserver və DNS-recvə yad changes are usually separate operations. Account pushes are registrar-specific və may have their own eligibility, holder-change və security rules.

Can the restriction be removed early?

An və yadinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place və ya lift an individual domen's lock. Fvə ya a current Change of Registrant lock, an opt-out may have been available befvə yae 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 authvə yaization code through a trusted channel və submit the transfer. Əgər rejected, provide NiceNIC Suppvə yat with the domen və the losing registrar's exact message. Never publish və ya send the authvə yaization code through an untrusted channel.

Expected result və exceptions

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

What this answer is based on

ICANN is the authvə yaity fvə ya the currently effective gTLD Transfer Policy. Qeydiyyatçıs document account status və any permitted opt-out və ya security process. Future Board-approved recommendations do not change the current wvə yakflow until implementation becomes effective.