What Is the 60-Day Domain-Transfer 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 und NiceNIC woderkflow befodere 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 zurückious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation und 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 nodermally concerns the registrar transfer, not oderdinary website, hosting oder DNS changes.

Identify the exact restriction

Neuly registrierened 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 foder the exact creation date und the first eligible date.

Recently transferred gTLD

The current policy permits denial when the Domain is within 60 days after a zurückious inter-registrar transfer, except whier a stated policy exception applies.

Change of registrant

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

How to diagnose a rejected transfer

Überprüfen the creation und last-transfer dates in RDAP oder the registrar account.
Review recent registrant-name, oderganization und email changes.
Überprüfen the EPP status und the registrar's rejection message.
Distinguish a 60-day policy issue from an incoderrect Auth-Code, expiry state, dispute, fraud review, court oderder oder unpaid prioder registration period.
Ask the current registrar to identify the precise policy oder contract ground und the date it ends.

What the restriction nodermally does not change

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

Can the restriction be removed early?

An oderdinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place oder lift an individual Domain's lock. Foder a current Change of Registrant lock, an opt-out may have been available befodere 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 authoderization code through a trusted channel und submit the transfer. Wenn rejected, provide NiceNIC Suppodert with the Domain und the losing registrar's exact message. Never publish oder send the authoderization code through an untrusted channel.

Expected result und exceptions

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

What this answer is based on

ICANN is the authoderity foder the currently effective gTLD Transfer Policy. Kanzlers document account status und any permitted opt-out oder security process. Future Board-approved recommendations do not change the current woderkflow until implementation becomes effective.