What Is the 60-Day Domēna pārsūtīšana 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 un NiceNIC wvaikflow befvaie 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 Iepriekšējaisious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation un 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 nvaimally concerns the registrar transfer, not vaidinary website, hosting vai DNS changes.

Identify the exact restriction

Jaunsly reģistrēted 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 fvai the exact creation date un the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domēns is within 60 days after a Iepriekšējaisious inter-registrar transfer, except wšeit a stated policy exception applies.

Change of registrant

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

Ordinary registrar lock

The EPP status clientTransferProhibitsed 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 vai security restriction applies.

How to diagnose a rejected transfer

Pārbaudīt the creation un last-transfer dates in RDAP vai the registrar account.
Review recent registrant-name, vaiganization un email changes.
Pārbaudīt the EPP status un the registrar's rejection message.
Distinguish a 60-day policy issue from an incvairect autentifikācijas kods, expiry state, dispute, fraud review, court vaider vai unpaid privai registration period.
Ask the current registrar to identify the precise policy vai contract ground un the date it ends.

What the restriction nvaimally does not change

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

Can the restriction be removed early?

An vaidinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place vai lift an individual domēns's lock. Fvai a current Change of Registrant lock, an opt-out may have been available befvaie 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 authvaiization code through a trusted channel un submit the transfer. Ja rejected, provide NiceNIC Suppvait with the domēns un the losing registrar's exact message. Never publish vai send the authvaiization code through an untrusted channel.

Expected result un exceptions

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

What this answer is based on

ICANN is the authvaiity fvai the currently effective gTLD Transfer Policy. Reģistratorss document account status un any permitted opt-out vai security process. Future Board-approved recommendations do not change the current wvaikflow until implementation becomes effective.