Transferring a domain to a new registrar is usually straightforward, but a rushed move can interrupt email, expose ownership problems, or leave DNS records unverified. This step-by-step domain transfer checklist shows what to prepare, what to monitor during the move, and which checks to repeat afterward so your website and domain services continue working.
Overview
A domain transfer moves the registration record from one registrar to another. It does not automatically move your website files, databases, mailboxes, or hosting account. Those services may remain where they are, provided the domain’s DNS records continue pointing to the correct servers.
That distinction is important. You can transfer a domain while keeping the same web hosting, or transfer the domain and migrate hosting separately. If both changes are needed, handle them as separate projects and record the existing DNS configuration before making changes. The website hosting migration guide provides a separate checklist for moving site infrastructure safely.
The exact labels in a control panel vary, but the transfer process normally includes these stages:
- Confirm that you control the domain and the registrar account.
- Review contact details, renewal status, and transfer eligibility.
- Unlock the domain if a registrar lock is active.
- Request the domain authorization code, sometimes called an EPP, transfer, or auth code.
- Start the transfer at the new registrar and approve required messages.
- Check registration status, DNS, website access, and email after completion.
Do not cancel the old registrar account immediately. Keep access until the transfer has completed and you have confirmed that the new registrar displays the correct domain, nameservers, expiration information, and management options.
What to track
1. Ownership and account access
Before you begin, sign in to the current registrar and verify that the domain appears in your account. Check the registrant name, organization, and email address for accuracy. The registrant email may be used for important confirmations, so make sure it is monitored and not tied solely to the domain you are transferring.
Also confirm that you can access the account at the new registrar. Use a strong, unique password and enable available account security controls. A transfer is an ownership-sensitive operation; avoid starting one from a shared or unverified account.
2. Domain status and transfer lock
Look for a status such as transfer locked, registrar lock, or client transfer prohibited. If the domain is locked, the new registrar will generally be unable to begin the transfer until you disable the lock at the current registrar. Some registrars separate the lock setting from privacy settings, so check both the domain overview and security sections.
Transfer eligibility can also be affected by recent registration, a recent transfer, pending ownership changes, or registry-specific rules. Because requirements vary by domain extension and registrar, review the current instructions shown in your account before proceeding. If the control panel reports that the domain is ineligible, resolve that issue rather than repeatedly submitting transfer requests.
3. Authorization code
Request the domain authorization code from the current registrar. It may be displayed immediately, emailed to an approved contact, or provided after an account-security check. Treat this code like a credential: do not publish it, and enter it only in the transfer form at the registrar you selected.
If the code is rejected, copy it carefully and check for spaces, similar characters, or an expired code. Requesting a new code may invalidate an earlier one, so use the latest code provided by the current registrar.
4. DNS and service records
Record the domain’s current nameservers and important DNS records before starting. At minimum, review:
- A and AAAA records: commonly used to direct the domain to web servers.
- CNAME records: often used for subdomains and hosted services.
- MX records: used to route email.
- TXT records: commonly used for verification and email security policies.
- NS records: identify the authoritative DNS service.
A registrar transfer does not necessarily change nameservers, but a new account may present an option to use its default DNS service. Do not accept a replacement DNS configuration unless you have copied the required records and intend to manage DNS there. For a record-by-record explanation, see DNS Records Explained.
5. Transfer messages and deadlines
Track every transfer email, approval request, and status message. Some transfers require approval from a domain contact or within a registrar dashboard. Others may proceed after a waiting period if no action is taken. The instructions shown for your domain should take priority because procedures differ by registrar and domain extension.
Cadence and checkpoints
Use the following sequence as a practical domain transfer checklist.
Before submitting the transfer
- Confirm the domain name and extension.
- Verify account access at both registrars.
- Check registrant contact details and monitor the associated email.
- Review expiration, renewal, and transfer eligibility information.
- Unlock the domain if required.
- Obtain a current authorization code.
- Save nameserver and DNS records.
- Check that your website, email, SSL certificate, and important subdomains work before the change.
While the transfer is pending
Check the transfer status in the new registrar’s dashboard and watch for approval requests. Avoid changing nameservers, DNS providers, hosting, and email routing at the same time unless there is a clear operational reason. Keeping the existing DNS arrangement reduces the number of variables if a service becomes unreachable.
If the transfer appears stuck, compare the dashboard status with the instructions from both registrars. Common causes include a locked domain, an invalid authorization code, an unapproved request, inaccurate contact information, or an eligibility restriction. Contact the relevant registrar with the domain name and transfer status, but do not share account passwords or authorization codes unnecessarily.
After completion
When the new registrar shows the domain as active, verify the following from an external connection as well as your local network:
- The website loads at the root domain and key subdomains.
- HTTP redirects to HTTPS as expected.
- SSL certificates show no browser warnings. For troubleshooting, see SSL Certificates Explained.
- New and existing email can be sent and received.
- DNS records still point to the intended hosting and service providers.
- The domain’s renewal date, nameservers, privacy settings, and auto-renewal preference are correct.
- Two-factor authentication and recovery details are configured at the new registrar.
Keep the old registrar account and transfer records until these checks pass. If DNS was accidentally replaced, restore the saved nameservers or records and allow time for DNS changes to become visible across networks.
How to interpret changes
A successful domain transfer should change who manages the registration without changing where the domain’s services operate. If the website stops loading but email continues to work, investigate web-related A, AAAA, or CNAME records. If the website works but email fails, inspect MX records and any related TXT records. If only one subdomain fails, compare that subdomain’s record with the saved DNS configuration.
A registrar dashboard may display different statuses during the process. “Pending” generally means the transfer is still being processed or awaits an action; “failed” calls for reviewing the stated reason; and “completed” means the registration move has finished, not that every DNS or hosting service has been tested. Treat the dashboard as one checkpoint, then confirm real-world service behavior.
Be cautious when a registrar offers optional extras during checkout, such as a new DNS service, forwarding configuration, or privacy setting. These may be useful, but changing them during a transfer can make troubleshooting harder. Decide deliberately and document the final configuration.
If the domain is close to expiration, the transfer may require additional planning. Review the expiration and renewal information shown by both registrars, and confirm how the transfer affects the registration term for the relevant domain extension. Do not assume that every extension follows the same renewal or transfer treatment.
When to revisit
Revisit this checklist whenever you transfer another domain, change registrars, move DNS providers, or prepare for a hosting migration. A monthly or quarterly domain-management review is also useful for business-critical domains. At each review, confirm the registrar account owner, recovery email, two-factor authentication, auto-renewal setting, expiration date, nameservers, and DNS records.
Keep a simple domain inventory with the domain name, registrar, renewal date, DNS provider, hosting destination, email provider, and responsible account owner. Update it after every transfer or DNS change. This turns a one-time transfer into a repeatable operational process and makes ownership clear when several people manage infrastructure.
Before your next transfer, first complete the preparation checks, export or record DNS, and test current services. During the move, monitor status messages and avoid unrelated configuration changes. After completion, verify the website, email, SSL, DNS, renewal settings, and account security. If you need to move the website as well as the registration, pair this checklist with the hosting migration guide and keep the two workstreams documented separately.
