How to Transfer a Domain Safely: EPP Codes, DNS, Locks, and Renewal Timing
domain-transferregistrarepp-codedomain-renewaldns-management

How to Transfer a Domain Safely: EPP Codes, DNS, Locks, and Renewal Timing

MMegastorage Editorial Team
2026-11-15
7 min read

Transfer a domain safely with a practical checklist for EPP codes, locks, DNS, email continuity, renewal timing, and post-transfer checks.

Transferring a domain is usually straightforward, but a rushed move can interrupt a website, email service, or DNS-based security control. This guide explains how to transfer a domain safely, including the pre-transfer checklist, EPP or authorization codes, domain locks, privacy settings, DNS and email continuity, transfer statuses, renewal timing, and the checks to complete after the move.

Overview

A domain transfer moves management of a domain from one registrar to another. The domain name itself does not change, and the website files normally remain wherever they are hosted. The registrar manages the domain registration, renewal, contact information, transfer controls, and often the authoritative nameserver settings.

The safest approach is to separate the transfer into three areas:

  • Registration control: Confirm ownership, unlock the domain, obtain the EPP or authorization code, and approve the transfer when required.
  • DNS continuity: Preserve nameservers and DNS records unless you intentionally plan to move DNS management as part of the project.
  • Service verification: Check the website, email, SSL certificate, redirects, authentication records, and renewal date after the transfer.

Before starting, record the current registrar, expiration date, nameservers, DNS provider, hosting provider, email provider, and administrative contacts. A screenshot or exported DNS zone can provide a useful reference, but verify whether the receiving registrar imports records automatically before relying on an import.

What to track

Pre-transfer checklist

Use this checklist before you submit a transfer request:

  1. Confirm the domain is eligible. Check the domain status, expiration date, registrar account, and any transfer restrictions. Some extensions have their own procedures, so review the receiving registrar's instructions for the specific extension.
  2. Verify account access. Make sure you can sign in to the current registrar and receive messages sent to the registrant or administrative contact. Update contact details before beginning if access is uncertain.
  3. Review the transfer lock. Many registrars use a lock to prevent unauthorized transfers. Remove it through the current registrar's control panel only when you are ready to transfer, then confirm that the status has changed.
  4. Request the EPP or authorization code. This code may be called an auth code, transfer code, or authorization key. Copy it carefully, keep it private, and use the most recent code if the registrar issues a replacement.
  5. Record DNS settings. List A, AAAA, CNAME, MX, TXT, CAA, and other records that support the website, email, verification services, and security tools. The DNS records guide can help identify what each record does.
  6. Check renewal timing. Avoid starting immediately before an important renewal, launch, migration, or marketing campaign. Confirm how the receiving registrar handles the expiration date and any transfer-related renewal treatment before paying.
  7. Confirm billing and privacy settings. Compare renewal terms, supported payment methods, account security, privacy features, DNS tools, and support channels. Do not compare only the initial registration price.
  8. Create a backup plan. Keep a recent website backup and an offsite copy of important configuration data. A registrar transfer should not alter website files, but a documented recovery path reduces risk if several changes happen together.

EPP codes, locks, and privacy

An EPP or authorization code is a registrar-issued credential used to demonstrate that the requester has control of the domain account. It is not the same as the registrar account password. Treat it as sensitive information: obtain it through the registrar's authenticated account or its approved support process, and do not publish it in tickets, chat rooms, or shared documents.

Domain privacy can affect which contact details are displayed in public registration records, but it does not remove the need for accurate account and registrant information. Check which email address receives transfer notices and verification messages. If a privacy service forwards mail, test that forwarding before you start.

Registrar interfaces use different labels for locks and transfer controls. Look for terms such as domain lock, transfer lock, or registrar lock. If the control is unavailable, contact the current registrar and ask what condition is preventing the change rather than repeatedly submitting transfer requests.

Registrar comparison table

Area to compareQuestions to ask
RenewalWhat renewal term and price will apply, and where is the next expiration date shown?
DNS managementCan you edit common records, use DNSSEC if needed, and control nameservers without contacting support?
SecurityAre multi-factor authentication, account alerts, and domain-lock controls available?
PrivacyWhat contact information is displayed, and how are legitimate notices delivered?
SupportHow can you resolve a failed transfer, incorrect status, or inaccessible authorization code?
Portfolio managementCan you manage multiple domains, roles, billing contacts, and renewal reminders efficiently?

Cadence and checkpoints

Before submitting the transfer

Lower the risk of downtime by leaving the existing nameservers in place during the registrar move. A registrar transfer and a DNS-provider migration are separate changes. If you move both at once, troubleshooting becomes harder because it is unclear whether a failure comes from the registrar, nameservers, or individual records.

Check that the current DNS zone contains the records needed by your hosting and email providers. Pay particular attention to MX records, SPF, DKIM, DMARC, CAA, domain-verification TXT records, and subdomain records used by applications or APIs. For email-specific checks, review the SPF, DKIM, and DMARC guide.

During the transfer

Submit the transfer at the new registrar using the correct domain and current authorization code. Track the request ID, submission time, confirmation messages, and any action requested from the current registrar. Transfer statuses may include pending, awaiting approval, approved, rejected, failed, or completed; the exact wording varies by registrar and domain extension.

A pending status does not always indicate a problem. Read the message beside the status and check whether approval is waiting from you, the current registrar, the receiving registrar, or a contact email. Do not cancel and restart a request until you understand the reason, because a new request may require a new code or restart the waiting period.

After completion

When the transfer is marked complete, verify the following rather than assuming everything carried over:

  • The domain appears in the new account and the registrant or administrative details are correct.
  • The expiration date and renewal settings match your records.
  • The nameservers are unchanged, unless a DNS migration was intentional.
  • The main domain, key subdomains, redirects, and web applications load correctly.
  • Inbound and outbound email work, including messages sent to important addresses.
  • SSL certificates remain valid and browsers do not show certificate warnings.
  • TXT-based verification, SPF, DKIM, DMARC, and CAA records are still present where required.
  • Domain lock, multi-factor authentication, recovery contacts, and renewal reminders are enabled as appropriate.

How to interpret changes

If the website stops loading after a transfer, compare the current nameservers and A or AAAA records with the values documented before the move. If only one subdomain fails, inspect its specific record rather than changing the entire DNS zone. If the site loads but email fails, check MX records first, followed by SPF, DKIM, and DMARC configuration.

If a transfer is rejected, verify the authorization code, domain lock, contact email, account ownership, and any extension-specific eligibility requirements. A recently changed contact or registration detail may also affect the transfer process. Because registrar policies and domain-extension rules can change, use the current registrar instructions for the exact reason and next step.

If the domain appears to have disappeared from an account, do not immediately register it again. Confirm the account, extension, transfer status, expiration state, and support case first. Domains in an expired, suspended, or redemption-related state may follow different procedures and timelines.

For operational context, keep a simple change log containing the old registrar, new registrar, authorization-code request, lock changes, nameservers, DNS edits, approval messages, and verification results. This is especially useful for domains supporting production systems, customer email, or multiple hosting environments.

When to revisit

Review your domain-transfer readiness quarterly and whenever a domain approaches renewal, changes ownership, moves hosting, or supports a new email or application service. A recurring review should confirm that registrar access works, multi-factor authentication is enabled, contact details are current, renewal reminders reach the right people, and the documented DNS zone still matches production.

Revisit this checklist immediately before any transfer, even if you completed one recently. Registrar interface labels, transfer requirements, privacy behavior, renewal treatment, and extension-specific rules can change. Confirm the current instructions instead of relying on an old screenshot or authorization code.

For a practical final pass, schedule a maintenance task or calendar reminder that checks domain expiration, DNS records, certificate status, and backup availability. You can use a cron jobs guide for recurring technical checks, and pair the process with a monthly hosting security audit. Once the transfer is complete, save the new registrar details and verification results in your infrastructure documentation so the next renewal or ownership change starts with reliable information.

Related Topics

#domain-transfer#registrar#epp-code#domain-renewal#dns-management
M

Megastorage Editorial Team

Technology and Infrastructure 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.