Move a business domain only after the company can prove who controls the registrar account, the registrant contact email and the active DNS zone. The transfer itself is usually straightforward; the costly mistakes happen when a confirmation email goes to a departed employee, a nameserver is changed unnecessarily, or nobody knows which vendor sends mail from the domain.
This is an operational guide, not a claim that every extension or registrar has identical rules. Confirm the current rules for the specific top-level domain with the gaining registrar before setting a date.
Separate the three systems before touching the transfer button
A registrar holds the domain registration. A DNS provider publishes the records that point the domain to web, mail and other services. A web host serves the site. They may be one vendor, but they do not have to be. Write down the current provider and account owner for each one.
| System | What to capture | Why it matters |
|---|---|---|
| Registrar | Account owner, recovery email, renewal date, transfer lock status | The transfer approval and authorization code originate here. |
| DNS | Nameservers and exported record list | Mail and web can fail if an active zone is replaced without comparison. |
| Hosting and mail | Which records each service requires | You need a way to test the public site and mail after the move. |
Do not treat a screenshot as the only record. Capture the account owner, recovery path, and a current record inventory in the company’s controlled documentation. Never paste a transfer authorization code into a broadly shared ticket; it is a transfer credential.
Check eligibility before you change registrant details
For many generic top-level domains, an authorization code is required for an inter-registrar transfer. ICANN explains that a registrar must either let the registered name holder generate the code through its control panel or provide it within five calendar days of a request. ICANN’s transfer policy also describes a possible 60-day transfer lock after a Change of Registrant, unless the registrar offered and the registrant used an opt-out where applicable.
That creates a practical sequencing rule: if the business needs to move to another registrar soon, ask the gaining registrar about transfer eligibility before changing registrant name or email. Do not assume a renewal, a new registration, a country-code domain, or a recent contact change follows the same timetable. Ask the registrar to identify the actual restriction on this domain.
Use a short transfer worksheet
- Confirm the legal business owner and two authorized administrators in the current registrar account.
- Verify that the registrant contact email is accessible now and is monitored during the move.
- Record the expiration date, auto-renew setting, current nameservers and every active DNS record type.
- Identify mail senders, website host, payment or booking providers and verification services that depend on DNS.
- Ask the gaining registrar to confirm eligibility and its required approval steps.
- Unlock the domain only when the transfer is ready to begin; request the authorization code through the controlled account.
- Start the transfer at the gaining registrar and have an authorized person monitor both registrars’ notices.
Preserve DNS deliberately
Changing registrars does not inherently require changing DNS provider. If the existing nameservers remain in place, the public DNS answers should continue to come from the same zone. That is often the lowest-change option. If the plan also changes DNS providers, treat that as a separate change with a record-by-record comparison and a scheduled validation window.
At minimum, compare A/AAAA, CNAME, MX, TXT, and any service-verification records. A common failure is preserving the website record while omitting an email authentication TXT record or a booking-provider CNAME. The site can look fine while inquiry confirmations silently fail.
Run transfer-day and post-transfer checks
Keep the old and new registrar confirmation emails with the change record. Once the gaining registrar shows the domain as active, verify the organization can sign in, renew, lock the domain and update contacts. Then test the public website on the canonical address, one representative inquiry form, and one normal inbound/outbound mail path if the domain is used for mail.
Illustrative example: a landscaping firm leaves its nameservers unchanged during a registrar transfer. Its owner checks the site, sends one contact-form test to a monitored inbox, and asks its mail administrator to confirm that the domain’s authentication records are still present. That does not prove deliverability to every recipient, but it catches a changed zone or missing record early.
What belongs in the final ownership record
- Registrar name, account owner and two recovery contacts.
- Renewal date and whether auto-renew is enabled.
- Nameservers, DNS provider and where the current record inventory lives.
- Who may request a transfer or change registrant information.
- Date, approver and result of the move.
A domain move is complete when the business—not a former vendor or individual—can administer renewal, recovery and future transfers, and when the connected website and communications services have been checked.
