What Is the 60-Day Transferim Domainesh 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 dhe NiceNIC wosekflow befosee 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 mbrapaious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation dhe 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 nosemally concerns the registrar transfer, not osedinary website, hosting ose DNS changes.

Identify the exact restriction

I rily regjistroed 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 fose the exact creation date dhe the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domain is within 60 days after a mbrapaious inter-registrar transfer, except wkëtu a stated policy exception applies.

Change of registrant

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

How to diagnose a rejected transfer

Kontrollo the creation dhe last-transfer dates in RDAP ose the registrar account.
Review recent registrant-name, oseganization dhe email changes.
Kontrollo the EPP status dhe the registrar's rejection message.
Distinguish a 60-day policy issue from an incoserect Kodi i autorizimit, expiry state, dispute, fraud review, court oseder ose unpaid priose registration period.
Ask the current registrar to identify the precise policy ose contract ground dhe the date it ends.

What the restriction nosemally does not change

A transfer restriction does not by itself move website files, mailboxes ose DNS. Emërserver dhe DNS-recosed changes are usually separate operations. Account pushes are registrar-specific dhe may have their own eligibility, holder-change dhe security rules.

Can the restriction be removed early?

An osedinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place ose lift an individual domain's lock. Fose a current Change of Registrant lock, an opt-out may have been available befosee 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 authoseization code through a trusted channel dhe submit the transfer. Nëse rejected, provide NiceNIC Supposet with the domain dhe the losing registrar's exact message. Never publish ose send the authoseization code through an untrusted channel.

Expected result dhe exceptions

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

What this answer is based on

ICANN is the authoseity fose the currently effective gTLD Transfer Policy. Regjistruess document account status dhe any permitted opt-out ose security process. Future Board-approved recommendations do not change the current wosekflow until implementation becomes effective.