Moving a domain to a new registrar does not have to interrupt your website or email. This guide provides a reusable domain transfer checklist, explains what to verify before unlocking a domain, and shows how to confirm DNS, email, privacy, redirects, and renewal settings after the transfer is complete.
Overview
A domain transfer changes the company responsible for managing your registration. It does not automatically move your website files, hosting account, mailboxes, databases, or DNS zone. Keeping those services separate is the key to transferring a domain without downtime.
In many cases, the safest approach is to leave the domain’s existing nameservers unchanged during the registrar transfer. The nameservers identify where DNS is hosted, while DNS records direct visitors to your website and route email to your mail provider. If you copy or replace those settings unnecessarily, a transfer that should be administrative can become a website or email migration.
Transfer terminology and eligibility requirements can vary by registrar, registry, and top-level domain. Treat the following as a planning framework, then confirm the exact instructions shown in both registrar accounts before you begin.
| Item | What to confirm | Why it matters |
|---|---|---|
| Domain status | The domain is not subject to a transfer lock or other restriction | A locked or restricted domain may not transfer until the issue is resolved |
| Authorization code | You can obtain the current transfer or authorization code | The receiving registrar may require it to start the transfer |
| Registrant access | You can access the registrant contact and administrative email | Verification messages or transfer notices may be sent there |
| Nameservers | You have recorded the active nameservers and DNS records | This helps preserve website and email routing |
| Expiration date | The transfer will not collide with an urgent renewal deadline | You need time to correct errors or respond to requests |
| Privacy settings | You know whether privacy protection will carry over | Privacy features may be configured separately at the new registrar |
Checklist by scenario
Before any domain transfer
- Confirm that you control the current registrar account and can sign in without relying on an email address hosted on the domain being moved.
- Check the domain’s expiration date, transfer status, and contact details. Correct outdated information before starting, but allow time for any required verification.
- Record the current nameservers. Then export or copy the DNS zone, including A, AAAA, CNAME, MX, TXT, and any provider-specific records. For background, see DNS Records Explained.
- Identify every service that depends on the domain: website hosting, email, transactional mail, analytics, payment tools, identity systems, VPNs, APIs, and domain-based redirects.
- Take a current website and database backup. Store a copy outside the hosting account and confirm that it can be opened or restored. The website backup strategy guide provides a practical approach.
- Check whether the domain has a registrar lock, client transfer prohibition, registry restriction, or pending ownership change. Requirements differ, so use the current registrar’s help documentation as the final reference.
- Request the domain authorization code, sometimes called an EPP, transfer, or auth code. Keep it private and enter it only in the receiving registrar’s verified transfer workflow.
If you are keeping the existing DNS provider
This is often the least disruptive scenario. Start the transfer without changing the nameservers, and verify that the new registrar displays the same nameserver values after completion. Do not assume that transferring registration also transfers the DNS zone. If DNS remains with the current provider, keep that account active until you have confirmed the transfer and all dependent services.
If you are moving DNS as well
Prepare the new DNS zone before changing nameservers. Recreate every required record and pay particular attention to MX records, SPF, DKIM, DMARC, verification TXT records, subdomains, wildcard records, and CNAMEs used by SaaS platforms. Lowering DNS time-to-live values ahead of a planned change may help reduce the time some resolvers retain old answers, but it does not guarantee instant propagation. Use the DNS propagation guide to plan verification.
If email continuity is critical
Do not make the transfer your only email change. Record the complete MX configuration and all authentication records first. Confirm that your mailbox provider is independent of the registrar account, and make sure you can receive administrative notices at an alternative address. After the transfer, send and receive test messages from more than one network or mailbox, then inspect the relevant mail headers if delivery behaves unexpectedly.
If the website is also moving hosts
Separate the registrar transfer from the hosting migration whenever possible. First copy the site, database, certificates, scheduled tasks, environment variables, and redirects to the new host. Test the site using a temporary address or local hosts-file method, then follow a dedicated website migration checklist. Combining both changes makes it harder to identify whether a problem comes from hosting, DNS, or registration.
What to double-check
- Nameservers: Compare the values before and after the transfer. A different nameserver set can point the domain to an empty or incomplete DNS zone.
- DNS records: Confirm the apex domain, www hostname, important subdomains, MX records, and TXT records used for email or service verification. Avoid deleting records simply because their purpose is not immediately obvious.
- SSL certificates: A registrar transfer normally does not issue or renew a certificate. Verify that HTTPS still works for the main domain and important subdomains. If hosting is changing too, confirm certificate provisioning at the new host.
- Redirects: Domain forwarding, URL redirects, and parked-domain settings may belong to the old registrar rather than the DNS provider. Recreate them if required.
- Privacy and contacts: Check whether privacy protection, registrant contact display, notification addresses, and two-factor authentication were carried over or need to be enabled again.
- Renewal settings: Confirm the new expiration date, auto-renewal preference, payment method, and renewal notifications. Do not rely on an assumed renewal date until the new registrar shows it.
- Delegation and DNSSEC: If DNSSEC is enabled, verify that the delegation and signing configuration remain consistent. An incorrect DS record can make a domain appear unreachable even when ordinary DNS records are correct.
Common mistakes
Changing nameservers during the transfer without a plan. This can move visitors and mail to an unconfigured zone. Preserve the existing nameservers unless you are intentionally migrating DNS.
Requesting a code from an unverified channel. Use the current registrar account and protect the authorization code like an account credential. If a message asks you to disclose it outside the transfer process, pause and verify the request.
Starting too close to expiration. A transfer can require user action, correction of contact details, or support intervention. Begin early enough to leave room for troubleshooting and renewal if necessary.
Assuming privacy, forwarding, and renewals are automatic. These are registrar-level settings and may not match between providers. Review them explicitly after the transfer.
Testing only the homepage. Check representative pages, redirects, forms, APIs, subdomains, and email. A homepage can work while a forgotten MX, TXT, or subdomain record is broken.
When to revisit
Use this checklist before every registrar change, renewal cycle, ownership update, or DNS provider migration. Revisit it before seasonal launches and other periods when downtime or missed email would be costly. It is also worth reviewing after a registrar changes its interface, transfer workflow, verification requirements, privacy controls, or DNS management features.
For a practical final pass, save a dated copy of your nameservers and DNS records, confirm your backups, obtain the authorization code, and schedule the transfer when someone can monitor the website and email. After completion, verify registration status, renewal settings, privacy, nameservers, HTTPS, website pages, and mail delivery. Keep the old registrar and DNS accounts accessible until those checks pass and you have a clear recovery plan.
