Transferring a domain between registrars is a common domain management operation — perhaps due to price increases, poor service, or the desire to centralize management. Whatever the reason, correct transfer procedures ensure safe migration with zero service interruption.
Why Transfer Registrars
Common reasons: better pricing, improved service quality, centralized management, security concerns, advanced features (API, bulk operations).
Key facts: service won’t be interrupted (if done correctly), most registrars include one year renewal with transfer-in, process takes 5-7 days, requires current registrar cooperation.
Pre-Transfer Restrictions
ICANN 60-Day Lock: Cannot transfer if registered less than 60 days ago, registrant info changed recently, or transferred in less than 60 days ago. Other restrictions: active UDRP disputes, redemption/pending delete status, court-ordered freezes.
Complete Transfer Steps
Step 1: Create Account at New Registrar
Complete profile, bind payment, enable 2FA.
Step 2: Unlock Domain at Current Registrar
Find “Transfer Lock” setting and disable it.
Step 3: Obtain Auth Code
Request from current registrar; usually emailed to registrant; valid for several days.
Step 4: Initiate Transfer at New Registrar
Enter domain name, input Auth Code, choose DNS options, pay transfer fee (typically one year’s renewal).
Step 5: Confirm Transfer
Current registrar emails confirmation to registrant. Click “confirm transfer” to expedite (otherwise auto-completes in 5-7 days).
Step 6: Verify Success
Confirm domain appears in new account, check DNS records, verify website and email function, confirm WHOIS update.
Ensuring Zero DNS Downtime
Option 1 (Recommended): Use third-party DNS (Cloudflare, Route 53) — completely independent of registrar; transfer doesn’t affect DNS.
Option 2: Pre-configure DNS at new registrar — copy all records before transfer.
Option 3: Manual post-transfer DNS migration — may have brief downtime depending on TTL.
Common Transfer Failures
| Issue | Cause | Solution |
|---|---|---|
| Invalid Auth Code | Expired or copy error | Request new Auth Code |
| Transfer rejected | Domain still locked | Unlock at current registrar |
| Transfer timeout | Confirmation not completed | Re-initiate transfer |
| 60-day lock | Recent domain changes | Wait for lock to expire |
| Invalid WHOIS email | Can’t receive confirmation | Update WHOIS email first |
Post-Transfer Checklist
- Domain visible in new registrar account
- All DNS records complete (A, CNAME, MX, TXT)
- Website accessible
- Email working
- WHOIS info correct
- Domain lock re-enabled
- Auto-renewal enabled
- 2FA configured
Conclusion
Domain registrar transfer is a standardized process that’s safe when following proper steps: Unlock → Get Auth Code → Initiate transfer at new registrar → Confirm → Verify. The key concern is DNS continuity — using third-party DNS is the simplest solution. After transfer, remember to re-enable domain lock, auto-renewal, and security settings at the new registrar.