How to Transfer a Domain Name Without Downtime

Map Your DNS Before a Domain Transfer

When I prepare a domain transfer, I open a terminal before I open the registrar’s transfer page. Last year, I checked a customer’s NS and A records and confirmed that the website pointed to the right VPS. Then I queried AAAA and found an IPv6 address belonging to a server that had been retired years earlier.

That old record was still answering. Clients with IPv6 could have reached the dead server while everyone else saw a perfectly healthy website. We removed it before starting the transfer. Small checks prevent long nights.

A domain transfer moves the registration from one registrar to another. It does not move your website files, database, mailboxes, or server. The company responsible for managing the registration changes; the services using the domain do not have to.

That distinction causes much of the confusion during a move. Your DNS records, mail service, and VPS can all stay exactly where they are while the domain changes registrars. If you also change DNS providers on the same day, finding the source of a failure becomes much harder.

I treat these as two separate jobs: first move the registration while keeping DNS unchanged, then move DNS later if there is a good reason. It takes a little longer. Still faster than hunting for missing mailboxes at midnight.

A Domain Transfer Is Not a DNS Change

After a transfer completes, the nameservers usually remain unchanged. If the domain uses ns1.exampledns.com and ns2.exampledns.com, the new registrar takes over the registration while retaining that nameserver information. The website should continue resolving to the same server.

Usually is not always. Check the current state before you begin:

dig +short NS example.com
dig +short A example.com
dig +short AAAA example.com
dig +short MX example.com

dig +short keeps the answer readable. An NS record identifies the authoritative DNS servers, an A record points to an IPv4 address, an AAAA record points to IPv6, and an MX record identifies the servers that accept mail.

After the transfer, I run the same queries and compare the results. If something changed, I check the new registrar’s DNS screen first. Restarting the server will not repair a DNS record. With DNS problems, use the right query before reaching for a reboot.

What You Need Before Starting

Not every domain can be transferred at any time. I check a few things before opening the transfer form.

Is the Transfer Lock Disabled?

Most domains have a transfer lock to prevent unauthorized moves. Your registrar may call it Registrar Lock, Transfer Lock, or ClientTransferProhibited.

Disable the lock before starting the transfer. Some panels show the change within minutes; others take longer to update the registrar system. If the transfer still cannot start, check the domain’s RDAP or WHOIS output after disabling the lock.

Do not assume that a button labelled “unlocked” means the registry has already updated. Give it time, then check again.

The EPP or Auth Code

The EPP code is the authorization code for a domain transfer. Some registrars call it an AuthInfo Code or simply a Transfer Code. The new registrar asks for it during the transfer order.

If possible, display the code in the registrar panel instead of having it sent by email. Copy it carefully and avoid adding spaces or line breaks. I normally paste it into a plain-text editor first, which makes invisible characters easier to spot.

I learned that habit after once blaming a transfer system for rejecting a code I had copied badly. The system was innocent. My clipboard was not.

Access to the Domain Owner’s Email

Transfer approval messages may go to the administrative or registrant email address held for the domain. If that mailbox is no longer in use, the transfer can sit waiting indefinitely. With privacy protection enabled, the address may also be a masked mailbox rather than the real destination.

Disabling privacy protection before a transfer is not always required; the answer depends on the registrar and the top-level domain. You do need to know exactly where the approval message will arrive. Domains still registered to a former agency employee are a surprisingly common place to lose time.

The 60-Day Transfer Restriction

A newly registered domain usually cannot be transferred during its first 60 days under the rules used by many generic top-level domains. A 60-day restriction may also follow certain changes to registrant or contact details. This is common for domains covered by ICANN rules, but country-code domains do not all follow the same process.

If you bought the domain recently or changed its owner information, an error in the transfer panel may be expected. Ask the registrar’s support team to confirm the reason for the restriction and its end date in writing.

My Pre-Transfer Checklist

Before I touch the transfer screen, I run through a short checklist. It does not make the transfer itself faster; it reduces the chance of forgetting something that matters.

• Check the domain’s expiration date and auto-renewal status.
• Disable the transfer lock.
• Obtain the EPP or Auth Code.
• Confirm that you can access the domain owner’s email address.
• Record the current NS, A, AAAA, CNAME, MX, TXT, and CAA records.
• Test the website and mail services.
• Check the transfer price and the renewal period added after the transfer.
• Avoid changing the domain owner’s contact details during the transfer.

If the DNS provider supports an export, save a copy. If it does not, a text file is more useful than a screenshot. I normally keep something like this:

example.com.       3600  IN  A     203.0.113.25
www.example.com.   3600  IN  CNAME example.com.
example.com.       3600  IN  MX    10 mail.example.com.
example.com.       3600  IN  TXT   "v=spf1 mx -all"

The IP address above is documentation-only. Do not skip the mail records, especially MX, SPF, DKIM, and DMARC. The website can remain online while incoming or outgoing mail quietly breaks.

Step-by-Step Domain Transfer

1. Choose the New Registrar

Do not choose a registrar based only on its first-year price. Renewal fees, supported extensions, EPP code access, transfer-lock controls, DNS services, and support response times all matter later.

If you run a VPS, you do not have to use the registrar’s DNS service. You can keep DNS with a separate provider such as Cloudflare or with your own authoritative DNS infrastructure. Decide where DNS belongs before placing the order.

If you are moving the domain together with a server, also follow the DNS and service checks in Launch a Secure VPS in 30 Minutes | Pro Admin Guide. A domain transfer is not a server migration.

2. Start the Transfer Order

Enter the domain in the new registrar’s panel and select the transfer option. The price depends on the extension. For many generic extensions, the fee includes adding one year to the registration period, but exceptions exist.

Enter the exact extension. example.com and example.com.tr do not follow the same transfer procedure. The new registrar may request additional documents or local eligibility information for your extension.

Read the final order screen carefully. A cheap transfer that renews at a very different price is not much of a bargain.

3. Enter the EPP Code

Enter the code from the current registrar into the transfer form. If it is rejected, do not keep submitting the same value. Generate a fresh code in the old panel and copy it carefully. Some registrars invalidate the previous code whenever a new one is generated.

Check the spelling of the domain too. An order started for the wrong domain will not correct itself because you meant another one. Autocomplete is not a reliable assistant here.

4. Watch for Approval Emails

The transfer request may send an approval message to the registrant or administrative email address. Following its link can speed things up, although approval is not always mandatory. Without approval, the transfer may wait for several days depending on the registrar and extension rules.

Check spam folders as well. With a company mailbox, a filter may block the registrar’s sending domain. If you open a support ticket, include the domain and transfer order number, but never put the EPP code in the ticket.

5. Monitor the Transfer Status

The panel may show Pending Transfer, Pending Approval, Completed, or a similar status. A status that does not change immediately is not necessarily an error. Timing depends on the extension, approval method, and response from the current registrar.

Do not wait if the domain will expire during the transfer. Some extensions allow an expired domain to be transferred, while others require renewal or another procedure. The safer approach is to start well before the final days.

6. Verify Everything After Completion

When the transfer completes, check the registrant details, expiration date, nameservers, auto-renewal setting, and transfer lock in the new panel. Some registrars automatically enable or disable the lock after a transfer. Never assume the default is the setting you want.

Check DNS resolution and the web response:

dig +short NS example.com
dig +short A example.com
dig +short MX example.com
curl -I https://example.com

curl -I requests only the HTTP headers. You should see 200, 301, or another response code that you expect. Opening the site in a browser is not enough; your local DNS cache may still show an old result.

For a more useful comparison, run the DNS checks from a second network as well. My home connection and the office resolver do not always refresh at the same moment.

DNS and Email Details That Matter

When email breaks after a domain transfer, the transfer itself is often not the cause. More commonly, a DNS record was missed or copied incorrectly. Checking only the website’s A record and forgetting MX is easy.

If you use Microsoft 365, Google Workspace, or an external mail server, preserve the verification TXT records along with the MX records. DKIM values are often long TXT strings, and one mistyped character can break verification. If the DMARC record is missing, your mail delivery policy may behave differently than expected.

Lowering DNS TTL before a registrar transfer is usually unnecessary. If the nameservers stay the same, cached records do not change. If you are also changing nameservers or IP addresses, lowering the TTL beforehand can make sense as part of that separate migration plan.

A domain transfer by itself normally does not change your SEO rankings. If the nameservers, URL structure, redirects, and content stay the same, changing registrars does not automatically push the site down. For the distinction between domain history and technical accessibility, see Boost Domain Authority: Practical SEO Power Tactics.

Why a Transfer Gets Rejected or Stuck

When a transfer is rejected, read the error code instead of submitting the same request repeatedly. Registrars sometimes show only a short explanation. Ask support whether the rejection is caused by an extension rule, a lock, or a contact-information change.

Do not restart the VPS just because the website disappeared after a registrar change. I have watched people lose ten minutes to that reflex; the resolver was still returning the wrong nameserver. Query first.

Keep the Transfer Secure

An EPP code may not look like a password, but it is still secret authorization data. Do not share it unnecessarily through email, support tickets, or chat. After the transfer, review API keys, access tokens, and delegated users in the old registrar account.

Enable two-factor authentication at the new registrar. Someone with access to the domain account can change redirects, mail records, and certificate-validation records. The account-security practices in 10 Essential Steps to Secure and Harden Your Linux Server apply here too: hardening the server while leaving the registrar account behind one shared password is an incomplete defense.

For company domains, use an address that remains under organizational control instead of a personal mailbox. When an employee leaves, the approval needed for a domain transfer should not remain in that person’s inbox.

Country-Code Extensions May Follow Different Rules

The flow described above is common for .com, .net, and similar generic extensions. Country-code extensions such as .tr, .de, and .uk may require different documents, authorization methods, or registrar procedures.

Do not check only whether an EPP code exists. Read the transfer requirements for the specific extension at the new registrar. A mismatch in the registrant name, company details, or local contact requirements can stop the transfer even after payment.

For .tr domains, check the current registrar’s process rather than assuming the generic .com workflow applies. Country-code rules are not decoration.

When to Postpone the Transfer

If you cannot access the domain owner’s email address, fix the contact details before starting. Wait as well if you have no DNS backup or only limited access to the current provider. To handle a problem during the transfer, you need access to both the old and new panels.

If the domain supports a brand, campaign, or critical email infrastructure, choose a quiet maintenance window. A registrar-only transfer should not cause downtime, but do not close the old account or delete the DNS service until the transfer has completed.

My usual plan keeps the old registrar account open for at least a few days after completion. I check the new panel, DNS records, and auto-renewal first, then confirm that the registration really moved before closing anything. Even for a small domain, that extra check reduces the chance of paying twice by mistake.

Frequently Asked Questions

How long does a domain transfer take?

Timing depends on the extension and approval process. Some transfers finish quickly when you approve the email immediately; without approval, the request may wait for several days.

Will my website go down during the transfer?

It normally will not if the nameservers and DNS records remain the same. Compare the NS, A, and MX records before and after the transfer so you can spot an unexpected change early.

Can I transfer a domain without an EPP code?

Most generic extensions require an EPP or Auth Code. Some country-code extensions use a different verification method, so confirm the exact requirement with your current registrar.

Should I start before the domain expires?

Yes. Leaving the transfer until the expiration date is riskier. An expired domain may trigger renewal, pending, or transfer restrictions and make the process take longer.

I do not consider a domain transfer finished just because the panel says Completed. I verify the nameservers, web response, mail records, and auto-renewal together. For your next transfer, open the terminal first; the panel can wait.