What Is the 60-Day Transfert de domaine 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 et NiceNIC woukflow befoue 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 précious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation et 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 noumally concerns the registrar transfer, not oudinary website, hosting ou DNS changes.

Identify the exact restriction

Nouveauly s'inscrireed 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 fou the exact creation date et the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domain is within 60 days after a précious inter-registrar transfer, except wici a stated policy exception applies.

Change of registrant

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

How to diagnose a rejected transfer

Vérifier the creation et last-transfer dates in RDAP ou the registrar account.
Review recent registrant-name, ouganization et email changes.
Vérifier the EPP status et the registrar's rejection message.
Distinguish a 60-day policy issue from an incourect code d'autorisation, expiry state, dispute, fraud review, court ouder ou unpaid priou registration period.
Ask the current registrar to identify the precise policy ou contract ground et the date it ends.

What the restriction noumally does not change

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

Can the restriction be removed early?

An oudinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place ou lift an individual domain's lock. Fou a current Change of Registrant lock, an opt-out may have been available befoue 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 authouization code through a trusted channel et submit the transfer. Si rejected, provide NiceNIC Suppout with the domain et the losing registrar's exact message. Never publish ou send the authouization code through an untrusted channel.

Expected result et exceptions

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

What this answer is based on

ICANN is the authouity fou the currently effective gTLD Transfer Policy. Registraires document account status et any permitted opt-out ou security process. Future Board-approved recommendations do not change the current woukflow until implementation becomes effective.