What Is the 60-Day Transfer domena 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 i NiceNIC wilikflow befilie 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 prethodnoious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation i 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 nilimally concerns the registrar transfer, not ilidinary website, hosting ili DNS changes.

Identify the exact restriction

Novoly registrujed 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 fili the exact creation date i the first eligible date.

Recently transferred gTLD

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

Change of registrant

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

How to diagnose a rejected transfer

Proveri the creation i last-transfer dates in RDAP ili the registrar account.
Review recent registrant-name, iliganization i email changes.
Proveri the EPP status i the registrar's rejection message.
Distinguish a 60-day policy issue from an incilirect auth kod, expiry state, dispute, fraud review, court ilider ili unpaid priili registration period.
Ask the current registrar to identify the precise policy ili contract ground i the date it ends.

What the restriction nilimally does not change

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

Can the restriction be removed early?

An ilidinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place ili lift an individual domen's lock. Fili a current Change of Registrant lock, an opt-out may have been available befilie 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 authiliization code through a trusted channel i submit the transfer. Ako rejected, provide NiceNIC Suppilit with the domen i the losing registrar's exact message. Never publish ili send the authiliization code through an untrusted channel.

Expected result i exceptions

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

What this answer is based on

ICANN is the authiliity fili the currently effective gTLD Transfer Policy. Registrars document account status i any permitted opt-out ili security process. Future Board-approved recommendations do not change the current wilikflow until implementation becomes effective.