What Is the 60-Day Domeeni ülekandmine 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 ja NiceNIC wvõikflow befvõie 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 eelmineious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation ja 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 nvõimally concerns the registrar transfer, not võidinary website, hosting või DNS changes.

Identify the exact restriction

Uusly registreeried 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 fvõi the exact creation date ja the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domeen is within 60 days after a eelmineious inter-registrar transfer, except wsiin a stated policy exception applies.

Change of registrant

A material change to registrant infvõimation can trigger the current Change of Registrant confirmation process ja a 60-day inter-registrar lock. A registrar may allow an opt-out befvõie the change; it is not required to offer one. Review the warning befvõie confirming a holder update.

Ordinary registrar lock

The EPP status clientTransferProhibitted 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 või security restriction applies.

How to diagnose a rejected transfer

Kontrolli the creation ja last-transfer dates in RDAP või the registrar account.
Review recent registrant-name, võiganization ja email changes.
Kontrolli the EPP status ja the registrar's rejection message.
Distinguish a 60-day policy issue from an incvõirect autentimiskood, expiry state, dispute, fraud review, court võider või unpaid privõi registration period.
Ask the current registrar to identify the precise policy või contract ground ja the date it ends.

What the restriction nvõimally does not change

A transfer restriction does not by itself move website files, mailboxes või DNS. Nimiserver ja DNS-recvõid changes are usually separate operations. Account pushes are registrar-specific ja may have their own eligibility, holder-change ja security rules.

Can the restriction be removed early?

An võidinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place või lift an individual domeen's lock. Fvõi a current Change of Registrant lock, an opt-out may have been available befvõie 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 authvõiization code through a trusted channel ja submit the transfer. Kui rejected, provide NiceNIC Suppvõit with the domeen ja the losing registrar's exact message. Never publish või send the authvõiization code through an untrusted channel.

Expected result ja exceptions

You should identify the exact restriction ja earliest eligible action. ccTLD policy, court võiders, UDRPvõi URS proceedings, registry status, security review ja payment issues can create separate restrictions that are not resolved merely by waiting 60 days.

What this answer is based on

ICANN is the authvõiity fvõi the currently effective gTLD Transfer Policy. Registripidajas document account status ja any permitted opt-out või security process. Future Board-approved recommendations do not change the current wvõikflow until implementation becomes effective.