Transferring a domain does not normally require moving the website, changing its DNS records, or interrupting email. This guide explains how to transfer a domain to a new registrar safely, what to record before starting, how to troubleshoot an authorization code, and which checks confirm that your website and email remained online.
Overview
A domain transfer changes the company that manages your domain registration. It is separate from changing web hosting. Your site files can remain on the same server, and your email can continue using the same provider, as long as the domain's DNS configuration remains intact.
The main risk is not the transfer itself but an avoidable change to the domain's nameservers or DNS records. Before you begin, document the current configuration and confirm that the new registrar will preserve, import, or allow you to recreate the records you need. A careful domain transfer checklist should cover:
- Domain ownership and account access
- Expiration date and renewal status
- Registrar lock or transfer-lock status
- Authorization code, also called an Auth-Code or EPP code
- Nameservers and important DNS records
- Website, email, SSL, and third-party service dependencies
- Transfer confirmation messages and post-transfer tests
Timing varies by registrar, domain extension, account verification, and whether the current registrar or registrant must approve the request. Start early rather than treating a transfer as a last-minute renewal or recovery task.
What to track
1. Record the domain and account details
Write down the exact domain name, current registrar, account username, expiration date, and the administrative or registrant contact used by the registrar. Make sure you can access the account email address. Transfer notices and verification requests may be sent there, and an inaccessible mailbox can delay the process.
Check whether the domain is subject to a transfer lock. Registrars and domain extensions can apply different eligibility rules, including restrictions related to a recent registration, transfer, or registrant-information change. Do not assume a lock can be removed immediately; read the current instructions in the registrar account or contact support before scheduling the move.
2. Save the DNS configuration
Record the domain's current nameservers and export or copy important DNS records. At minimum, check:
- A and AAAA records: commonly used to direct the domain to a web server.
- CNAME records: often used for subdomains and hosted services.
- MX records: used to route email.
- TXT records: may support email authentication, site verification, or other services.
- CAA records: where present, these can influence which certificate authorities may issue SSL certificates.
Also note custom subdomains such as www, mail, app, and api. If DNS is hosted by a separate provider, the transfer may leave those records unchanged. If DNS is hosted at the old registrar, confirm whether the new registrar will copy them or whether you must recreate them manually. See the DNS records troubleshooting guide for a record-by-record reference.
3. Confirm website and email dependencies
Identify where the website is hosted and where email is hosted. A domain transfer is not the same as a website migration, so do not cancel the old hosting account until you have separately confirmed that all site files, databases, backups, and email data are safe.
Before submitting the transfer, test the website over both the root domain and commonly used subdomains. Send and receive a test email, inspect forms that send email, and note any external services that rely on DNS verification. If the site uses HTTPS, confirm that its SSL certificate is valid before and after the transfer.
4. Obtain and protect the authorization code
Request the domain transfer authorization code from the current registrar. The label may differ by provider, but it is commonly called an Auth-Code, EPP code, transfer code, or authorization key. Treat it like a sensitive account credential: share it only through the new registrar's secure transfer workflow, and avoid publishing it in tickets or public messages.
If the code is rejected, copy it carefully without extra spaces and check whether it has expired or been regenerated. If a code is not displayed, look for a registrar-specific request or recovery option. Support may need to verify account ownership before issuing it.
Authorization-code troubleshooting
| Problem | Checks to make | Next step |
|---|---|---|
| Code is rejected | Check spelling, capitalization, spaces, and whether a newer code was issued. | Request a fresh code and submit it again. |
| Transfer is unavailable | Review the domain's lock, recent account changes, expiration status, and extension-specific rules. | Ask the current registrar which eligibility condition is blocking the transfer. |
| Approval email is missing | Check the correct contact mailbox, spam folders, forwarding rules, and account notifications. | Use the registrar's resend option or contact support. |
| DNS appears empty at the new registrar | Determine whether DNS was hosted at the old registrar or by an independent provider. | Keep the existing nameservers if appropriate, or recreate records before changing them. |
Cadence and checkpoints
Before starting
Choose a low-risk period when you can monitor the domain and access both registrar accounts. Back up the website and any domain-related data. Record DNS values, confirm billing details at the new registrar, and verify that the domain's renewal settings match your intentions. A website migration checklist can help identify dependencies beyond the registrar account.
During the transfer
Unlock the domain only when you are ready to submit the request, obtain the authorization code, and enter it at the new registrar. Follow the new registrar's confirmation steps and monitor both accounts for status changes. Do not make unrelated DNS edits during this window unless necessary; minimizing changes makes troubleshooting easier.
Some transfers complete after an approval, while others remain pending for a period determined by the registrars and the domain extension. The exact process can change, so use the current status shown in your registrar accounts rather than relying on a generic timeline.
After completion
Confirm that the domain appears in the new registrar account and that its expiration or renewal information is recorded correctly. Check the registrar lock setting and enable it again if you do not plan another transfer. Review domain privacy settings, since privacy availability and contact-display behavior can vary by registrar and domain extension.
Then verify the nameservers and DNS records. Visit the website from more than one network, load key pages, test contact forms, and send email to and from the domain. A DNS propagation checker can provide useful observations from different locations, but it should supplement—not replace—real website and email tests.
How to interpret changes
If the website and email continue working while the registrar changes, the transfer preserved the operational configuration. A different registrar name alone does not mean that hosting moved. Check the nameservers before assuming a DNS problem.
If the website fails but email works, inspect the A, AAAA, and CNAME records and confirm that the web host is still active. If email fails but the website works, inspect MX records and related TXT records used for email authentication. If both fail, check whether the nameservers changed or whether the new DNS zone is missing records.
Do not immediately change several records at once. Compare the current configuration with the pre-transfer notes, correct the specific missing or incorrect value, and allow time for DNS caches to update. If a certificate warning appears, verify that the domain still points to the intended host and that the host is configured to issue or renew the certificate.
Also compare the total cost and service terms after the move. The first-year transfer charge, future renewal cost, privacy protection, DNS features, account security, and support access can all affect whether the new registrar remains a good fit. The domain registrar comparison guide provides a framework for reviewing those factors without focusing only on the initial transfer.
When to revisit
Review this transfer record at least quarterly for business-critical domains, and before any renewal, hosting migration, ownership change, or registrar consolidation. Policies, transfer eligibility, privacy practices, and pricing can change, so confirm the current registrar instructions before beginning a future transfer.
Use this practical revisit checklist:
- Confirm the domain is still in the intended registrar account.
- Check the expiration date, auto-renewal choice, and payment method.
- Verify the registrar lock and account security settings.
- Review nameservers and compare critical DNS records with your saved copy.
- Test the website, SSL certificate, forms, and domain email.
- Update the domain inventory if hosting, email, DNS, or third-party services changed.
- Refresh this checklist when the registrar publishes new transfer or privacy instructions.
The safest domain transfer is planned as a controlled account change, not an emergency website move. Preserve DNS, keep hosting active, protect the authorization code, and verify every service after completion. With those checkpoints documented, you can transfer a domain without deliberately creating website or email downtime and have a reliable record for the next renewal or registrar review.
