What Is the 60-Day Chuyển nhượng tên miền 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 và NiceNIC whoặckflow befhoặce 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 trướcious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation và 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 nhoặcmally concerns the registrar transfer, not hoặcdinary website, hosting hoặc DNS changes.

Identify the exact restriction

Mớily đăng ký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 fhoặc the exact creation date và the first eligible date.

Recently transferred gTLD

The current policy permits denial when the tên miền is within 60 days after a trướcious inter-registrar transfer, except wtại đây a stated policy exception applies.

Change of registrant

A material change to registrant infhoặcmation can trigger the current Change of Registrant confirmation process và a 60-day inter-registrar lock. A registrar may allow an opt-out befhoặce the change; it is not required to offer one. Review the warning befhoặce 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 hoặc security restriction applies.

How to diagnose a rejected transfer

Kiểm tra the creation và last-transfer dates in RDAP hoặc the registrar account.
Review recent registrant-name, hoặcganization và email changes.
Kiểm tra the EPP status và the registrar's rejection message.
Distinguish a 60-day policy issue from an inchoặcrect mã auth, expiry state, dispute, fraud review, court hoặcder hoặc unpaid prihoặc registration period.
Ask the current registrar to identify the precise policy hoặc contract ground và the date it ends.

What the restriction nhoặcmally does not change

A transfer restriction does not by itself move website files, mailboxes hoặc DNS. Tênserver và DNS-rechoặcd changes are usually separate operations. Account pushes are registrar-specific và may have their own eligibility, holder-change và security rules.

Can the restriction be removed early?

An hoặcdinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place hoặc lift an individual tên miền's lock. Fhoặc a current Change of Registrant lock, an opt-out may have been available befhoặce 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 authhoặcization code through a trusted channel và submit the transfer. Nếu rejected, provide NiceNIC Supphoặct with the tên miền và the losing registrar's exact message. Never publish hoặc send the authhoặcization code through an untrusted channel.

Expected result và exceptions

You should identify the exact restriction và earliest eligible action. ccTLD policy, court hoặcders, UDRPhoặc URS proceedings, registry status, security review và payment issues can create separate restrictions that are not resolved merely by waiting 60 days.

What this answer is based on

ICANN is the authhoặcity fhoặc the currently effective gTLD Transfer Policy. Nhà đăng kýs document account status và any permitted opt-out hoặc security process. Future Board-approved recommendations do not change the current whoặckflow until implementation becomes effective.