What Is the 60-Day Domainin siirto 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 wtaikflow beftaie 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 edellinenious 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 ntaimally concerns the registrar transfer, not taidinary website, hosting tai DNS changes.

Identify the exact restriction

Uusily rekisteröied 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 ftai the exact creation date ja the first eligible date.

Recently transferred gTLD

The current policy permits denial when the verkkotunnus is within 60 days after a edellinenious inter-registrar transfer, except wtässä a stated policy exception applies.

Change of registrant

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

Ordinary registrar lock

The EPP status clientTransferProhibittied 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 tai security restriction applies.

How to diagnose a rejected transfer

Tarkista the creation ja last-transfer dates in RDAP tai the registrar account.
Review recent registrant-name, taiganization ja email changes.
Tarkista the EPP status ja the registrar's rejection message.
Distinguish a 60-day policy issue from an inctairect valtuutuskoodi, expiry state, dispute, fraud review, court taider tai unpaid pritai registration period.
Ask the current registrar to identify the precise policy tai contract ground ja the date it ends.

What the restriction ntaimally does not change

A transfer restriction does not by itself move website files, mailboxes tai DNS. Nimiserver ja DNS-rectaid 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 taidinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place tai lift an individual verkkotunnus's lock. Ftai a current Change of Registrant lock, an opt-out may have been available beftaie 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 authtaiization code through a trusted channel ja submit the transfer. Jos rejected, provide NiceNIC Supptait with the verkkotunnus ja the losing registrar's exact message. Never publish tai send the authtaiization code through an untrusted channel.

Expected result ja exceptions

You should identify the exact restriction ja earliest eligible action. ccTLD policy, court taiders, UDRPtai 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 authtaiity ftai the currently effective gTLD Transfer Policy. Rekisterinpitäjäs document account status ja any permitted opt-out tai security process. Future Board-approved recommendations do not change the current wtaikflow until implementation becomes effective.