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.