Changing domain registrars: transfer locks, authorization codes and keeping DNS working

If you want to manage your domains in one account or move to a registrar that is easier to use, you usually do not need to rebuild your entire website. This work primarily hands the domain's registration management to another service. Your existing web host and mailboxes can remain where they are, provided the relevant DNS services continue to work.

Divide this handover into two checklists: one for who manages the domain, when it expires and how it renews; another for where the name currently directs website and email traffic. Check both, so you do not end up seeing the domain in your new account while customers cannot open your site or send you email.

Confirm that a registrar transfer is what you need

Changing web hosts, changing DNS hosting, changing the domain registrant and transferring to another registrar are different operations. If you only want the existing domain to use a new host, you may only need to adjust the website's DNS records. A registrar transfer is appropriate when you want to manage the same domain on another platform. Confirm your purpose first to avoid starting unnecessary changes at the same time.

The new registrar must also support your domain extension and its current status. Alongside the transfer-in fee, check subsequent renewals, currency, payment methods and DNS features. Some services impose their own conditions on nameserver use. Comparing only the first year's price does not establish that every existing setting can remain after the transfer.

1. Identify the current registrar, domain extension, expiration date and management account.
2. Confirm that the new registrar accepts the domain, and read its transfer-in and renewal conditions.
3. Decide whether DNS will change at the same time; if so, schedule a separate DNS handover.

Check eligibility and the reason for a lock, not just the unlock button

For generic top-level domains covered by ICANN policy, the official policy in effect on the verification date still listed sixty-day restrictions related to initial registration, a previous registrar transfer and certain changes of registrant. The conditions and available options differ between these situations. Simply reaching sixty days is not the sole test that guarantees every domain can be transferred.

A normal transfer lock that the registrant can remove is also different from restrictions caused by policy, disputes or other domain statuses. Check the reason shown in the account and the date on which transfer becomes possible; ask the existing registrar to explain any inconsistent information. If you are already preparing a transfer, do not casually change registrant details without reading the consequences: some changes can trigger a new lock.

The ICANN process in this article cannot be applied directly to every country-code domain. For .tw, .台灣 and other extensions, check the current rules of the registry and the registrar handling the request. If a domain is expired, in redemption or in dispute, first establish how that status must be handled, then plan the transfer. Do not wait for the website to stop working before trying a registrar change as the remedy.

Save DNS settings and email dependencies before transferring

Save the nameservers, website A or AAAA records, CNAME records, email MX records and related TXT records in a readable list. Include subdomains and verification records too. This list is your handover baseline: record each current value, its purpose and the responsible service. A screenshot of the homepage alone cannot later tell you which email verification record was missed.

Keeping the same nameserver names does not guarantee that the old registrar will continue providing DNS after the domain leaves. Namecheap's official transfer-in guidance, for example, distinguishes externally hosted DNS from the old registrar's default DNS. Ask the original service whether DNS will remain available after transfer. If DNS must change, create and verify the complete set of records before arranging the registration transfer.

For a domain with DNSSEC enabled or custom nameservers, separately record those settings and follow both providers' handover documentation. Do not treat switching off every security feature as a universal step. Understand which setting needs updating, when to verify it and how to restore normal protection. If you are unfamiliar with the process, give both support teams the settings list to check.

Get the authorization code, then apply through the new registrar

An authorization code may be called an Auth-Code, AuthInfo, EPP code or transfer code. It helps confirm authorization for the transfer. Obtain it through the existing registrar's account process, and remove the transfer lock you are allowed to change when required. Enter the code only in the verified official transfer-in interface of the new registrar. Do not include it in public screenshots or ordinary collaboration documents.

Enter the complete domain at the new registrar, check the spelling and extension, then enter the authorization code and confirm the payment items. During transfer, you may need to respond to confirmations or exceptions. Sign in directly to the official account to check the status, and ensure the current contact email can receive messages. If an email does not arrive, check spam and account notifications before repeatedly submitting the application.

1. Sign in to the existing registrar, confirm eligibility, obtain the authorization code and remove the transfer lock as instructed.
2. Sign in to the new registrar's transfer-in page and check the domain, hosting conditions, fees and application summary.
3. After submitting, save the order or case identifier and track the status and required confirmations on both sides.

Handle waiting and failures according to the actual status

Payment completed, application submitted and registrar changed are different states. Do not close the old account just because a payment was charged, or cancel and restart merely because nothing changed for one day. Monitor the expected processing time shown by the service. If it is exceeded, give support the case number, status and error message so they can investigate the same application.

If the authorization code is reported as incorrect, check for extra spaces, whether you are using the latest generated code and whether it belongs to the correct domain. For a lock, registrant confirmation or domain-status issue, address that specific cause; generating another code may not help. Unless the official procedure requires it, do not submit transfer-in requests for the same domain to several registrars at once.

If the existing website or mailbox suddenly stops working during transfer, check DNS responses and the original DNS service's status before investigating the web host. A registration transfer is not a deployment of website content; evidence of failures differs between the two. Keep the time of the outage and a change log to help identify whether the problem lies in the application, DNS handover or another service.

After completion, check management, DNS and billing

Confirm that the new registrar account can manage the domain, and use the applicable official lookup service to check the registrar status. Then check the nameservers and important records, open the website from different networks, and send an email from an external mailbox and reply to it. A transfer-completion notice confirms the registration handover; it does not replace website and email acceptance checks.

Recheck the expiration date, automatic renewal, payment method, contact details and account protection. Whether the transfer-in fee extends the registration, by how much, and what exceptions apply after a recent renewal all depend on the domain and service conditions. Do not state that a transfer always adds one free year. Put the next renewal date in your calendar and keep the payment and transfer records.

Finally, list any hosting, DNS, email or other domains that still remain in the old account. Stop only the items you no longer need so that you do not cancel services still in use. Keep an updated domain-handover sheet: the next person taking over will then know who is responsible for the registrar, DNS and web hosting.

Read the full description

An original four-step diagram: confirm transfer eligibility, save the DNS and email checklist, apply with an authorization code, then verify registration management, the website and email.

Domain registration and management basics

Understanding DNS records and faults

Domain and hosting renewal checklist

• Tutorials
• Apps & software
• Websites & e-commerce
• Domains, hosting & front-end