Moving a domain to another registrar does not have to interrupt your website or email. This reusable checklist explains how to prepare, preserve DNS records, verify ownership, complete the transfer safely, and troubleshoot problems before they become outages.
Overview
A domain transfer changes the company that manages your domain registration. It does not automatically move your website files, hosting account, mailbox contents, or DNS hosting. Those services may remain with different providers, so the safest approach is to map the whole setup before you unlock the domain.
For example, your domain may be registered at Registrar A, use DNS at a managed DNS provider, point to a website hosted elsewhere, and send email through a separate business mail platform. A successful transfer should preserve the domain's nameservers and records, but you should not rely on that without checking them before and after the move.
Before starting, record the domain name, current registrar, renewal date, nameservers, DNS records, website host, email provider, and the account owners who can approve changes. Keep access to the current registrar until the transfer is complete and tested. Do not close the old account or cancel related services simply because the transfer has been initiated.
If your DNS setup includes SPF, DKIM, DMARC, DNSSEC, or WHOIS privacy, document those settings as well. The DNS security guide for website owners provides a useful companion checklist.
Checklist by scenario
Before any domain transfer
- Confirm the exact domain. Check spelling, extensions, and whether related domains also need to move.
- Verify account access. Sign in directly through a saved or manually entered registrar address rather than following an unexpected transfer email link.
- Check the registrant contact. Make sure the account email is current and accessible. Transfer approvals and security notices may depend on account or registrant contacts.
- Review eligibility. Look for an active registrar lock, recent registration or transfer, pending ownership change, expired status, dispute, or other restriction. Rules differ by domain extension and registrar, so confirm the current requirements in the relevant account.
- Export or copy DNS records. Save A, AAAA, CNAME, MX, TXT, SRV, CAA, and any verification records. Include TTL values if your DNS provider displays them.
- Record nameservers. Write down the nameserver hostnames exactly. Nameservers determine where DNS is managed; they are separate from the registrar.
- Check renewal timing. Note the expiration date and any transfer-related renewal or registration terms shown by the current and receiving registrars.
- Secure the accounts. Use unique passwords and multi-factor authentication where available. Review recovery email addresses, delegated users, API keys, and recent sign-in activity.
When you are transferring the domain but keeping the same DNS provider
This is usually the least disruptive scenario because the nameservers and DNS records should remain at the existing DNS provider. Before unlocking the domain, capture a screenshot or export of the nameserver configuration. At the new registrar, enter the domain and authorization code, then check that the proposed nameservers match the existing ones. If the new registrar offers to replace them with default nameservers, do not accept that change unless you have deliberately prepared equivalent records there.
When you are transferring the domain and changing DNS providers
Prepare the destination DNS zone before changing nameservers. Recreate every required record, including email authentication and third-party verification records. Compare the old and new zones line by line. Pay special attention to MX records, because a missing or incorrect MX record can interrupt email delivery even when the website still loads.
If possible, lower DNS TTL values in advance according to your provider's guidance, make the planned change during a monitored period, and keep the old DNS service active until the new configuration is working. Propagation is not a single universal countdown; resolvers and cached records can update at different times.
When you need to transfer email without losing service
A domain transfer does not copy mailboxes or messages. If your email provider is staying the same, preserve the existing MX, SPF, DKIM, and DMARC records. If the email provider is changing too, plan mailbox migration separately and confirm that users can sign in, send, and receive mail before changing DNS.
Test addresses at the domain, including shared inboxes, aliases, forwarding rules, contact forms, transactional mail, and password-reset messages. Keep a temporary alternate contact method for important accounts in case mail delivery is delayed.
Transfer comparison checklist
| Item | What to check | Why it matters |
|---|---|---|
| Registrar lock | Whether the domain is locked and how to disable or re-enable the lock | An active lock can block a transfer; leaving it off longer than necessary increases risk |
| Authorization code | Request it through the authenticated registrar account and keep it private | The receiving registrar uses it to verify transfer authorization |
| DNS hosting | Identify where nameservers and records are managed | DNS may stay put, move separately, or be replaced by defaults |
| Privacy settings | Compare contact privacy, public registration display, and verification requirements | Privacy features and required contact details can vary by registrar or extension |
| Renewal date | Record expiration and any pending renewal | A transfer can take time, and an expired domain may follow different recovery rules |
| Transfer timing | Check approval steps, review periods, and any current restrictions | Planning around a launch or renewal deadline leaves less room for troubleshooting |
What to double-check
Lock status and authorization
Unlock the domain only when you are ready to begin. Request the authorization code from the current registrar through its normal dashboard. Treat the code like a password: do not post it in a ticket, chat, screenshot, or public document. After the transfer is accepted or completed, confirm that the domain is locked again if your registrar supports that control.
Do not trust urgent messages claiming that a transfer is pending unless you verify the status by signing in directly. A convincing transfer request can be an account-takeover attempt. For related warning signs, see how to check if a website is safe before you sign in.
DNS and website records
Check the live website from more than one network or device, and verify both the preferred hostname and the alternate form, such as the root domain and www. Test redirects, HTTPS, forms, analytics, content delivery, APIs, and services that depend on subdomains. A site can appear healthy while a less frequently used subdomain or verification record is broken.
Do not assume that copying only the main A record is enough. Modern websites commonly use CNAME records, TXT records for verification and email security, and additional records for applications or regional services.
Ownership and recovery controls
After the move, review the new registrar's account users, recovery methods, notification addresses, and two-factor authentication. Confirm that the domain is listed under the correct legal or business owner and that billing contacts are not the only people receiving security alerts. Keep an offline record of renewal dates and the person responsible for future reviews.
Common mistakes
- Changing nameservers accidentally. Accepting a registrar's default DNS settings can take the domain away from the DNS provider that currently serves your website and email.
- Transferring without a DNS inventory. Without a record of the old zone, it is harder to restore missing mail, verification, or subdomain records.
- Waiting until expiration. A transfer near renewal leaves little time for approval, payment questions, or eligibility restrictions. Start while the domain is active and stable.
- Closing the old registrar account too early. Keep it available for transfer status, authorization, invoices, support, and rollback decisions.
- Assuming email is included. Domain registration and mailbox hosting are separate services. A transfer does not migrate mailboxes or preserve a separate provider's configuration automatically.
- Sharing an authorization code insecurely. Use the receiving registrar's authenticated transfer form and avoid sending the code to an unverified person who contacts you unexpectedly.
- Testing only the homepage. Check email sending and receiving, forms, subdomains, redirects, APIs, and third-party integrations as well.
If you discover that credentials were entered into a suspicious transfer page, treat it as a possible account compromise: change the affected password from the genuine registrar site, revoke unfamiliar sessions or API keys, enable multi-factor authentication, and review domain and DNS changes. The recovery steps in how to recover after phishing can help structure that response.
When to revisit
Use this checklist before every domain transfer, registrar renewal review, rebrand, acquisition, hosting migration, or DNS provider change. Revisit it before a major launch or seasonal sales period, when an employee or contractor with account access leaves, and whenever a registrar changes its dashboard, approval process, privacy controls, or transfer requirements.
Make a short annual domain safety review part of website maintenance. Confirm the registered owner, renewal date, nameservers, DNS host, email provider, account recovery methods, multi-factor authentication, and billing contacts. Remove former users and rotate credentials that may have been shared during a prior project.
Final pre-transfer action: save the DNS zone, confirm account access, verify the domain is eligible, note the renewal date, prepare the authorization code, and decide whether DNS will stay or move. After completion, test the website and every email path, confirm ownership and privacy settings, re-enable the registrar lock, and keep the old setup available until the results are stable.