A domain transfer readiness review should prove that the business controls the current registrar account, can receive transfer messages, understands any transfer lock, has a current authorization code, and can preserve DNS service throughout the move. Do not start by changing every account detail. First record the existing state, check timing restrictions, and schedule the transfer while the website and email can be monitored.

Identify the registration and its owner

Record the domain, current registrar, renewal date, registration status, nameservers, registrant contact, billing owner, and the internal person accountable for the move. Confirm that the team can sign in using an organization-controlled account and can complete any required multi-factor authentication. If access depends on a former employee, a personal mailbox, or an unknown reseller, recover control before requesting a transfer.

Check that the destination registrar supports the top-level domain and that the person opening the destination account is authorized to accept ownership. Store the approval, transfer date, and support contacts in the change record.

Check locks before changing contact details

ICANN's registrant transfer FAQ lists situations that can prevent a transfer, including the first 60 days after initial registration, the 60 days after a previous transfer, and a Change of Registrant lock. ICANN's Change of Registrant guidance advises a registrant who intends to move registrars to consider transferring before changing registrant information to avoid triggering the applicable lock.

Review the domain status in the registrar panel and note the exact reason for any lock. Do not assume that an ordinary security lock, a recent registration, a previous transfer, and a registrant-change lock are the same condition. Ask the current registrar for the specific removal or waiting process when the panel is unclear.

Obtain and protect the authorization code

ICANN explains in About Auth-Code that an authorization code identifies the holder for a generic top-level domain transfer and is required for the move. The registrar may let the holder create the code in the control panel or must provide it within the documented request period.

Request the code only when the destination account and change window are ready. Treat it as a temporary secret: keep it out of tickets, shared chat rooms, screenshots, and public documents. If the registrar sends it by email, verify the recipient mailbox and delete unnecessary copies after the transfer is complete.

Preserve DNS and dependent services

Export or capture the current DNS records before the move. List the website, mail routing, verification records, subdomains, redirects, and any service that depends on the domain. A registrar transfer and a nameserver change are separate decisions; keeping the existing authoritative nameservers during the registrar move reduces the number of variables being changed at once.

Record the current website and email checks so the team has a baseline. If the destination registrar proposes new nameservers automatically, review that choice rather than accepting it without a matching zone.

Run and verify the transfer

  1. Confirm the domain is eligible and unlocked for the intended transfer.
  2. Confirm the registrant contact and approval mailbox are accessible.
  3. Open the correct destination registrar account and verify its security settings.
  4. Enter the authorization code only in the destination registrar's authenticated transfer flow.
  5. Respond to legitimate confirmation requests after checking the domain and registrar names.
  6. Monitor the website, HTTPS, DNS, and business email during the change window.
  7. Verify the domain appears in the destination account with the intended registrant, renewal setting, and nameservers.

Keep the old registrar account available until the destination shows completed ownership and all dependent services pass their checks. Then revoke obsolete access, remove saved authorization-code copies, update the domain register, and set reminders well before the next renewal. The goal is not merely a completed transfer message; it is continued control of the domain and every service that relies on it.

Sources

  1. About Auth-Code — ICANN
  2. FAQs for Registrants: Transferring Your Domain Name — ICANN
  3. About Change of Registrant — ICANN

Related reading