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.