How to Transfer a Domain Safely: Registrar Checklist for DNS, Email, and Renewal
domain transferregistrarsDNSdomain renewalWHOIS privacy

How to Transfer a Domain Safely: Registrar Checklist for DNS, Email, and Renewal

WWebsiteHost Editorial Team
2026-11-16
7 min read

Transfer a domain safely with a practical checklist for registrar locks, authorization codes, DNS, email, renewal dates, and post-transfer testing.

Transferring a domain does not have to interrupt your website or business email. This checklist shows how to prepare the domain, preserve DNS records, approve the transfer, verify every service afterward, and keep renewal dates and registrar settings under control.

Overview

A domain transfer moves the registration from one registrar to another. It is separate from moving your website files, changing your web host, or switching email providers. In many cases, the website and email can continue working during the transfer because the domain’s nameservers remain unchanged. However, a transfer can expose problems if DNS records are incomplete, an authorization code is outdated, a registrar lock is still active, or renewal information is overlooked.

The safest approach is to treat the transfer as a controlled change with three stages: document the current setup, complete the registrar transfer, and verify each dependent service. Before starting, identify the domain owner, the account that controls it, the current nameservers, the expiry date, and the services connected to the domain. If the domain is used for a business, record who is responsible for approving changes and receiving transfer notices.

Do not assume that transferring a domain also transfers hosting, website content, mailboxes, SSL settings, or DNS hosting. Those services may remain with the existing provider or may need separate migration work. If you are also moving the website, use a separate website migration checklist so the domain transfer does not become confused with the hosting change.

What to track

1. Registration status and ownership

  • Confirm that the registrant and administrative contact details are accurate.
  • Check the domain’s expiry date, renewal setting, and payment method.
  • Note whether the domain has a registrar lock or another transfer restriction.
  • Confirm that the current registrar account has access to transfer controls.
  • Check whether privacy protection changes which contact details appear publicly without preventing legitimate registrar notices.

Registrar dashboards use different labels. Look for terms such as “transfer lock,” “domain lock,” “authorization code,” “EPP code,” or “transfer key.” If an option is unclear, check the registrar’s current help documentation before changing it.

2. The authorization code and transfer notices

Request the domain authorization code only through the current registrar’s authenticated account or its documented support process. Treat the code like a credential: do not publish it, place it in an unprotected shared document, or send it to an unverified contact. Record when it was issued because some registrars can replace or invalidate codes.

After starting the transfer at the new registrar, watch the domain owner’s email inbox for approval or verification messages. These messages may come from either registrar or a related registration service. Confirm that the email is genuine by opening the registrar’s website directly rather than relying on a suspicious link.

3. DNS and connected services

Record the current nameservers and export or copy the DNS zone before making changes. At minimum, check the records used by:

  • The website, such as A, AAAA, or CNAME records.
  • Email, especially MX records and related SPF, DKIM, and DMARC TXT records.
  • Subdomains for applications, staging sites, customer portals, or support tools.
  • Domain verification services, analytics, advertising platforms, and payment or ecommerce systems.

A useful reference for this inventory is DNS Records Explained. If DNS is hosted separately from the current registrar, write down that provider and confirm that the transfer will not automatically replace the nameservers.

Cadence and checkpoints

Use the following workflow whenever you transfer a domain. Keep a simple transfer log with dates, account names, approval messages, nameservers, and the final verification results.

  1. Review the domain first. Check ownership, expiry, registrar lock, privacy settings, contact email, and any current transfer restrictions. Avoid beginning just before a critical launch, campaign, renewal deadline, or holiday closure.
  2. Back up the DNS configuration. Copy every record, including records that appear unrelated to the main website. Do not rely only on memory or a screenshot of the DNS page.
  3. Confirm website and email operation. Test the homepage, important forms, login areas, transactional messages, and inbound and outbound email before the transfer. This gives you a baseline for comparison.
  4. Unlock the domain when eligible. Remove the transfer lock only in the current registrar’s account and only when you are ready to submit the transfer. If the option is unavailable, ask the registrar why rather than repeatedly retrying.
  5. Obtain and protect the authorization code. Use the current code at the receiving registrar. Check that the domain name is spelled correctly before submitting payment or confirmation.
  6. Start the transfer and monitor notices. Complete the receiving registrar’s verification steps and watch the registrant email account. Some transfers can be approved through an email or dashboard action; others may proceed through the registrars’ normal process. Follow the instructions currently shown for your domain extension.
  7. Leave DNS stable during the transfer. Unless you are deliberately moving DNS hosting, keep the existing nameservers in place. Changing registrar and nameservers at the same time creates unnecessary troubleshooting variables.
  8. Verify after completion. Confirm the domain appears in the new account, the expiry and renewal settings are understood, privacy protection is configured as intended, and the nameservers and DNS records still match your inventory.

Registrar fees, renewal treatment, approval windows, transfer restrictions, and privacy behavior vary by registrar and domain extension. Check the current terms before starting, especially if the domain is close to expiry or has recently changed ownership or contact details.

How to interpret changes

A successful transfer should not be judged only by seeing the domain in the new dashboard. Compare the post-transfer state with your baseline. The website should resolve over its normal hostname, HTTPS should work, forms should reach their intended inbox, and business email should both send and receive. Test from more than one network or device when practical, because DNS results can differ temporarily as caches update.

If the website fails but email works, inspect the web-related A, AAAA, or CNAME records and confirm that the hosting account still contains the domain. If email fails but the website works, check MX and mail-authentication records before changing anything else. If both services fail, compare the active nameservers with the recorded nameservers and determine where DNS is actually being managed.

Do not immediately delete the old registrar account, DNS zone, or hosting service. Keep access available until the transfer is complete and the dependent services have passed testing. A rollback is not always as simple as reversing the transfer: a completed transfer may have its own timing and eligibility requirements. When the problem is DNS-related, restore the last known-good records at the active DNS provider rather than starting another registrar transfer.

For email-specific checks, review the business email hosting guide. For a site that is also changing servers, verify redirects, certificates, backups, and performance using the relevant Core Web Vitals hosting guidance.

When to revisit

Revisit this checklist before every domain transfer, ownership change, registrar consolidation, or major DNS change. It is also worth reviewing monthly or quarterly for business domains, depending on how many domains and services your organization manages. A recurring review should cover the expiry date, auto-renewal status, payment method, account access, registrar lock, privacy setting, nameservers, DNS provider, and the email address that receives registrar notices.

Update your internal notes whenever you add a subdomain, change email providers, launch an application, or delegate DNS management to another team. Review the process again whenever a registrar changes its dashboard, transfer instructions, fees, privacy controls, or approval requirements. Domain extension rules can also differ, so do not assume that a procedure used for one domain applies to every other domain in your portfolio.

Action plan: choose one domain to audit today, export or copy its DNS records, record its renewal date and nameservers, and test its website and email. Store the checklist in a location your organization can access without exposing authorization codes. After the audit, set a calendar reminder for the next quarterly review and for renewal well before the expiry date. This small maintenance routine makes the next domain transfer easier to verify and less likely to interrupt a service that customers rely on.

Related Topics

#domain transfer#registrars#DNS#domain renewal#WHOIS privacy
W

WebsiteHost Editorial Team

SEO and Web Hosting Editors

Senior editor and content strategist. Writing about technology, design, and the future of digital media. Follow along for deep dives into the industry's moving parts.