What Is the 60-Day Trasferimento Dominio 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 e NiceNIC wokflow befoe 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 precedenteious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation e 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 nomally concerns the registrar transfer, not odinary website, hosting o DNS changes.

Identify the exact restriction

Nuovoly registrareed 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 fo the exact creation date e the first eligible date.

Recently transferred gTLD

The current policy permits denial when the dominio is within 60 days after a precedenteious inter-registrar transfer, except wqui a stated policy exception applies.

Change of registrant

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

How to diagnose a rejected transfer

Verifica the creation e last-transfer dates in RDAP o the registrar account.
Review recent registrant-name, oganization e email changes.
Verifica the EPP status e the registrar's rejection message.
Distinguish a 60-day policy issue from an incorect codice di autorizzazione, expiry state, dispute, fraud review, court oder o unpaid prio registration period.
Ask the current registrar to identify the precise policy o contract ground e the date it ends.

What the restriction nomally does not change

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

Can the restriction be removed early?

An odinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place o lift an individual dominio's lock. Fo a current Change of Registrant lock, an opt-out may have been available befoe 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 authoization code through a trusted channel e submit the transfer. Se rejected, provide NiceNIC Suppot with the dominio e the losing registrar's exact message. Never publish o send the authoization code through an untrusted channel.

Expected result e exceptions

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

What this answer is based on

ICANN is the authoity fo the currently effective gTLD Transfer Policy. Registrars document account status e any permitted opt-out o security process. Future Board-approved recommendations do not change the current wokflow until implementation becomes effective.