How to Transfer a Domain Without Downtime

Move a domain registration to another registrar while keeping the website, email and authoritative DNS working.

How to Transfer a Domain Without Downtime

Quick answer

Move the registration independently of DNS and hosting where your providers permit it. Inventory current nameservers and mail records, verify transfer eligibility, then keep the working services online until the gaining registrar confirms completion.

In this guide

Registrar acknowledged the transfer, but delegation changed

Compare the parent-zone NS answers with the nameservers saved before the move. If the new provider took over delegation, verify the new zone has the original MX records and expected web addresses before canceling the old DNS service.

A registrar move in three independent checks

Consider a small studio whose domain is registered with provider A, DNS is hosted at provider B, and email is handled by provider C. The studio wants a different registrar. Its operator saves a current zone export and writes down the nameservers shown in the registry delegation, plus the expiry date, mail provider and working website hostname. Provider B confirms that DNS is an independent paid service. The website stays on the current host. The transfer is therefore a change of account responsibility while website and mail remain on the same working services. The gaining registrar asks for a transfer code. The owner obtains it from provider A, uses the gaining registrar’s official transfer form and checks the transfer status directly.

The useful post-transfer checks have three different owners. The registrar check confirms the transfer completed and renewal is set correctly. The DNS check confirms nameservers and answers still match. The website and mail check demonstrates the site loads under HTTPS on a deep URL and representative mail still arrives. If the old provider supplied free DNS only while it was registrar, replace the zone and validate it before transferring. During a DNSSEC-enabled move, confirm the correct chain and follow both providers’ instructions before changing delegation. A valid old DS record paired with an incompatible destination zone can cause validating resolvers to reject answers. If nobody knows who manages DNSSEC, resolve that responsibility before cutover. Keep the transfer code outside project notes and save a written record of expiry after the move.

Identify who does what

A domain seller, DNS provider and website host may be three different businesses. Find the current registrar, authoritative nameservers, hosting account and email provider. A single dashboard can manage several roles without making them technically interchangeable.

Common problem. A transfer checklist accidentally cancels the only DNS service or mailbox plan. Record which provider answers authoritative questions and check whether that service continues after transfer.

Ask the losing provider about bundled DNS and email before authorizing the transfer.

Check the domain’s transfer status

A transfer button is missing shortly after a purchase or registrant update. Review domain status and the current registrar and registry rules. Rules differ by extension, transfer history and ownership change.

Common problem. An owner changes contact details immediately before a planned transfer and encounters a lock. Check provider guidance on eligibility, expiration and any required waiting period.

If renewal is close, resolve continuity and payment ownership before relying on a timely transfer.

Prepare the authorization

Obtain the authorization code when your extension uses one. Use the losing registrar’s official account workflow and give the code only to the intended gaining registrar. Verify access to the relevant contact inbox.

Common problem. A confirmation arrives in a stale mailbox or a code is pasted into an unrelated support thread. Check the operator’s official dashboard for pending actions and request a fresh code if necessary.

Document who can approve the move without adding credentials to a general project checklist.

Preserve nameservers and records

You want the existing host to keep serving throughout the registrar move. Keep current authoritative nameservers when independent service can continue. Export relevant records and record the domain’s DNSSEC state where applicable.

Common problem. The new account applies default parking nameservers or stops serving an out-of-date zone. Compare the delegation and authoritative web and mail records before and after the move.

If bundled DNS must move, build and verify the replacement zone as a separate step.

Test mail independently

A business uses multiple mail services and a website form. Record MX and sender authentication records. Test inbound and outbound mail with approved accounts and confirm the form’s delivery destination.

Common problem. A healthy homepage masks a broken mailbox route or forgotten DKIM selector. Check a representative mailbox and inspect a delivered test message’s authentication results.

Test external calendar invitations or helpdesk replies when they rely on the same domain.

Verify completion and recovery

The gaining registrar reports a successful transfer. Check domain status, expiry, renewal settings, nameservers and contact details. Reapply the appropriate transfer lock after confirmation.

Common problem. The domain is operational but auto-renew remains disabled in the new account. Confirm a valid payment method and authorized operator in the gaining dashboard.

Link the new account record to a shared renewal calendar and assign a backup contact.

Troubleshoot a disagreement

The old dashboard and public records seem to show different information. Distinguish registrar status from cached DNS. Check the registrar’s confirmation and authoritative delegation independently.

Common problem. Several nameserver changes are made while a transfer is still processing, obscuring what changed. Record timestamps and exact statuses before contacting support from the official portal.

Keep the old service available until web, mail and ownership checks have passed.

Leave an ownership record

A contractor handed over the website after the domain move. Record the official registrar, organization owner, renewal date and authorized support contacts. Store recovery details in approved secure storage.

Common problem. The contractor remains the only person who can receive a renewal warning. Ask a second authorized operator to find the renewal view and identify how to get help.

Review the record after staff or billing changes so ownership stays clear.

Record what will change before approving the transfer

A registrar transfer order should name the domain, gaining registrar, current DNS service, expiry and person who can approve the change. List any provider-controlled mailbox tied to the old account. Check whether DNSSEC, registrant changes or extension-specific limits affect the move. Record the successful baseline for both web and mail. Use the registry and registrar status as evidence of transfer completion, then independently verify a working public HTTPS route. Preserve locked and unlocked states only for the appropriate duration of the workflow. Help with an ineligible transfer should come through the current registrar’s documented account route.

ICANN policy and guidance

DNS Records Explained: A, AAAA, CNAME, MX and TXT