A practical domain transfer checklist.

Confirm what kind of handover you need

A domain acquisition changes who controls a registration. That may involve a change of registrant and, depending on the plan, moving the domain to a different registrar. Some registrars offer account-to-account changes within their own service; the process and requirements are provider-specific.

A hosting migration is a separate operation. Changing the registrar does not necessarily change the website host, and moving the website does not necessarily require a registrar transfer. Write down which changes are intended so the seller, buyer, and providers agree on the scope.

Check registrar status and possible transfer locks

Confirm the current registrar, expiration status, and registrant control. ICANN’s lookup can help identify registration and registrar details, but redacted public records may not identify the owner. Agree on an appropriate verification process before payment.

ICANN describes circumstances that can prevent an inter-registrar transfer, including locks after registration, a prior transfer, or a change of registrant. A 60-day restriction can apply in certain situations. Some change-of-registrant lock options are at the registrar’s discretion. Check the policy and exact domain status with both registrars rather than assuming an exception is available.

• Ask whether the domain is currently transfer-locked and why.
• Check recent registration, transfer, or registrant changes.
• Clarify whether a same-registrar account change is possible and appropriate.
• Confirm what happens if a transfer is delayed or denied.
• Do not promise a fixed completion date until the registrar confirms eligibility.

Document the transaction terms

Record the exact domain name, price, included assets, fees, payment process, transfer method, and completion conditions. Specify who handles registrar charges and any agreed escrow costs. The domain’s acquisition price is separate from future renewal fees, which should be confirmed directly with the receiving registrar.

If escrow is used, confirm the provider independently, read its identity-verification requirements, and understand when funds are released. Never assume an email link or last-minute payment instruction is legitimate. Do not send account passwords, authorization codes, or identity documents through an unverified channel.

AppVault does not collect payments on this website or operate an escrow service. Any acquisition arrangement must be explicitly agreed. Read the AppVault transfer policy and buying guide before proceeding.

Follow the registrar’s authorization process

An inter-registrar transfer typically involves an authorization code, also called an Auth-Code, AuthInfo, or EPP code, and the relevant registrar’s confirmation process. ICANN explains that this code helps identify the registrant and prevent unauthorized transfers. Follow the providers’ current instructions rather than treating a generic checklist as a substitute.

For a same-registrar change, follow that registrar’s account and registrant update workflow. Keep transaction records and confirm that you are gaining the intended control. A screenshot of an account is not the same as completed control in the buyer’s own registrar account.

Protect website and email continuity

Inventory nameservers and essential DNS records before making changes. Plan for website hosting, email delivery, subdomains, and any verification records used by third-party services. Preserve working settings until the replacement services are ready, unless the written agreement specifies otherwise.

For a .app website, coordinate TLS certificate provisioning before the public launch or hosting change. Browsers require HTTPS for the extension, so a new HTTP-only destination can break access. Our .app HTTPS guide covers the practical requirements and security limits.

If you are also replacing an older domain, map existing pages to relevant new URLs, implement permanent redirects where appropriate, and update important internal and external links. A registrar transfer alone does not carry out that website migration.

Confirm completion and ongoing responsibility

Verify the domain in the buyer’s intended registrar account, check the registrant information, and confirm the expiry and renewal settings. Test website and email functionality after any DNS changes. Keep proof of the agreement, registrar confirmations, and payment completion.

Use strong account security and make sure renewal notices reach someone responsible for the domain. Confirm the regular renewal fee and budget for it. Then document who controls registrar access, DNS, hosting, and certificate maintenance.

Each transaction is different. For an AppVault listing, ask for current availability, registrar information, and proposed handover terms before agreeing to a purchase.