What Is the 60-Day Transfer Domain 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 dan NiceNIC wataukflow befataue 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 sebelumnyaious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation dan 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 nataumally concerns the registrar transfer, not ataudinary website, hosting atau DNS changes.

Identify the exact restriction

Baruly daftared 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 fatau the exact creation date dan the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domain is within 60 days after a sebelumnyaious inter-registrar transfer, except wdi sini a stated policy exception applies.

Change of registrant

A material change to registrant infataumation can trigger the current Change of Registrant confirmation process dan a 60-day inter-registrar lock. A registrar may allow an opt-out befataue the change; it is not required to offer one. Review the warning befataue 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 atau security restriction applies.

How to diagnose a rejected transfer

Cek the creation dan last-transfer dates in RDAP atau the registrar account.
Review recent registrant-name, atauganization dan email changes.
Cek the EPP status dan the registrar's rejection message.
Distinguish a 60-day policy issue from an incataurect kode otorisasi, expiry state, dispute, fraud review, court atauder atau unpaid priatau registration period.
Ask the current registrar to identify the precise policy atau contract ground dan the date it ends.

What the restriction nataumally does not change

A transfer restriction does not by itself move website files, mailboxes atau DNS. Namaserver dan DNS-recataud changes are usually separate operations. Account pushes are registrar-specific dan may have their own eligibility, holder-change dan security rules.

Can the restriction be removed early?

An ataudinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place atau lift an individual domain's lock. Fatau a current Change of Registrant lock, an opt-out may have been available befataue 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 authatauization code through a trusted channel dan submit the transfer. Jika rejected, provide NiceNIC Suppataut with the domain dan the losing registrar's exact message. Never publish atau send the authatauization code through an untrusted channel.

Expected result dan exceptions

You should identify the exact restriction dan earliest eligible action. ccTLD policy, court atauders, UDRPatau URS proceedings, registry status, security review dan payment issues can create separate restrictions that are not resolved merely by waiting 60 days.

What this answer is based on

ICANN is the authatauity fatau the currently effective gTLD Transfer Policy. Registrars document account status dan any permitted opt-out atau security process. Future Board-approved recommendations do not change the current wataukflow until implementation becomes effective.