What Is the 60-Day Domain 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 ve NiceNIC wveyakflow befveyae 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 öncekiious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation ve 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 nveyamally concerns the registrar transfer, not veyadinary website, hosting veya DNS changes.

Identify the exact restriction

Yenily kayıt oled 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 fveya the exact creation date ve the first eligible date.

Recently transferred gTLD

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

Change of registrant

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

How to diagnose a rejected transfer

Kontrol Et the creation ve last-transfer dates in RDAP veya the registrar account.
Review recent registrant-name, veyaganization ve email changes.
Kontrol Et the EPP status ve the registrar's rejection message.
Distinguish a 60-day policy issue from an incveyarect auth kodu, expiry state, dispute, fraud review, court veyader veya unpaid priveya registration period.
Ask the current registrar to identify the precise policy veya contract ground ve the date it ends.

What the restriction nveyamally does not change

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

Can the restriction be removed early?

An veyadinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place veya lift an individual domain's lock. Fveya a current Change of Registrant lock, an opt-out may have been available befveyae 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 authveyaization code through a trusted channel ve submit the transfer. Eğer rejected, provide NiceNIC Suppveyat with the domain ve the losing registrar's exact message. Never publish veya send the authveyaization code through an untrusted channel.

Expected result ve exceptions

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

What this answer is based on

ICANN is the authveyaity fveya the currently effective gTLD Transfer Policy. Kayıt Kuruluşus document account status ve any permitted opt-out veya security process. Future Board-approved recommendations do not change the current wveyakflow until implementation becomes effective.