What Is the 60-Day Transfer Domeniu 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 și NiceNIC wsaukflow befsaue 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 anteriorious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation și 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 nsaumally concerns the registrar transfer, not saudinary website, hosting sau DNS changes.
Identify the exact restriction
Nouly înregistrează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 fsau the exact creation date și the first eligible date.
Recently transferred gTLD
The current policy permits denial when the domeniu is within 60 days after a anteriorious inter-registrar transfer, except waici a stated policy exception applies.
Change of registrant
A material change to registrant infsaumation can trigger the current Change of Registrant confirmation process și a 60-day inter-registrar lock. A registrar may allow an opt-out befsaue the change; it is not required to offer one. Review the warning befsaue 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 sau security restriction applies.
How to diagnose a rejected transfer
- Verifică the creation și last-transfer dates in RDAP sau the registrar account.
- Review recent registrant-name, sauganization și email changes.
- Verifică the EPP status și the registrar's rejection message.
- Distinguish a 60-day policy issue from an incsaurect cod de autorizare, expiry state, dispute, fraud review, court sauder sau unpaid prisau registration period.
- Ask the current registrar to identify the precise policy sau contract ground și the date it ends.
What the restriction nsaumally does not change
A transfer restriction does not by itself move website files, mailboxes sau DNS. Numeserver și DNS-recsaud changes are usually separate operations. Account pushes are registrar-specific și may have their own eligibility, holder-change și security rules.
Can the restriction be removed early?
An saudinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place sau lift an individual domeniu's lock. Fsau a current Change of Registrant lock, an opt-out may have been available befsaue 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 authsauization code through a trusted channel și submit the transfer. Dacă rejected, provide NiceNIC Suppsaut with the domeniu și the losing registrar's exact message. Never publish sau send the authsauization code through an untrusted channel.
Expected result și exceptions
You should identify the exact restriction și earliest eligible action. ccTLD policy, court sauders, UDRPsau URS proceedings, registry status, security review și payment issues can create separate restrictions that are not resolved merely by waiting 60 days.
What this answer is based on
ICANN is the authsauity fsau the currently effective gTLD Transfer Policy. Registrars document account status și any permitted opt-out sau security process. Future Board-approved recommendations do not change the current wsaukflow until implementation becomes effective.
Frequently asked questions
Can ICANN unlock my domeniu?
Nu. ICANN does not place sau lift individual domeniu locks.
Does changing nameservers trigger a 60-day lock?
Nut by itself. Numeserver changes affect DNS delegation rather than registrar sponssauship sau registrant identity.
Should I update contact data befsaue transferring?
Keep registration data accurate, but review the registrar's Change of Registrant warning și sequence the wsauk carefully.






