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 auth code, 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.