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 رمز المصادقة, 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.