Transferring a domain name does not have to interrupt your website, email, or other online services. This guide explains how to prepare the domain, preserve DNS records, request the authorization code, monitor the transfer, and confirm that renewal and ownership details remain correct after the move.
Overview
A domain transfer moves the registration from one registrar to another. It does not automatically move your website files, database, hosting account, mailboxes, or DNS zone. That distinction is the foundation of a safe transfer.
Your website and email can continue working during a registrar transfer when the domain keeps using the same nameservers and the existing DNS records remain available. The main risks come from changing several services at once, allowing the domain to expire during the process, overlooking a DNS record, or losing access to the administrative email address used for transfer approval.
Use this workflow when changing registrars, consolidating domains, moving ownership, or reviewing domain and hosting costs. If you are also moving the website to new infrastructure, treat that as a separate project. The website migration checklist can help you plan the hosting portion without combining unrelated changes.
Before starting, record the current state of the domain:
- Registrar name, account access, and domain expiration date.
- Registrant, administrative, and technical contact details.
- Current nameservers and all important DNS records.
- Website hosting provider, email provider, and any third-party services connected to the domain.
- Auto-renewal status, renewal terms, and payment method.
- Any recent ownership, contact, or nameserver changes that could affect transfer eligibility.
Do not cancel the old registrar account or hosting service immediately after submitting a transfer. Keep the existing setup available until the new registrar, DNS, website, and email have all been verified.
What to track
1. Registration status and transfer eligibility
Confirm that the domain is active, has not expired, and is not subject to a transfer restriction. Many domains have a registrar lock that must be disabled before an outbound transfer. Some registries or recent account changes may create additional restrictions, so check the current registrar and registry instructions rather than relying on a generic timeline.
Also verify that the domain extension supports the transfer process you expect. Transfer steps, approval methods, fees, and renewal treatment can vary by registry and registrar. The receiving registrar should explain its process before you begin.
2. The domain authorization code
The authorization code, sometimes called an EPP code, transfer code, or auth code, is a credential used to approve a domain transfer. Request it through the current registrar and store it securely. Codes may be displayed in an account dashboard, delivered through an approved channel, or provided after an identity check.
Enter the code exactly as provided. If it is rejected, do not repeatedly guess. Request a fresh code or ask the current registrar to confirm whether the code has expired or been replaced.
3. Nameservers and DNS records
Copy the complete DNS zone before making changes. At minimum, review the A and AAAA records for the website, CNAME records for subdomains, MX records for email, and TXT records used for email authentication, verification, or security services. Note any SRV, CAA, or custom records used by applications.
A registrar transfer normally does not require a nameserver change, but a DNS provider may be bundled with the old registrar. Confirm whether the current nameservers will remain active after the transfer. If the old registrar hosts the DNS zone and will deactivate it when the registration leaves, recreate the zone with another DNS provider before transferring the domain. The DNS records guide explains what each common record does and what to check.
4. Website, email, and business dependencies
List the services that depend on the domain, including the main site, subdomains, transactional email, customer support mailboxes, marketing platforms, payment or checkout tools, analytics, remote access, and developer systems. Test a representative page, form, mailbox, and subdomain before the transfer so you have a baseline for comparison afterward.
For a business website, a short transfer log is useful. Record the date and time of each action, the person who approved it, and the result of each test. This makes troubleshooting more precise if a record is missing or an approval email is delayed.
Registrar comparison checklist
| Item | What to compare | Why it matters |
|---|---|---|
| Transfer process | Authorization-code delivery, approval steps, and status visibility | Reduces delays and makes the move easier to monitor |
| DNS management | Record controls, zone access, and nameserver options | Helps preserve website and email continuity |
| Renewal details | New expiration date, renewal settings, and billing controls | Prevents unexpected expiry or duplicate assumptions |
| Account security | Multi-factor authentication, access roles, and recovery options | Protects a high-value business asset |
| Support | Available channels and escalation process | Provides a path forward if the transfer is delayed |
Cadence and checkpoints
Use the following sequence to transfer a domain without avoidable downtime.
- Choose the receiving registrar. Confirm that it supports the domain extension and clearly displays transfer status, DNS controls, renewal information, and account security settings.
- Back up the current DNS configuration. Export the zone if the provider supports it, or create a written copy of every record, value, priority, and TTL. Save the current nameservers separately.
- Check the expiration date. Start early enough to resolve an account, payment, or authorization issue. Avoid beginning a transfer when the domain is close to expiry unless you have confirmed the appropriate process with both registrars.
- Verify contact and account access. Make sure you can receive messages at the approved email address and can sign in to both registrar accounts. Check spam filtering and organizational mail rules.
- Disable the registrar lock. Use the current registrar dashboard or support process. Confirm that the status has changed before submitting the transfer.
- Request the authorization code. Keep the code private and use the current version supplied by the registrar.
- Start the transfer at the receiving registrar. Enter the domain and authorization code, review the displayed price and renewal information, and submit the request.
- Approve when required. Watch for an approval message or account notification. Some transfers proceed after a waiting period, while others can be confirmed through an account or email workflow.
- Monitor both registrar accounts. Keep notes on the transfer status and any requested action. Do not change nameservers, DNS records, hosting, and email settings at the same time unless there is a separate reason to do so.
- Verify after completion. Confirm the domain appears in the new account, the expiration date is understood, the nameservers are correct, and the transfer lock is enabled if appropriate.
During the transfer, check the website from more than one network and send a test message to and from each important mailbox. A simple uptime monitor can help identify an unexpected DNS or hosting issue; see the website uptime monitoring guide for practical monitoring and alerting considerations.
How to interpret changes
A successful registrar transfer should not, by itself, change the website content or mail routing. If the website stops resolving, compare the active nameservers with your recorded values first. If the nameservers changed, inspect the new DNS zone for missing A, AAAA, or CNAME records. If the website loads but email fails, check MX and related TXT records before changing mail settings.
Not every apparent change is caused by the transfer. A hosting outage, an expired SSL certificate, an application deployment, or a separate DNS edit can produce similar symptoms. Compare the timing of the incident with your transfer log and test the affected service directly.
If the transfer is rejected, review the domain lock, authorization code, contact email, expiration status, and any recent account changes. If the transfer remains pending, check both registrar dashboards and contact the appropriate support team rather than submitting multiple competing requests.
If the new registrar reports a different expiration date than expected, pause before assuming something went wrong. Transfer and renewal handling can differ by domain extension and registrar. Review the transaction confirmation and registry-specific terms, then ask the receiving registrar to explain the resulting date in writing.
For rollback planning, leave the old DNS provider and hosting account intact until the new setup has passed your tests. A registrar transfer itself may not be reversible in the same way as a DNS edit, so the practical rollback is usually to restore the known-good nameservers and DNS records, if those services remain available. Keep an up-to-date backup of the website and database as well; the website backup guide covers restore testing and retention decisions.
When to revisit
Revisit this checklist whenever you transfer, renew, sell, acquire, or change control of a domain. A quarterly review is practical for business-critical domains, while a monthly review may be appropriate for domains supporting active campaigns, frequent product launches, or several third-party services.
At each review, confirm the expiration date, auto-renewal setting, payment method, registrar lock, account recovery details, multi-factor authentication, nameservers, DNS records, and responsible owner. Remove former administrators and verify that the current team can access the registrar without relying on one person’s private mailbox.
Update your records after any change to hosting, email, DNS, or ownership. If you are planning a larger infrastructure move, separate the domain transfer from the hosting migration and schedule a clear verification window. The hosting migration guide provides a separate workflow for moving site infrastructure while keeping the domain stable.
Before closing the task, complete this final action list:
- Save the final registrar, expiration, and renewal information.
- Confirm nameservers and compare the live DNS zone with your backup.
- Test the homepage, key forms, subdomains, and priority mailboxes.
- Confirm SSL, email authentication, and third-party verification records.
- Enable appropriate account security and remove outdated access.
- Keep the old provider available until normal website and email operation is confirmed.
A domain transfer is complete only when ownership, renewal, DNS, website, and email have all been verified. Treat the domain as a business dependency rather than a one-time purchase, and future transfers or ownership changes will be easier to control.
