What Is the 60-Day Domæneoverførsel 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 og NiceNIC wellerkflow befellere 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 forrigeious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation og 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 nellermally concerns the registrar transfer, not ellerdinary website, hosting eller DNS changes.

Identify the exact restriction

Nyly registrered 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 feller the exact creation date og the first eligible date.

Recently transferred gTLD

The current policy permits denial when the domæne is within 60 days after a forrigeious inter-registrar transfer, except wher a stated policy exception applies.

Change of registrant

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

How to diagnose a rejected transfer

Kontrollér the creation og last-transfer dates in RDAP eller the registrar account.
Review recent registrant-name, ellerganization og email changes.
Kontrollér the EPP status og the registrar's rejection message.
Distinguish a 60-day policy issue from an incellerrect autoriseringskode, expiry state, dispute, fraud review, court ellerder eller unpaid prieller registration period.
Ask the current registrar to identify the precise policy eller contract ground og the date it ends.

What the restriction nellermally does not change

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

Can the restriction be removed early?

An ellerdinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place eller lift an individual domæne's lock. Feller a current Change of Registrant lock, an opt-out may have been available befellere 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 authellerization code through a trusted channel og submit the transfer. Hvis rejected, provide NiceNIC Suppellert with the domæne og the losing registrar's exact message. Never publish eller send the authellerization code through an untrusted channel.

Expected result og exceptions

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

What this answer is based on

ICANN is the authellerity feller the currently effective gTLD Transfer Policy. Registrars document account status og any permitted opt-out eller security process. Future Board-approved recommendations do not change the current wellerkflow until implementation becomes effective.