How to Transfer a Domain Name Without Downtime

What a Domain Name Transfer Actually Moves

The first thing I check in a domain transfer is not the transfer button. I check what the customer expects to move. A domain name transfer changes the registrar responsible for the domain; it does not automatically move website files, databases, mailboxes, or a hosting account to another server.

I have seen site owners discover this only after the transfer completed, expecting the website to appear in a new hosting account by itself. It does not work that way.

You can change hosting while keeping the domain at the same registrar. You can also move only the domain while leaving hosting where it is. DNS is managed separately from both. I explained the relationship between these three pieces in What Are Domain Names, DNS and Web Hosting?.

Let me put it this way: moving a domain is like changing the estate agent responsible for your house. The website is the house; the domain is the address visitors use. Changing the agency does not make the furniture move.

Requirements for a domain name transfer

Check the domain’s status before starting. The following usually applies to common generic top-level domains such as .com and .net. Country-code domains can have different rules, so check the procedure required by the relevant registrar for domains such as .tr.

• The domain must not be expired or suspended.
• The transfer lock must be disabled.
• You must be able to obtain the transfer authorization code, also called an EPP or AuthInfo code.
• The domain must usually have passed the 60-day waiting period after initial registration or its last transfer.
• You must have access to the administrative or registrant contact email address.
• WHOIS privacy or contact verification must not prevent transfer approval.

The 60-day rule is not identical for every extension or registration event. A change of registrant can create another 60-day transfer lock with some registrars. Do not rely only on a panel showing the transfer lock as disabled; ask the registrar to confirm that the domain is eligible.

Rules vary. That small check can save a week of back-and-forth.

Transfer and DNS changes are different things

When you move a domain between registrars, its nameservers are usually preserved. Your DNS service can continue operating at the old provider. Some registrars assign different default nameservers during account setup, though, so take a screenshot and save the current values as text before you begin.

For any business that uses email, check the MX, SPF, DKIM, and DMARC records carefully. The website may load perfectly while one missing MX record causes incoming mail to disappear or go to the wrong server. For practical examples, see DNS Record Types Explained: Practical Guide: A, AAAA, MX, CNAME, TXT, SRV and CAA.

Step-by-step domain name transfer

1. Identify the current registrar

Start by finding out which registrar holds the domain and when its registration expires. Your hosting company and registrar may be the same business, but they do not have to be. If an agency purchased the domain, establish who controls the panel, who can obtain the authorization code, and which person owns the registrant email address.

From a terminal, you can check basic details with whois or dig. WHOIS privacy may hide personal information; that is normal.

whois exampledomain.com

dig NS exampledomain.com
dig MX exampledomain.com

The first command returns registration and expiry information. The other two show the domain’s DNS and mail servers. When a DNS ticket reaches me, I do not trust the panel alone; I query the domain with dig from a different network.

Panels show intentions. DNS queries show what is actually published.

2. Disable the transfer lock

Depending on the registrar, this may be called Registrar Lock, Transfer Lock, or Domain Lock. If the lock remains enabled, the new registrar can submit a request but the transfer will not complete.

Starting the transfer immediately after disabling the lock usually works. Some panels need a few minutes to process the change. If the new registrar still reports a lock while the old panel says it is disabled, ask support to verify the status.

You can also inspect the domain status codes:

whois exampledomain.com | grep -iE 'clientTransferProhibited|Domain Status'

If clientTransferProhibited appears, the transfer lock is still active. The command may return nothing, especially with privacy-focused registration services, so the registrar’s panel and support team remain authoritative.

3. Obtain the EPP or AuthInfo code

The EPP code is the password-like authorization value for the domain transfer. Some companies display it in the panel, some send it to the registered email address, and others require a support request. Make sure no leading or trailing spaces come along when you copy it. A copied line break is a surprisingly common cause of an invalid authorization code error.

Do not send this code to just anyone. Possessing it may not always be enough to complete a transfer, but it is still sensitive domain-management information. If it arrived by email, store or delete that message safely after the transfer is finished.

I treat the code like a temporary password.

4. Create the transfer request at the new registrar

Enter the domain and EPP code on the new registrar’s transfer page. For many generic extensions, the transfer fee includes a one-year renewal. Fees vary by registrar and extension, and some specialized extensions do not add a renewal year, so read the payment screen carefully.

Enter only the domain name. Do not add https://, www, or a subdomain. exampledomain.com is correct; https://www.exampledomain.com is not the format the transfer form expects.

5. Watch for approval emails

During the transfer, an approval email may go to the current registrant, the administrative contact, or the new registrar. Check spam and junk folders if you do not see it. If the address in the domain’s contact information is obsolete, update it first.

Some transfers complete automatically after a waiting period if nobody objects. Others do not move forward until explicit approval arrives. For an e-commerce domain that needs to move promptly, verify the approval link safely in the registrar panel instead of leaving the message unattended.

Read the sender and destination carefully. A familiar-looking email is not proof that the request is genuine.

6. Wait for the transfer to complete

A transfer for a common extension often finishes within a few days. The timing depends on how quickly the old registrar approves it and whether the registration details need verification. Do not start another transfer while one is in progress; overlapping requests make a simple job harder to diagnose.

The website will normally continue working during the transfer. As long as the nameservers remain unchanged, visitors keep using the same DNS service and reaching the same hosting server. Once the transfer completes, check the nameservers, auto-renewal, DNSSEC, and contact information in the new panel.

Prepare DNS and hosting separately

There is no reason to squeeze a domain transfer and a hosting migration into the same day. Planning them separately makes it much easier to identify which layer failed if something goes wrong.

If hosting is changing too, prepare the site on the new server first. Export the WordPress database, copy the files, and check the PHP version and plugins. I do not touch a WordPress site before migration or updates without running wp db export.

cd /var/www/html
wp db export ../backup-$(date +%F).sql
wp core version
wp plugin list --update=available

The first command enters the site directory. The second exports the database to a date-stamped file; the last two show the WordPress and plugin status.

Do not treat a file on the same disk as a complete backup. I once found an allegedly available migration backup directory completely empty. Since then, I trust no copy that has not been restored in a test. A backup that cannot be restored is only a confident-looking directory.

If DNS will also change, lower the relevant records’ TTL to 300 seconds around 48 hours before the migration. That reduces the time old records remain cached after the change. This is about DNS changes, not the registrar transfer itself.

A WordPress migration surprise in wp_options

During one customer’s hosting migration, the files and database copied without errors. Yet the site opened at the new address and redirected to the old one a few seconds later. The settings shown in the hosting panel looked correct.

When I inspected the database, I found that one of the siteurl and home values in the wp_options table still pointed to the old address. The customer had changed it manually earlier. A small value created a very large panic.

I exported the database first, then corrected the values with WP-CLI:

wp db export ../before-search-replace-$(date +%F-%H%M).sql
wp search-replace 'https://old-exampledomain.com' 'https://exampledomain.com' --all-tables-with-prefix --dry-run
wp search-replace 'https://old-exampledomain.com' 'https://exampledomain.com' --all-tables-with-prefix

The first command creates a rollback copy. --dry-run reports the number of matches without changing anything; the final command applies the replacement. WP-CLI handles serialized data more safely than a plain SQL text replacement, but I still inspect the dry-run output before proceeding.

Since that incident, I test more than the homepage after a migration: the login screen, contact forms, and the complete checkout flow as well. A successful HTTP 200 is not the same thing as a working store.

Will the website and email go offline?

With proper preparation, usually not. A domain name transfer happens at the registrar level, while the web server remains in place through the existing DNS records. The situation changes if you also move DNS or if the new provider has an incomplete DNS zone.

Export the current DNS zone before the change, or at least record these entries:

• A and AAAA records
• The CNAME or A record for www
• All MX records for incoming mail
• TXT records used for SPF, DKIM, and DMARC
• TXT records used by Google Search Console, payment services, and verification tools
• Subdomains used by external services

Compare the records after creating the zone at the new DNS provider. Loading the main domain is not enough. Check mail.exampledomain.com, the administration panel, and any API endpoints your site uses.

Email deserves its own test. A working homepage cannot tell you if your MX record is missing.

Checks after the transfer

Do not consider the job finished when the completion email arrives. Review these items one by one at the new registrar:

Be careful with DNSSEC. If an old DS record does not match the new DNSSEC signature after a nameserver change, the domain may stop resolving. Changing the DS record before the new keys are ready can interrupt both the website and email.

Query different public resolvers to compare what they see:

dig @1.1.1.1 exampledomain.com A +short
dig @8.8.8.8 exampledomain.com MX +short
dig +trace exampledomain.com

The first two commands compare records returned by different public DNS resolvers. dig +trace follows the chain from the root servers to the authoritative DNS servers. When DNS is being blamed, this output tells me more than a screenshot of a control panel.

If DNSSEC is enabled, I also check the delegation and validation path rather than assuming that a green panel icon means everything is healthy.

What to do if the transfer is rejected

Errors such as Transfer prohibited, invalid authorization code, and domain not eligible usually have a specific cause.

• The transfer lock is still enabled.
• The EPP code is incomplete, expired, or incorrectly copied.
• The domain was registered or transferred recently.
• The contact email address has not been verified.
• The domain has expired and the registrar has blocked the transfer.
• The extension has a special transfer procedure.

Send the exact error message to support. Instead of saying only that it does not work, include the domain, error code, transfer-lock status, and time when the request was created. Keep auto-renewal enabled at the old registrar until the transfer finishes; a delayed process should not allow the domain to expire.

Exact output beats a long description of a button that appears not to work.

Security and payment details

Inspect emails requesting a transfer code carefully. Domain transfers are commonly used as a pretext for phishing. Rather than clicking the message link, type the registrar’s address into your browser and sign in there. If your email account is compromised, an attacker may approve the transfer before you see the request, so enable two-factor authentication on the domain account.

Review your payment and renewal settings too. Auto-renewal may be enabled at the new registrar, but card details do not move with the domain. Adding the expiry date to your calendar is simple, but I still encounter accounts protected by passwords such as admin and 123456 in support tickets. That is a much larger risk than the transfer itself.

Do not close the old registrar account immediately. You may still need old invoices, DNS history, security notices, or access to other domains. Keep access for at least a few weeks and archive the records you need.

I have seen a renewal notice arrive at an address nobody monitored. The domain was fine that time, but the lesson was not subtle: ownership contact details need the same attention as server credentials.

When is changing nameservers enough?

If your only goal is to run the website on another hosting account, you do not need to change registrars. Prepare the new hosting server, then update the A record or move the nameservers to the new DNS provider.

A transfer makes more sense when you want billing in one place, better support, domain ownership under a company account, or a different set of registrar services. Decide which problem you are solving first. Buying new hosting does not obligate you to move the domain as well.

A domain name transfer itself does not lower search rankings. Indirect problems can appear if the website becomes unreachable during a DNS or hosting change, redirects are wrong, or email-verification records disappear. For the connection between hosting choices and search visibility, see Hosting and SEO: Myths vs Reality About IPs, Location, CDNs and HTTP/2/3.

Sometimes the safest transfer is the one you decide not to combine with a hosting move.

Frequently asked questions

How long does a domain name transfer take?

A transfer for a common extension can finish within a few days. Approval by the old registrar, a valid EPP code, and the extension’s own rules all affect the timing.

Does the website go offline during a domain transfer?

Usually not if the nameservers and DNS records remain unchanged. If DNS or hosting is also moving, prepare the records in advance and test from external networks.

What is an EPP code, and where do I get one?

An EPP or AuthInfo code authorizes the domain to move to another registrar. You can usually obtain it from the current registrar’s panel or request it at the registered contact address.

Does a domain name transfer add one year?

For many extensions, including .com, the transfer fee includes a one-year renewal. The rule is not universal, so check the new registrar’s transfer terms before paying.