Transferring a domain to a different registrar does not usually require moving your website, email, or hosting. This guide provides a reusable domain transfer checklist, explains how to prepare an EPP or auth code request, and shows what to check when a transfer is delayed or fails.
Overview
A domain transfer changes the registrar responsible for managing your domain registration. It is separate from changing your web hosting provider. Your website can remain on the same server while the registrar transfer takes place, provided that the domain’s DNS records continue to point to the correct services.
The safest approach is to prepare the destination registrar first, preserve your existing DNS configuration, and avoid making unrelated changes during the transfer window. A typical transfer requires access to the current registrar account, an unlocked domain, a valid administrative contact email address, and an authorization code known as an EPP code or auth code. Exact labels and screens vary by registrar and domain extension.
Before starting, record the domain’s current expiration date, nameservers, DNS records, renewal settings, and any services connected to the domain. If the domain supports business email, pay particular attention to MX, SPF, DKIM, and DMARC records. A registrar transfer should not remove these records, but documenting them gives you a recovery reference if the new account displays incomplete information.
For background on the records involved, see the DNS records guide. If the broader move also includes your server or hosting provider, use the website hosting migration checklist separately.
Checklist by scenario
Before you transfer any domain
- Confirm that you control the current registrar account and can receive messages sent to the domain’s administrative contact email.
- Check the domain’s expiration date and leave enough time to resolve an unexpected delay before expiration.
- Export or document the current DNS records, nameservers, forwarding rules, renewal settings, and privacy settings.
- Check whether the domain is eligible for transfer. A recent registration, recent transfer, contact change, or other account event may trigger a temporary transfer restriction depending on the extension and applicable policy.
- Disable the registrar lock or transfer lock only when you are ready to submit the transfer. Re-enable it if you pause the process.
- Confirm that domain privacy or proxy settings will not prevent transfer approval messages from reaching you.
- Ensure that your payment method and account details at the destination registrar are ready.
Requesting the EPP or auth code
In the current registrar’s control panel, look for an option labelled transfer, authorization code, EPP code, or domain security. Some registrars display the code immediately; others send it to the registered contact or require an account verification step. Treat the code as sensitive account information and share it only through the destination registrar’s secure transfer form.
If you need to contact support, use this short template:
Subject: Request for domain transfer authorization code
Hello, I am the account holder for [domain.example]. I intend to transfer this domain to another registrar. Please confirm whether the domain is eligible for transfer, identify any active transfer lock or restriction, and provide instructions for obtaining the EPP or auth code. Please send the code through the approved secure channel associated with my account. Thank you.
Starting the transfer at the new registrar
- Open the destination registrar’s domain transfer page and enter the domain name.
- Enter the EPP or auth code exactly as provided. Watch for spaces, capitalization, and similar-looking characters.
- Review the transfer price, renewal term, privacy options, and contact information before payment. Do not assume that a transfer includes the same settings or services as the current registrar.
- Confirm that the destination account uses the correct nameservers or be prepared to re-enter them after the transfer.
- Save the order number and transfer status page.
While the transfer is processing
Monitor email at the registered contact address and both registrar accounts. Some transfers complete after an approval message, while others proceed after a waiting period. The exact time depends on the registrar, domain extension, approval flow, and whether the current registrar releases the transfer early. Avoid changing registrant contact details, nameservers, or DNS providers unless necessary.
Use an uptime monitor or test the website and email from more than one network. The website uptime monitoring guide covers a practical way to detect availability problems during planned changes.
What to double-check
Transfer eligibility and policy holds
Many domain extensions have rules that can place a domain on a temporary transfer lock after registration, a previous transfer, or certain changes to registrant information. The widely discussed 60-day periods are not a substitute for checking the current registrar and registry rules for your specific extension. If a lock applies, ask whether it can be removed, whether an exception is available, and when the domain will become eligible.
DNS continuity
A registrar transfer and a DNS provider change are different operations. If your nameservers remain unchanged, website and email routing should continue through the same DNS provider. If the destination registrar replaces nameservers or imports records incompletely, restore the documented values promptly. Verify A, AAAA, CNAME, MX, TXT, and any verification records used by your services.
Contact and security settings
Check the registrant name, organization, address, phone number, and contact email at the new registrar. Confirm two-factor authentication, recovery methods, transfer lock, auto-renewal, and domain privacy settings. Review whether the transfer changed the domain’s expiration date or added a renewal term, and retain the receipt for your records.
HTTPS and connected services
Changing registrars normally does not replace an SSL certificate. However, DNS or nameserver errors can make a certificate appear broken because the site is no longer reaching the expected server. Check HTTPS, redirects, email delivery, analytics, payment callbacks, API endpoints, and third-party domain verification after completion. For certificate symptoms, consult the SSL certificate troubleshooting guide.
Common mistakes
- Transferring too close to expiration: Start early enough to investigate eligibility, billing, or approval problems. A transfer is not a substitute for renewing an expiring domain.
- Changing DNS at the same time: Keep the registrar transfer separate from a hosting or DNS migration where possible. Fewer simultaneous changes make diagnosis easier.
- Using an old auth code: Request a fresh code if the first one has expired, been regenerated, or is rejected.
- Ignoring the approval email: Check spam folders and confirm that the administrative contact address is current before beginning.
- Assuming every service moves with the domain: Website files, databases, mailboxes, DNS hosting, SSL settings, and backups may remain with other providers.
- Failing to re-lock the domain: Once the transfer is complete, verify the new registrar’s lock and account security settings.
- Not recording the final state: Save the new registrar, renewal date, nameservers, DNS provider, and recovery contacts in your asset inventory.
If a transfer is rejected, first read the exact status message rather than repeatedly resubmitting it. Common categories include an invalid auth code, active transfer lock, ineligible domain, contact verification problem, or billing issue. Ask the current or destination registrar which party must take the next action. If the website is also being moved, keep the hosting work tracked separately; the hosting migration guide can help prevent an unrelated infrastructure change from being mistaken for a domain problem.
When to revisit
Revisit this checklist before every domain transfer, not just the first one. Registrar interfaces, transfer-status labels, authentication flows, pricing, and domain-extension rules can change. Review the current registrar and registry instructions whenever you transfer a less common extension, change registrant information, or work under a tight expiration deadline.
For a practical final pass, complete these actions in order:
- Record the current DNS and account configuration.
- Confirm eligibility, expiration timing, and contact access.
- Unlock the domain and obtain a current EPP or auth code.
- Submit the transfer at the destination registrar and save its reference number.
- Monitor approval messages, website uptime, and email delivery.
- After completion, verify ownership details, nameservers, DNS records, renewal, two-factor authentication, and transfer lock.
Once those checks pass, document the new registrar and schedule a reminder before the next renewal or planned infrastructure change. A repeatable process is the simplest way to transfer a domain without unnecessary downtime or lost account access.
