Understand which move you are making

A registrar transfer moves the registration between providers. A registrant change changes the registered holder’s details. A hosting move changes where the website runs. These are separate operations, even when a provider offers to coordinate them.

Write down the intended outcome before changing settings. If the goal is a new web host, you may only need a DNS change. If the goal is a new registrar, the website files may remain exactly where they are. A sale can involve several separate handover tasks.

What happens to the creation date?

A normal registrar transfer usually preserves the creation date because the registration continues. The registrar name, updated date, expiration date, or other fields may change. Our checker still calculates age from the registration event it receives.

Save a record before the move and compare it with a fresh result afterward. A newer updated date is not a new birthday. If the creation date changes unexpectedly, ask the registrar to explain rather than assuming that every transfer resets age. Deletion followed by a new registration is a different event; see the expiration guide.

Check restrictions before you begin

For domains covered by ICANN’s transfer rules, recent registration, previous transfers, or some changes to registrant details can introduce transfer restrictions, including 60-day locks in applicable cases. Check the current ICANN transfer FAQ and both registrars’ instructions for your situation.

Do not assume all country-code extensions use the same process. Ask the receiving provider to confirm eligibility, required approvals, and any extension-specific steps before you schedule the move.

Prepare a handover checklist

  1. Confirm access to the current registrar account and relevant approval email addresses.
  2. Record the current nameservers and where DNS records are managed.
  3. Check renewal timing and any transfer restrictions in the account.
  4. Obtain any required authorization code through the registrar’s approved process.
  5. Initiate and approve the move using the receiving provider’s instructions.
  6. Confirm completion in the receiving account and review renewal settings.

Treat authorization codes as credentials. They are not needed for a public domain-age lookup and should not be pasted into a checker, research spreadsheet, or public message.

Verify the services afterward

Check that the domain appears in the correct account and that contact and renewal settings are correct. Test the website and email separately. If DNS hosting was bundled with the old provider, confirm whether it remains available or needs to be migrated.

Finally, run a new lookup and save it alongside your earlier record. Public data may not reflect every change immediately, so use the registrar’s completion notice and account state to resolve operational questions. A successful age lookup alone cannot prove that a website migration, mailbox move, or asset handover is complete.

Free domain age checkerBulk domain age checker