You cannot transfer your domain to another registrar if it is under a 60-day ICANN security lock. This global lock is automatically applied whenever a domain is newly registered, previously transferred, or if the registrant's WHOIS contact information is updated. To bypass this, you can push the domain to another account within the same registrar.
What Is the ICANN 60-Day Transfer Lock?
ICANN (Internet Corporation for Assigned Names and Numbers) mandates a 60-day cooling-off period after specific domain events. During this window, registrar-to-registrar transfers are blocked at the registry level.
Critical point: This is not a NameSilo policy. It's a global ICANN rule enforced by every accredited registrar worldwide. Customer support cannot override it. No exceptions exist. The lock is hardcoded at the registry.
The lock applies to the domain itself, not your account. Other domains in your account remain unaffected.
Why It Matters: Hijacking Prevention
The 60-day lock exists to protect domain owners from theft.
If a hacker gains temporary access to your registrar account, they might:
- Change your WHOIS email to their address
- Immediately transfer the domain to a registrar they control
- Disappear with your domain
The 60-day lock stops this attack chain. Even if an attacker changes your contact info, they can't transfer the domain for 60 days, giving you time to detect and reverse the compromise.
Frustrating when you're the legitimate owner? Yes. But it's saved countless domains from theft.
The 3 Triggers (Plus Abuse Holds)
| | |
| | |
Recent registrar transfer | | |
| | |
clientHold (abuse suspension) | | |
New Registration: Just bought the domain? Wait 60 days before transferring out.
Recent Transfer: Just transferred in? Another 60-day wait before you can transfer again.
WHOIS Registrant Change: Updated your name or email? Clock resets to 60 days.
clientHold Status: Domains suspended for abuse, non-payment, or ICANN verification failure cannot transfer. This status must be resolved first, contact support if your domain shows clientHold.
How to Check Your Domain Status
Step 1: Run a WHOIS lookup on your domain.
Step 2: Look for status codes:
- clientTransferProhibited , Locked (registrar or ICANN 60-day)
- clientHold , Suspended, not eligible for transfer
Step 3: Check creation date or last transfer date. Add 60 days to calculate expiry.
Step 4: If immediate ownership change is needed, use account push instead. Common Mistakes
Updating WHOIS before selling: You change the registrant email to the buyer's address, accidentally triggering a 60-day lock. Now neither of you can transfer the domain. Update WHOIS after the transfer completes.
Confusing registrar lock with ICANN lock: Registrar lock (the padlock toggle) is different. You can unlock the padlock; you cannot unlock the ICANN period.
Ignoring clientHold: Domains in clientHold have additional issues. Resolve the underlying problem first.
What This Means for You
Can't wait 60 days? Use NameSilo's Push Domain feature to instantly transfer ownership to another NameSilo account. Pushes bypass the ICANN lock entirely, no waiting, no fees. Planning to transfer to NameSilo? Verify your domain isn't within 60 days of registration or recent transfer first. Check WHOIS status codes before initiating. Frequently Asked Questions
Why is my domain transfer locked?
Within 60 days of registration, previous transfer, or WHOIS change.
Can I bypass the 60-day ICANN lock?
Not for registrar transfers. Use account push instead.
Does changing WHOIS data lock my domain?
Yes. Registrant changes trigger a new 60-day lock.
How do I know when my domain lock expires?
Check the creation/transfer date in WHOIS, add 60 days.
Can I sell a domain during the 60-day lock?
Yes, via account push within the same registrar.
What is an account push vs a transfer?
Push moves domains between accounts at the same registrar; transfer moves between registrars.
Do all registrars have the 60-day lock?
Yes. It's an ICANN mandate.
How do I unlock my domain?
Toggle off registrar lock. The ICANN lock cannot be removed. 
.png&w=2048&q=75)
.png&w=3840&q=75)
