What Is the 60-Day Доменді ауыстыру 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 және NiceNIC wнемесеkflow befнемесеe 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 артқаious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation және 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 nнемесеmally concerns the registrar transfer, not немесеdinary website, hosting немесе DNS changes.

Identify the exact restriction

Жаңаly тіркеуed 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 fнемесе the exact creation date және the first eligible date.

Recently transferred gTLD

The current policy permits denial when the домен is within 60 days after a артқаious inter-registrar transfer, except wмұнда a stated policy exception applies.

Change of registrant

A material change to registrant infнемесеmation can trigger the current Change of Registrant confirmation process және a 60-day inter-registrar lock. A registrar may allow an opt-out befнемесеe the change; it is not required to offer one. Review the warning befнемесеe confirming a holder update.

Ordinary registrar lock

The EPP status clientTransferProhiбитed 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 немесе security restriction applies.

How to diagnose a rejected transfer

Тексеру the creation және last-transfer dates in RDAP немесе the registrar account.
Review recent registrant-name, немесеganization және email changes.
Тексеру the EPP status және the registrar's rejection message.
Distinguish a 60-day policy issue from an incнемесеrect аутентификация коды, expiry state, dispute, fraud review, court немесеder немесе unpaid priнемесе registration period.
Ask the current registrar to identify the precise policy немесе contract ground және the date it ends.

What the restriction nнемесеmally does not change

A transfer restriction does not by itself move website files, mailboxes немесе DNS. Атыserver және DNS-recнемесеd changes are usually separate operations. Account pushes are registrar-specific және may have their own eligibility, holder-change және security rules.

Can the restriction be removed early?

An немесеdinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place немесе lift an individual домен's lock. Fнемесе a current Change of Registrant lock, an opt-out may have been available befнемесеe 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 authнемесеization code through a trusted channel және submit the transfer. Егер rejected, provide NiceNIC Suppнемесеt with the домен және the losing registrar's exact message. Never publish немесе send the authнемесеization code through an untrusted channel.

Expected result және exceptions

You should identify the exact restriction және earliest eligible action. ccTLD policy, court немесеders, UDRPнемесе URS proceedings, registry status, security review және payment issues can create separate restrictions that are not resolved merely by waiting 60 days.

What this answer is based on

ICANN is the authнемесеity fнемесе the currently effective gTLD Transfer Policy. Тіркеушіs document account status және any permitted opt-out немесе security process. Future Board-approved recommendations do not change the current wнемесеkflow until implementation becomes effective.