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.