How to Transfer a Domain Safely: Auth Codes, DNS, Email, and Downtime Checklist
domain transferdomain authorization codeDNS managementbusiness emailregistrarsdomain security

How to Transfer a Domain Safely: Auth Codes, DNS, Email, and Downtime Checklist

TTopDomains Editorial Team
2026-11-20
7 min read

Transfer your domain without avoidable downtime using a practical checklist for auth codes, DNS, email, security, testing, and troubleshooting.

Transferring a domain does not have to interrupt your website or business email. This practical checklist explains how to prepare the domain, preserve DNS and mail settings, obtain the authorization code, complete the move, and test every important service afterward.

Overview

A domain transfer moves the registration record from one registrar to another. It is separate from moving website files, changing web hosting, or switching email providers. In many cases, your website and email can continue working during the transfer because the existing nameservers and DNS records remain in place. The main risk comes from changing several services at once without recording how they are connected.

Before you begin, identify the difference between your registrar and your hosting provider. The registrar manages the domain registration, renewal, transfer controls, and authorization code. The hosting provider runs your website or application. A separate email provider may manage mailboxes and mail delivery. Keeping these roles clear helps you transfer the domain without accidentally changing the services that depend on it.

Use this guide when moving to a new registrar, consolidating a domain portfolio, completing a business ownership handoff, or reviewing a domain after an acquisition. For ownership changes involving several people or organizations, also use the domain ownership handoff checklist.

Pre-transfer inventory

  • Domain name and extension, including any related country-code or secondary domains.
  • Current registrar, account owner, billing contact, and renewal date.
  • Nameservers and the DNS provider currently serving the domain.
  • Website hosting account, CDN, SSL configuration, redirects, and verification records.
  • Email provider, mailboxes, forwarding rules, and SPF, DKIM, and DMARC records.
  • People who can access the registrar, DNS provider, hosting account, and business email.
  • Current DNS records, exported or copied into a change log before making changes.

If you need to document the records themselves, refer to DNS Records Explained and the SPF, DKIM, and DMARC setup guide.

Checklist by scenario

Scenario 1: Transfer the registration while keeping your website and email unchanged

  1. Check eligibility. Sign in to the current registrar and review the domain status, renewal date, and transfer restrictions. Some domains may be subject to registrar, registry, or recent-change restrictions. If the account shows a lock, hold, verification request, or pending update, resolve it before starting.
  2. Confirm the registrant contact. Make sure the ownership and administrative details are accurate and that the responsible person can access the associated email address. Keep a record of the current details before editing anything.
  3. Export or record DNS. Capture nameservers and all important records, including A, AAAA, CNAME, MX, TXT, and any records used for verification. Do not assume the new registrar will automatically recreate DNS records.
  4. Check the domain lock. Turn off the registrar transfer lock only through the authenticated registrar account. Do not follow an unlock request from an unsolicited message.
  5. Request the authorization code. The code may be called an auth code, EPP code, transfer key, or transfer password. Obtain it through the registrar’s secure account or its documented support process. Treat it like a password.
  6. Start the transfer at the new registrar. Enter the exact domain name and authorization code. Review the price, included renewal period if stated, privacy options, account security, and renewal settings before submitting.
  7. Approve confirmation messages carefully. Watch the registrant and account email addresses for transfer notices. Confirm only requests that match the transfer you initiated. If a message is unexpected, verify its status from the registrar dashboard instead of using its link.
  8. Monitor the transfer status. Keep the current registrar account active until the transfer is complete. Do not cancel hosting, DNS, or email services based only on a transfer submission notice.
  9. Test after completion. Confirm the domain appears in the new account, the nameservers are correct, the domain lock is enabled again, renewal is configured, and all website and email services work.

Scenario 2: Transfer the domain and move DNS at the same time

This is a higher-risk change because the registration move and DNS migration can fail independently. First, recreate the existing DNS zone at the new DNS provider and verify it. Lowering DNS TTL in advance may help some resolvers notice planned changes sooner, but it does not guarantee instant propagation. Keep the old DNS service available until the new records have been tested and the change is stable.

Make a separate change plan for nameservers. The domain transfer should not be treated as proof that nameservers have changed. After updating them, use multiple networks or a DNS propagation checker to inspect authoritative nameservers, website resolution, mail exchange records, and important TXT records.

Scenario 3: Transfer during a website or email migration

Separate the work into stages whenever possible. Complete the website or email migration first, test it while the domain remains at the current registrar, then transfer the registration. If timing requires a combined move, establish a rollback plan, preserve the old DNS zone, and define who can make emergency changes. For mail-specific checks, use the business email DNS checklist.

What to double-check

AreaWhat to verify
OwnershipThe registrant name, organization, contact email, and account owner are intentional and current.
AuthorizationThe auth code was obtained securely, entered accurately, and has not been shared in an unsecured channel.
DNSNameservers and records match the intended website, email, verification, redirect, and security configuration.
WebsiteHTTP and HTTPS versions load, redirects work, forms submit, and the SSL certificate remains valid.
EmailInbound and outbound mail work, MX records are correct, and SPF, DKIM, and DMARC remain aligned.
SecurityTwo-factor authentication is enabled where available, the transfer lock is restored, and unused users or API keys are removed.
BillingAuto-renewal, payment details, privacy settings, and renewal dates are correct at the new registrar.

Keep screenshots or exported records of the completed transfer. They provide a useful audit trail if ownership, billing, or DNS responsibilities later change. Review the registrar versus hosting provider decision matrix if you are also deciding which services should remain together.

Common mistakes

  • Transferring a domain that is already locked. A domain lock is a security control, but it must be disabled temporarily for an authorized transfer. Re-enable it after completion.
  • Changing nameservers without copying DNS records. This can make a website disappear or interrupt mail even when the registration transfer itself succeeds.
  • Using an outdated contact email. Transfer notices and verification requests may go to an address nobody can access.
  • Assuming a transfer includes hosting. Registration, DNS, website files, databases, SSL, and email are separate services unless a provider explicitly combines them.
  • Deleting the old account too soon. Keep access until you have confirmed the domain, DNS, website, email, billing, and security settings at the new registrar.
  • Ignoring renewal settings. Check whether the transfer changed the renewal date, auto-renewal preference, privacy setting, or payment method.
  • Approving an unfamiliar email. Confirm the transfer from a trusted dashboard if a message looks suspicious or does not match your change record.

Transfer troubleshooting

ProblemPractical next step
Transfer rejectedCheck the domain lock, authorization code, contact email, and any registrar or registry eligibility notice. Correct one issue at a time.
Authorization code failsRequest a new code, copy it without extra spaces, and confirm that the code belongs to the exact domain being transferred.
Transfer is delayedReview both registrar dashboards and email inboxes for a pending approval, verification request, or required action.
Website stops loadingCompare nameservers and A, AAAA, or CNAME records with the pre-transfer inventory. Do not change several DNS records at once.
Email stops arrivingCheck MX and email authentication records, then verify that the active DNS provider is the one you intended.

When to revisit

Revisit this checklist before every domain transfer, especially before a busy sales period, product launch, seasonal campaign, or planned maintenance window. It is also useful when a business changes ownership, a team member leaves, a registrar changes its workflow, or a website and email provider are replaced.

After the transfer, schedule a short follow-up audit. Confirm the domain is registered to the intended owner, the renewal date is recorded, the transfer lock and account security controls are active, and the website and email still pass their normal tests. Repeat the review when registrar interfaces, verification procedures, or registry rules change; those details vary by provider and domain extension.

Action plan: create a dated folder containing the DNS inventory, transfer status, authorization-code request, registrar receipts, and post-transfer test results. Assign one person to own renewal and access reviews. If the move is part of a wider site change, pair this checklist with the domain redirect mapping guide, the website backup and restore testing guide, and the domain renewal and expiration guide.

Related Topics

#domain transfer#domain authorization code#DNS management#business email#registrars#domain security
T

TopDomains Editorial Team

Editorial Team

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.