Transferring a domain is usually straightforward, but a missed lock, expired payment method, or unplanned DNS change can interrupt a website or business email. This practical domain transfer checklist explains what to prepare, how to protect DNS continuity, where authorization codes fit, and how to verify the move after it is complete.
Overview
A domain transfer moves the registration record from one registrar to another. It does not automatically move your website files, hosting account, content management system, email mailboxes, or DNS configuration. Those services may remain exactly where they are, provided the domain continues to use the correct nameservers and DNS records.
The safest approach is to separate the transfer into three jobs:
- Prepare the domain: confirm ownership, renewal status, eligibility, contact access, and registrar settings.
- Protect continuity: record DNS and email details before starting, and avoid unnecessary changes during the transfer.
- Verify the result: check the domain, website, email, security certificate, and account access after the new registrar shows the transfer as complete.
Before changing anything, identify where the domain’s DNS is hosted. It may be managed by the current registrar, your web host, a website builder, or a separate DNS provider. If you are unsure how the domain connects to hosting, use a DNS setup reference such as this guide to connecting a domain to web hosting.
Checklist by scenario
Before any domain transfer
- Confirm that you can sign in to the current registrar and the account email is accessible.
- Check the domain’s expiration date and confirm that renewal or transfer charges will not be missed during the process.
- Verify the registrant and administrative contact information. Update inaccurate details before requesting a transfer, allowing time for any confirmation steps.
- Review whether the domain is subject to a transfer lock, recent registration restriction, recent contact change, dispute, suspension, or other eligibility condition. Rules can vary by domain extension and registrar.
- Make sure the domain is not in an expired, redemption, or pending-delete stage. Recovery options can become more limited as a domain moves through expiration stages; see this explanation of expired domains and recovery timelines.
- Save a copy of the current DNS zone, including A, AAAA, CNAME, MX, TXT, and any verification records that your services require.
- Note the current nameservers and identify every service that depends on the domain, including website hosting, business email, newsletters, analytics, payment tools, and security services.
- Check whether domain privacy protection or WHOIS protection is enabled. Privacy settings may affect what contact information is visible, but they do not replace accurate registrar account details.
When requesting the authorization code
The authorization code, sometimes called an auth code, transfer code, or EPP code, is issued by the current registrar. Request it through the registrar’s domain management area or support channel, then copy it carefully. Treat the code as account-sensitive information and share it only with the new registrar’s transfer form or a verified support process.
- Request a new code if the first one has expired, been revoked, or is rejected.
- Watch for confusing characters when copying the code, especially zero, the letter O, one, lowercase L, and uppercase I.
- Do not cancel the old registrar account or delete DNS records after receiving the code.
- Keep access to the current registrar until the transfer has been confirmed and tested.
If the website and email must stay online
- Record the DNS values before starting. A screenshot alone can be difficult to search later, so export or copy the records into a simple document as well.
- Confirm that the new registrar will retain the existing nameservers, or prepare to recreate them exactly if the transfer workflow requires a change.
- Do not change hosting, email providers, nameservers, and registrar at the same time unless you have a documented migration plan.
- Keep the existing hosting and email services active until the new arrangement has been tested.
- After the transfer, test the site on both the root domain and the www version if both are used. Send and receive test email from each important mailbox.
If you are moving the domain and hosting together
Handle the domain transfer and website migration as separate workstreams. A domain transfer changes registrar control; a hosting migration changes where the website runs. Before pointing DNS to new hosting, confirm that the site has been copied, the database works, forms submit correctly, redirects are in place, and the SSL certificate setup is ready. For planning costs and renewal commitments, a domain and hosting cost calculator can help separate first-year and ongoing expenses.
What to double-check
Transfer status and approval messages
Submit the transfer at the new registrar using the exact domain name and authorization code. Monitor both registrar accounts and the administrative email address for approval, rejection, or verification messages. Some transfers complete automatically after a processing period, while others provide an option to approve or cancel. The exact workflow depends on the registrar and domain extension, so follow the instructions displayed for your domain.
Nameservers and DNS records
A completed registrar transfer does not guarantee that DNS is correct. Compare the post-transfer nameservers with your pre-transfer notes. Then check records for the website, email, and third-party services. Pay particular attention to MX records for email, TXT records for sender authentication or service verification, and CNAME records used by platforms and subdomains.
Renewal and account settings
Confirm the domain’s expiration date, auto-renewal preference, payment method, and renewal contact at the new registrar. Also check whether privacy protection, two-factor authentication, domain locking, and account recovery details are configured as intended. A low introductory registration price is less important than understanding the renewal terms and maintaining reliable account access.
Website, email, and security
Open the website from a normal browser and test key pages, forms, redirects, and subdomains. Confirm that HTTPS works and that the site does not display a certificate warning. For email, test inbound and outbound delivery, aliases, forwarding, and any connected applications. If something fails, compare DNS records first rather than immediately changing hosting settings.
Common mistakes
- Assuming the transfer moves hosting: The domain registration and website hosting are separate services. A transfer alone does not copy site files or mailboxes.
- Changing nameservers without a record of the old zone: Missing one MX, TXT, or verification record can affect email or connected tools.
- Starting too close to expiration: A transfer can require time for eligibility checks, approvals, or troubleshooting. Begin early enough to avoid relying on a last-minute renewal decision.
- Ignoring account email: Approval and rejection notices may go to the registered contact or registrar account. Confirm access before submitting the request.
- Using an old authorization code: Codes can be regenerated or become invalid. If the new registrar rejects it, return to the current registrar and request or copy the active code again.
- Closing the old account immediately: Keep it available until DNS, email, billing, and transfer status have all been verified.
- Transferring every domain at once: For a portfolio, move one low-risk domain first, document the process, then repeat it for higher-priority domains.
- Forgetting subdomains: A homepage may work while a store, staging site, help center, or campaign subdomain does not. Include every active hostname in the post-transfer test.
When to revisit
Use this checklist whenever you transfer a domain, but revisit it before seasonal planning cycles, a major launch, a registrar change, or a website migration. It is also worth reviewing after a business email change, a new website platform, a portfolio consolidation, or a change in who controls the domain account.
Registrar dashboards and transfer workflows can change, and domain extensions may have different eligibility rules. Before acting, check the current instructions shown by both registrars and the registry or domain extension involved. Do not rely on an old authorization code, saved pricing, or a previous nameserver setup without verifying it.
Practical final check: keep a dated domain inventory with the registrar, expiration date, nameservers, DNS provider, hosting provider, email provider, renewal setting, and account owner. Before submitting a future transfer, update that inventory, export the DNS records, confirm contact access, unlock the domain only when ready, and lock it again after the move is complete. This small record turns a stressful domain transfer into a repeatable maintenance task.
