A domain transfer checklist should protect more than the transfer request itself. Your website and email depend on services that may sit outside your registrar account. Moving registration usually does not require moving those services. However, bundled DNS, unexpected nameserver changes, or missing renewal settings can turn an administrative task into an outage.
This guide focuses on moving between registrars while keeping your existing website, email, and DNS services intact. Use it to define the work, assign responsibility, and confirm continuity before closing the old account.
Separate Registration From DNS and Hosting
A registrar manages your domain registration. The registry maintains the top-level domain, such as the extension after your business name. DNS, the Domain Name System, directs requests toward your website, mail servers, and other services.
Authoritative nameservers publish your domain’s DNS records. A different company may provide those servers, even when your registrar displays DNS settings.
- Registrar transfer: Changes the company managing the registration.
- DNS provider migration: Changes where you maintain and publish DNS records.
- Hosting migration: Moves the website, mailboxes, or other applications.
Keep these changes separate whenever practical. ICANN’s overview of domain infrastructure explains the underlying DNS relationships.
Ask both registrars whether the transfer preserves existing nameservers and DNSSEC settings. If you must also move DNS, create a separate DNS provider migration plan rather than adding that change silently.
Build a Domain Transfer Checklist With Clear Ownership
Start with a written inventory. Screenshots help, but an export of the complete DNS zone provides a more useful recovery reference. A zone is the collection of DNS records for your domain.
- Record the current registrar, DNS provider, website host, and email provider.
- Identify the business owner who can approve the transfer.
- Save the current nameserver list and domain expiration date.
- Export DNS records, including mail, verification, and certificate-related entries.
- Record DNSSEC status and any parent DS records.
- Confirm access to both registrar accounts and recovery methods.
- Assign one person to approve changes and another to verify results.
A DS record connects a signed DNS zone to its parent’s chain of trust. Keep its exact values, not just a note that DNSSEC is enabled.
Store this evidence securely. Do not include passwords or transfer authorization codes in shared project notes.
Verify Contacts, Eligibility, Locks, and Authorization
Check the registration contact details inside the current registrar account. Public registration data may hide those details, so public lookup results do not prove they are correct.
Confirm that the responsible person can receive approval messages. Maintain a recovery address outside the transferring domain where the provider permits it. This reduces dependence on the very email service you are protecting.
Review transfer eligibility before changing contact information. Recent registration, a previous transfer, or certain contact changes can trigger restrictions. Rules vary by domain extension and registrar.
- Check for ordinary transfer locks and any separate registry lock service.
- Resolve disputes, holds, or other restrictions with the current provider.
- Unlock the domain only when you are ready to submit the transfer.
- Request the authorization code, sometimes called an auth or EPP code.
- Share that code only through the receiving registrar’s trusted process.
Treat the authorization code as a secret. Avoid posting it in support tickets with broad access.
Confirm Nameservers and DNS Service Will Remain Active
The main continuity question is not simply whether the nameservers stay unchanged. You also need assurance that the company operating them will continue serving your domain after the transfer.
Some providers bundle DNS with registration. Transferring away may affect that service or its billing. Obtain written confirmation about retention, charges, and cancellation behavior.
- Compare the current delegated nameservers with your saved baseline.
- Check whether the receiving registrar requires its own nameservers.
- Reject optional parking, forwarding, or default DNS changes you do not need.
- Keep existing DNS and hosting subscriptions active.
- Confirm continued access to DNS editing and any automation credentials.
If you use nameservers under your own domain, check their registered host objects and glue records. Glue supplies addresses that resolvers need for certain nameserver lookups. Ask the receiving registrar how it handles those objects.
Do not lower DNS cache lifetimes automatically. A registration-only transfer should not need record changes or a DNS cache countdown.
Check DNSSEC Before Approving the Transfer
DNSSEC adds digital signatures that help resolvers verify DNS answers. A registrar transfer should preserve the existing trust relationship when your DNS provider and signing keys remain unchanged.
However, registrar interfaces and supported workflows differ. Confirm that the receiving registrar supports your domain extension and existing DNSSEC configuration before submitting the request.
- Save the current DS record values from the parent zone.
- Confirm who manages the signing keys at the DNS provider.
- Ask how the destination handles existing DS records during transfer.
- Verify that its account tools support future DS updates.
- Check DNSSEC validation before and after completion.
Do not disable DNSSEC merely because you are changing registrars. Likewise, do not publish a new DS record unless it matches the active signing setup.
If validation fails after an unexpected delegation change, use a focused DNSSEC failure investigation. Repeatedly changing nameservers and DS values can make recovery harder.
Review Renewals, Billing, and Transfer Timing
Schedule the transfer well before expiration. Avoid combining it with a website launch, email migration, or staff departure. Leave time to resolve approval or account-access problems.
Do not assume every transfer adds the same registration period. Extension rules and recent renewal activity can affect the result. Ask the receiving registrar to confirm the expected expiration date and charges.
Your domain transfer checklist should also cover services billed separately:
- Domain renewal and auto-renew settings at the destination.
- Valid payment details and billing contacts.
- DNS hosting, email, website hosting, and forwarding subscriptions.
- Privacy services and any provider-specific security controls.
- Certificate renewal automation that uses the old registrar’s DNS API.
An API lets software manage services automatically. A certificate renewal may fail later if its DNS integration loses access, even when today’s website works.
Keep the old account accessible until you confirm every remaining dependency.
Submit the Transfer Without Adding Unrelated Changes
Review the receiving registrar’s order carefully. Confirm the domain spelling, account owner, selected nameservers, and any optional services. Then submit the authorization code through its official interface.
Watch both accounts and the designated contact mailbox for approval requests. Verify messages through the registrar portal rather than trusting unexpected email links.
Record the submission time, approval time, and support reference numbers. Continue checking website and email availability while the request remains pending.
If a service fails, compare the live delegation with your baseline first. A pending registrar transfer alone does not prove DNS changed. Avoid editing working records just to make the transfer appear to progress.
Also establish an escalation path in advance. The current registrar handles some transfer restrictions; the receiving registrar handles its order and account process. Your DNS provider handles authoritative service failures.
Validate Website, Email, and Registration After Completion
Completion in the registrar portal is only one acceptance check. Compare the final registration and service state with the evidence you collected beforehand.
- Confirm the receiving registrar now manages the domain.
- Verify nameservers, parent DS records, and any required glue records.
- Check DNS answers through multiple independent resolvers.
- Open the main website and important subdomains over HTTPS.
- Test inbound and outbound email with an external mailbox.
- Compare mail routing and email authentication records with the baseline.
- Verify the expiration date, payment method, contacts, and auto-renew settings.
- Re-enable transfer protection and confirm multifactor authentication.
Keep monitoring after completion. A working cached DNS answer does not prove the authoritative path remains healthy. Test certificate automation if it depends on registrar-linked access.
Close the domain transfer checklist only after the owner accepts the results. Cancel old services individually, and only after confirming that nothing still depends on them.
Professional remote assistance can help when account ownership, bundled DNS, DNSSEC, or certificate automation complicates the move. Tech Rescue Ops LLC can help review dependencies and coordinate validation without combining unrelated infrastructure changes.