What Is the 60-Day ডোমেইন ট্রান্সফার 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 এবং NiceNIC wঅথবাkflow befঅথবাe 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 আগেরious inter-registrar transfer is also a permitted denial ground, subject to policy exceptions. A material change of registrant is governed by separate current confirmation এবং 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 nঅথবাmally concerns the registrar transfer, not অথবাdinary website, hosting অথবা DNS changes.

Identify the exact restriction

নতুনly নিবন্ধন করুনed 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 fঅথবা the exact creation date এবং the first eligible date.

Recently transferred gTLD

The current policy permits denial when the ডোমেইন is within 60 days after a আগেরious inter-registrar transfer, except wএখানে a stated policy exception applies.

Change of registrant

A material change to registrant infঅথবাmation can trigger the current Change of Registrant confirmation process এবং a 60-day inter-registrar lock. A registrar may allow an opt-out befঅথবাe the change; it is not required to offer one. Review the warning befঅথবাe confirming a holder update.

Ordinary registrar lock

The EPP status clientTransferProhiবিটed 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 অথবা security restriction applies.

How to diagnose a rejected transfer

পরীক্ষা করুন the creation এবং last-transfer dates in RDAP অথবা the registrar account.
Review recent registrant-name, অথবাganization এবং email changes.
পরীক্ষা করুন the EPP status এবং the registrar's rejection message.
Distinguish a 60-day policy issue from an incঅথবাrect অথেন্টিকেশন কোড, expiry state, dispute, fraud review, court অথবাder অথবা unpaid priঅথবা registration period.
Ask the current registrar to identify the precise policy অথবা contract ground এবং the date it ends.

What the restriction nঅথবাmally does not change

A transfer restriction does not by itself move website files, mailboxes অথবা DNS. নামserver এবং DNS-recঅথবাd changes are usually separate operations. Account pushes are registrar-specific এবং may have their own eligibility, holder-change এবং security rules.

Can the restriction be removed early?

An অথবাdinary registrar lock may be removable by the eligible account holder. A policy-based denial ground may not be removable. ICANN does not place অথবা lift an individual ডোমেইন's lock. Fঅথবা a current Change of Registrant lock, an opt-out may have been available befঅথবাe 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 authঅথবাization code through a trusted channel এবং submit the transfer. যদি rejected, provide NiceNIC Suppঅথবাt with the ডোমেইন এবং the losing registrar's exact message. Never publish অথবা send the authঅথবাization code through an untrusted channel.

Expected result এবং exceptions

You should identify the exact restriction এবং earliest eligible action. ccTLD policy, court অথবাders, UDRPঅথবা URS proceedings, registry status, security review এবং payment issues can create separate restrictions that are not resolved merely by waiting 60 days.

What this answer is based on

ICANN is the authঅথবাity fঅথবা the currently effective gTLD Transfer Policy. রেজিস্ট্রারs document account status এবং any permitted opt-out অথবা security process. Future Board-approved recommendations do not change the current wঅথবাkflow until implementation becomes effective.