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 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 또는 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.