Domains · Practical guide
How to transfer a domain registrar without breaking your website
A registrar transfer changes who manages the domain registration. It does not need to change the nameservers or hosting, but an accidental DNS change can take services offline.
First published · OlaCheap technical reference · Check current provider instructions before changing production services
Separate the three things people often confuse
The registrar stores the registration and controls renewal. The authoritative DNS provider publishes records such as A, AAAA, MX and TXT. The hosting company delivers the website or mail service. All three roles can be held by different companies. A change to one does not automatically require changing the other two.
Before taking any action, record the current registrar, the nameservers shown by the registry, the DNS zone contents and where website and email traffic actually go. This baseline tells you whether a later issue is caused by a transfer or by an unrelated hosting change.
Verification checklist
- Save the nameserver list and DNS export
- Record all MX, SPF, DKIM, DMARC and verification TXT records
- Confirm the renewal and expiry dates
Check transfer eligibility and authorization
Registrars commonly require the domain to be unlocked and an authorization code (sometimes called EPP or auth code) for eligible transfers. Recent registration, transfers or registrant changes may impose restrictions depending on the applicable registry and ICANN policy. Do not remove security controls until you know the receiving registrar's specific steps.
The receiving registrar should show the domain name, charges and expected transfer consequences before submission. Confirm which account and contact will own the domain after transfer. Keep approval messages until the process finishes, and be suspicious of unsolicited requests to surrender an auth code.
Keep DNS unchanged unless a migration is intentional
A registrar transfer can complete while the existing authoritative nameservers continue serving the same DNS zone. That is normally the least disruptive approach. If you also plan to change nameservers, do it as a separate, tested change with a complete zone copy.
After the transfer, compare the nameservers again, and check the website over HTTPS, mail delivery and any DNS-based ownership proofs. Monitor the domain for at least one full normal business cycle, including messages from outside your own organization.
Verification checklist
- Do not simultaneously transfer the registrar and change DNS unless necessary
- Retest inbound and outbound mail after completion
- Verify registrar lock, recovery options and renewal settings again
Know when not to transfer
If the domain expires very soon, if you cannot receive the authorization email, or if business-critical DNS records are undocumented, fix those blockers first. Moving a registrar is not the fastest method to move a website and should not be used as a shortcut to bypass ownership or security controls.
For country-code domains, registry procedures may differ materially from generic top-level domains. Use the actual receiving registrar's requirements rather than an all-purpose checklist that assumes every TLD behaves like .com.
Next practical step
This article is an educational checklist, not a claim of live product availability or a substitute for current documentation from your provider.
Check OlaCheap domain transfer options →References and official documentation
These materials help verify procedures. Provider requirements may change, and this guide does not claim first-hand security certification or independent testing of third-party products.