Moving a domain to a different registrar changes the company that manages its registration. It does not move the website, hosting account, email service, or DNS records by itself. This guide covers a holder-authorized transfer between registrars for generic top-level domains (gTLDs) governed by ICANN's Transfer Policy. Country-code domains and some registry or registrar services can have different rules, so check the exact extension's terms before starting.

ICANN's current Transfer Policy was updated on February 21, 2024, with implementation required no later than August 21, 2025. The policy and ICANN's registrant transfer guidance were checked November 3, 2026. A registrar's own control panel may use different labels, but the checks below help identify the required information and common timing restrictions.

Before you start: confirm eligibility and protect the live site

1. Confirm who controls the registration. Check the domain in your current registrar account and confirm that you are the registered name holder or are authorized to act for that holder. Make sure you can access the account and the contact channels used for transfer notices. Do not begin while another party controls the registrar account or registrant approval.
2. Check the domain's status and dates. Record the expiration date and look for a transfer lock, recent registration, recent registrar transfer, or recent change to registrant contact data. Under ICANN's gTLD policy, a transfer may be denied during the first 60 days after initial registration or a prior registrar transfer. A 60-day inter-registrar lock may also follow a change of registrant; the policy allows an opt-out only if the registrar offered it before that change and the holder opted out. Ask the registrar which date and rule applies to your domain.
3. Check for special restrictions. An active dispute or court order can prevent a transfer. Other grounds in the policy include fraud concerns, a reasonable dispute about the holder's identity, certain unpaid registration charges, or the holder's explicit objection. If any apply, resolve the issue with the registrar or obtain specific advice before submitting a request. A domain being expired does not mean every transfer will work; check renewal and recovery status first.
4. Preserve DNS and email settings. Save the current nameservers and DNS records, including A/AAAA, CNAME, MX, TXT, and any DNSSEC/DS settings. Check whether DNS hosting is bundled with the current registrar or provided separately. A registrar transfer alone should not be treated as a website or DNS migration, but verify whether the gaining registrar will keep the existing nameservers or offer a default DNS setup. Keep hosting and mail services active during the move.

Registrar transfer steps

1. Choose the gaining registrar and verify its terms. Check that it supports the exact domain extension, its current transfer price and renewal terms, whether transfer adds registration time, and how it handles DNS and DNSSEC. ICANN's policy requires a one-year extension for a completed holder-authorized gTLD transfer, subject to a maximum total unexpired registration term of ten years; confirm how the registrar and registry apply this to your extension and billing.
2. Unlock the domain if required. In the current registrar account, remove the registrar transfer lock (sometimes labeled domain lock or clientTransferProhibited). ICANN's policy requires the registrar to provide a way to remove that status; if it does not provide a self-service facility, it must remove it within five calendar days of the holder's request. Follow the registrar's own steps and wait for its account status to update.
3. Request the AuthInfo or transfer code. Generate the code in the current registrar account or request it from support. For gTLDs covered by ICANN's policy, where the registrar does not provide a self-service way to generate and manage the code, it must provide the code within five calendar days of the request. Keep the code private and enter it only in the gaining registrar's official transfer flow. ICANN does not create or retrieve these codes for registrants.
4. Submit the transfer with the gaining registrar. Enter the exact domain and the requested authorization code, then follow that registrar's instructions. Read the order summary and confirm the account, renewal, and contact details. A transfer request can require explicit holder authorization; the gaining registrar must receive the required confirmation before it can proceed.
5. Read and respond to transfer messages. Monitor the registered holder's email and registrar account for the gaining registrar's authorization request and notices from the current registrar. Approve only a transfer you initiated. Do not ignore an unexpected notice: contact the current registrar if you did not authorize it. ICANN's current policy requires the registrar of record to notify the holder of a pending transfer, and a transfer request may fail if required confirmation is not completed.
6. Wait for completion and verify account status. The registry process has a five-calendar-day response window for the registrar of record to object after the registry receives a transfer command, but account processing and registrar-specific steps can make the total elapsed time different. Check both registrar accounts and the gaining registrar's confirmation rather than assuming a fixed completion time.
7. Recheck DNS, website, and email. Confirm the domain's nameservers, DNS records, DNSSEC/DS configuration, renewal date, auto-renew setting, and registrant contact details in the gaining account. Visit the site and send/receive a test email if those services use the domain. If you intend to change DNS providers or hosting too, schedule and verify that as a separate migration.

When a transfer can be delayed or denied

For covered gTLDs, ICANN's policy lists specific reasons a registrar may deny a transfer. These include evidence of fraud, a reasonable identity dispute, certain unpaid registration periods, the holder's informed objection, a request within 60 days of initial registration, a request within 60 days after another registrar transfer, and a 60-day lock after a registrant change when the holder did not opt out before the change. A pending UDRP or URS matter, a court order, or a pending transfer dispute can also require denial. The exact policy has additional detail and exceptions; consult the current policy and ask the registrar for the specific reason if a request is denied.

Do not assume every registrar lock is a valid reason to block a transfer indefinitely. The policy says the holder must have a reasonable opportunity to unlock the domain before a transfer request. If a registrar denies the request, ask for the reason and the applicable policy section in writing. ICANN provides a transfer complaint process for suspected policy violations involving covered registrars and domains.

Keep transfer and website migration separate

A registrar transfer changes the registrar of record. It does not automatically copy website files, databases, mailboxes, or DNS zone data. Before changing nameservers or DNS records, compare the current and new DNS configurations and plan the cutover. If you are moving hosting as well, use the hosting move checklist and migration hours estimator. Use the multi-year domain cost calculator to model prices you have verified with each registrar.

Sources checked November 3, 2026

• ICANN Transfer Policy, updated February 21, 2024 — holder authorization, AuthInfo code, registrar lock removal, timing restrictions, denial conditions, and transfer-term extension.
• ICANN inter-registrar transfer information — holder-facing process overview and links to current transfer resources.
• ICANN: About Auth-Codes — what an Auth-Code is, how registrars provide it, and why ICANN cannot create one for a registrant.