How Domain Transfers Work (And How to Avoid Common Problems)

A domain transfer moves your domain registration from one registrar to another without changing the domain name itself. Your website, email, and existing DNS settings can usually continue working during the transfer, provided the underlying services remain active.

For common extensions such as .COM, .NET, and .ORG, the process typically involves checking transfer eligibility, unlocking the domain, obtaining an EPP/Auth Code, submitting the request to the new registrar, and waiting for the registry to complete the change.

Most standard gTLD transfers take approximately 5-7 days from preparation to completion, although individual cases vary. Under ICANN’s current Transfer Policy, the registry normally completes an eligible transfer within five calendar days after receiving the request unless a valid rejection is submitted.

Some transfers finish sooner. Others are delayed by registration restrictions, authorization problems, or extension-specific rules.

This guide explains how domain transfers work, when the 60-day restrictions apply, what different transfer statuses mean, and how to avoid problems that could affect your domain, website, or email.

How Does a Domain Transfer Work?

Three parties are involved in a standard registrar transfer:

• Losing registrar: The company currently managing your domain registration.
• Gaining registrar: The company you are moving your registration to.
• Registry operator: The organization maintaining the official registration database for the domain extension.

You initiate the transfer through the gaining registrar. The registry processes the request according to the applicable rules.

Here is how the process usually works for a standard gTLD.

These stages do not represent six separate waiting periods.

Step 1: Check Whether Your Domain Can Be Transferred

Before paying a transfer fee, review your domain’s:

• Initial registration date
• Most recent inter-registrar transfer date
• Recent registrant contact changes
• Current expiration date
• EPP status codes
• Applicable registry restrictions

Some domains may be temporarily ineligible because they were recently registered or transferred.

Others may be affected by a Change of Registrant lock, legal dispute, or registry-level restriction.

A domain approaching expiration may require additional attention even if it is technically eligible for transfer.

Step 2: Unlock Your Domain

Many registrars protect domains against unauthorized transfers by enabling a transfer lock.

The most common EPP status associated with this protection is:

clientTransferProhibited

When this status is active, the registry will not complete an ordinary inter-registrar transfer.

You can usually remove the lock through your current registrar’s domain management or security settings.

If the domain displays serverTransferProhibited, the restriction is controlled at the registry level. You will normally need assistance from your current registrar to investigate or remove it.

Important: Your domain does not need to display only ok to be eligible for transfer. Other EPP statuses can coexist with an otherwise transferable domain.

What matters is whether a transfer-prohibiting restriction or another applicable policy prevents the requested transfer.

Step 3: Obtain Your EPP or Authorization Code

An EPP/Auth Code is a security credential used to help identify the registered domain holder during a transfer.

Depending on the registrar, it may be called:

• EPP Code
• Auth Code
• AuthInfo Code
• Authorization Code
• Transfer Code

For standard ICANN-governed gTLD transfers, you obtain this code from your current registrar.

Under ICANN’s Transfer Policy, if your registrar does not provide a self-service mechanism to generate and manage your code, it must provide the applicable unique AuthInfo code within five calendar days of your request.

The same policy establishes requirements for removing a registrar transfer lock when the holder cannot remove it through self-service.

An Auth Code is not your registrar account password, and possessing one does not override an existing transfer prohibition.

Treat the code as sensitive information and provide it only through the authorized transfer process.

For detailed instructions, read What Is a Domain Transfer Authorization Code (EPP Code), and Where Do I Find It?.

Step 4: Submit the Transfer Request

Once the domain is eligible and unlocked, visit the gaining registrar’s transfer page.

Enter the domain name, provide the required authorization information, review the price and terms, and complete the order.

Depending on the registrar and extension, you may also need to complete additional verification or confirmation.

Does every domain transfer require clicking an approval email?

Not necessarily.

ICANN’s Transfer Policy includes authorization and notification requirements, but the exact customer-facing process can vary. ICANN has also deferred enforcement of part of the gaining registrar’s standardized Form of Authorization (FOA) requirement.

Therefore, an email approval link should not be described as a universal requirement for every gTLD transfer.

Nevertheless, you should keep access to your registered contact email and monitor messages from both registrars. If a specific approval or verification step is required, failing to complete it may delay or prevent the transfer.

Step 5: Wait for Registry Processing

After the gaining registrar submits an eligible gTLD transfer request, the registry processes it under the applicable transfer policy.

The losing registrar may approve the request early or reject it for a valid reason.

Under ICANN’s current policy, if the losing registrar does not respond within five calendar days of the registry notification, the transfer normally receives default approval.

A domain may display the EPP status:

pendingTransfer

This generally means the registry has received a transfer request and processing is underway.

It does not automatically indicate a problem.

Step 6: Verify the Transfer Is Complete

When the transfer finishes, confirm that:

• The gaining registrar is recorded correctly.
• The domain appears in your new registrar account.
• The expiration date reflects the applicable transfer terms.
• Your nameservers and DNS records are functioning.
• Your website and email remain accessible.
• Your renewal, account security, and contact settings are correct.

If appropriate, re-enable the registrar transfer lock to protect against unauthorized transfers.

For the official requirements, see ICANN Transfer Policy.

When Does the 60-Day Domain Transfer Restriction Apply?

The 60-day rule is one of the most misunderstood parts of domain transfers.

For ICANN-governed gTLDs, several different situations may involve a 60-day restriction, but they do not all operate in exactly the same way.

Why Changing Your Registrant Details Can Delay a Transfer

Suppose you own example.com and want to move it to another registrar.

Before transferring, you change the registrant email address.

Depending on the circumstances, this change may qualify as a material Change of Registrant.

Under the current ICANN policy, a registrar must generally impose a 60-day inter-registrar transfer lock after such a change unless it offered an opt-out and the registrant selected that option before the change.

Your transfer could therefore be delayed even though the domain is several years old.

If you plan to change both the registrar and the registrant details, confirm the correct sequence before making either change.

Does Renewing a Domain Trigger a New 60-Day Lock?

No. An ordinary renewal does not itself trigger ICANN’s general 60-day inter-registrar transfer restriction.

However, the timing of a renewal can affect the registration term credited during a subsequent transfer.

This is especially relevant when a domain has expired and entered an auto-renew grace period.

That issue is different from a transfer lock and is explained later in this guide.

How Long Does a Domain Transfer Take?

For many common gTLDs, planning for approximately 5-7 days is reasonable.

However, the five-calendar-day registry processing period does not necessarily begin when you first place an order.

Preparation and verification can add time before the request reaches the registry.

Example: A Normal Domain Transfer

You unlock your .COM domain on Monday, obtain the Auth Code, and submit the transfer request.

The gaining registrar verifies the necessary information and sends the request to the registry.

If the registry receives the request that day and the losing registrar does not reject it, the transfer will normally complete within the applicable five-calendar-day processing period.

It may also complete earlier if the losing registrar approves or releases it sooner.

Example: A Transfer That Appears Stuck

You submit a transfer order on Monday, but your domain remains locked.

The gaining registrar cannot successfully submit the eligible transfer request to the registry.

By Friday, your registrar dashboard still says “Pending.”

In this situation, the five-day registry processing period may not have started at all.

Waiting another five days will not solve the lock problem.

The most useful question is: Has the request reached the registry, or is it still awaiting action at the registrar?

This distinction helps you identify whether to wait, unlock the domain, correct the Auth Code, or contact support.

Domain Transfer Status Codes Explained

A registrar dashboard status and an official EPP domain status are not always the same.

For example, “Pending Transfer” in a customer account may describe an order that has not yet reached the registry.

The official EPP status pendingTransfer, however, indicates that a transfer request has been received and is being processed at the registry level.

Here are the most relevant codes.

A domain displaying clientHold or serverHold may have serious service or compliance issues, but those codes should not be confused with transfer-specific prohibitions.

To understand the authoritative definitions, see ICANN EPP Status Codes.

Why Do Domain Transfers Fail?

When a transfer fails, repeating the request without identifying the cause usually wastes time.

The correct solution depends on where the process stopped.

What If Your Registrar Refuses to Provide the EPP Code?

For gTLDs covered by ICANN’s Transfer Policy, registrars must provide an appropriate mechanism for obtaining the authorization code.

If the code is not available through self-service, the registrar generally must provide it within five calendar days of the registered name holder’s request.

If your registrar fails to meet the applicable obligation, keep records of your request and contact ICANN through its transfer complaint process.

You can review ICANN's Auth-Code guidance.

What If the Losing Registrar Rejects the Transfer?

Request the exact reason.

Depending on the circumstances, valid denial grounds can include fraud, certain unresolved identity disputes, applicable court orders, specified domain dispute proceedings, transfer restrictions, and qualifying payment issues.

Under ICANN’s policy, a registrar cannot deny an otherwise eligible transfer for arbitrary reasons.

If the stated explanation appears inconsistent with the applicable rules, document the rejection and use the registrar’s escalation procedure. ICANN’s transfer complaint process may also be available for covered gTLDs.

Will a Domain Transfer Affect Your Website, Email, or DNS?

A registrar transfer does not automatically transfer your hosting, move your website, or change your email provider.

In a standard registrar change, the domain can continue using its existing nameservers.

However, uninterrupted service depends on whether your DNS hosting remains active and properly configured.

If Your DNS Is Hosted by an Independent Provider

Suppose your domain is registered at Registrar A, but its authoritative DNS is hosted by a separate DNS provider.

You transfer the registration to Registrar B without changing the nameservers.

Your website and email can normally continue working because the DNS provider has not changed.

If Your Current Registrar Also Hosts Your DNS

This situation requires extra care.

Some registrars provide DNS hosting only while the domain remains under their management or while a related service remains active.

After the transfer, that DNS service might be discontinued.

If the old DNS zone disappears, your website or business email could stop working even though the registrar transfer itself succeeded.

Before starting, confirm whether your old registrar will continue hosting your DNS records.

DNSSEC Also Matters

If DNSSEC is enabled, the registry may hold DS records associated with the current DNS configuration.

Changing DNS providers or cryptographic keys without coordinating the DNSSEC settings can cause DNS validation failures.

Before transferring a business-critical domain, save the existing nameservers and DNS records, check DNSSEC, and avoid combining several major infrastructure changes unless you have a verified migration plan.

It is generally safer to separate a registrar transfer from a DNS migration.

Also note that nameserver modifications may be unavailable while a transfer is being processed. Make any necessary preparations before submitting the request.

Do ccTLDs Follow the Same Transfer Rules?

Not always.

ICANN’s standard inter-registrar Transfer Policy governs covered generic top-level domains (gTLDs), such as .COM, .NET, and .ORG.

Country-code top-level domains (ccTLDs) follow the rules established by their respective registry operators.

Some use familiar authorization codes, while others have different procedures, timelines, fees, or registration requirements.

Two examples show why extension-specific checks matter.

.DE: Provider Transfers Through AuthInfo

Germany’s .DE registry, DENIC, operates an AuthInfo-based provider transfer process.

The domain holder obtains the appropriate AuthInfo through the current provider.

The new provider then submits the authorization information to DENIC.

When the information is valid and the applicable requirements are met, the provider transfer can be completed immediately at the registry level.

This differs from the standard five-calendar-day gTLD processing model.

Official reference: DENIC Provider Transfer.

.UK: Existing IPS TAG Process and the 2027 Transition

As of October 2026, .UK registrar changes operate under Nominet’s existing system, which uses registrar TAGs, commonly referred to as IPS TAGs, rather than the standard .COM-style AuthInfo transfer process.

However, this system is changing.

Nominet has confirmed that its .UK Standardisation transition is scheduled for February 9, 2027. The programme introduces a new inter-registrar transfer policy and Transfer Authorisation Codes (TACs).

Those future arrangements should not be treated as already effective in October 2026.

Until the transition, .UK registrants should follow the currently applicable registrar-change process and confirm the required steps with their registrar.

Official reference: Nominet .UK Policies.

What Should You Check Before Transferring a ccTLD?

Confirm whether the extension requires an Auth Code, TAG change, registry approval, or another authorization method.

Also verify whether the transfer changes the expiration date, whether a fee applies, and whether registration eligibility or local-presence requirements must be satisfied.

A .COM transfer checklist is a useful starting point, but it should not be applied automatically to every ccTLD.

Can You Transfer an Expired or Recently Renewed Domain?

Sometimes, but it depends on the domain’s current lifecycle stage and applicable policies.

An expired domain is not necessarily deleted immediately.

For certain gTLDs, a transfer may still be possible during an eligible post-expiration period. However, restoration or deletion stages can prevent an ordinary transfer.

If your domain has already expired, check its exact status and recovery options before submitting a transfer request.

For a business-critical domain, preserving the registration should take priority over moving it immediately.

Does a Domain Transfer Add One Extra Year?

For many standard gTLDs, a successful inter-registrar transfer normally extends the registration period by one year, subject to the applicable maximum registration term.

However, the final expiration date may not increase by an additional full year in certain situations.

One important example involves the auto-renew grace period after expiration.

For affected gTLDs, a transfer during that period can result in the registry reversing the automatically added renewal year and applying the transfer extension instead.

Consequently, you may not receive two additional years even if you recently paid the losing registrar to renew and then paid the gaining registrar to transfer.

Refund treatment for the previous renewal may also differ between registrars.

Important for customers transferring to NiceNIC: NiceNIC’s published transfer-in guidance advises customers who renewed an expired domain with their previous registrar to avoid transferring it within 45 days of the previous expiration date, because of the possible loss of the expected additional registration year.

This 45-day warning concerns renewal accounting. It should not be confused with ICANN’s separate 60-day transfer restrictions.

Before transferring a recently expired or renewed domain, verify its expiration date, renewal history, registry rules, and both registrars’ terms.

For details, see How to Transfer a Domain Into NiceNIC.

How to Transfer Your Domain to NiceNIC

If you have checked your domain’s eligibility and are ready to change registrars, you can begin the process through NiceNIC.

For a supported extension using a standard Auth Code transfer:

1. Sign in to your existing registrar account.
2. Remove the applicable transfer lock.
3. Obtain your EPP/Auth Code.
4. Open the NiceNIC Domain Transfer page.
5. Enter the domain and required authorization code.
6. Review the current transfer price, terms, and applicable registration period.
7. Submit the order and complete any required authorization.
8. Monitor the transfer until it finishes.

How to Check Your Transfer Status at NiceNIC

After submitting your transfer, sign in to your NiceNIC account and go to:

My Products > Domain Names

NiceNIC’s published instructions explain that the Status column may display:

• Pending Transfer: The transfer is submitted and still being processed.
• Active / Transfer Completed: The transfer has finished.

For pending transfers, the information icon can provide the expected approval or completion date.

The precise timing depends on the registry and transfer conditions.

If your main concern is whether NiceNIC is the right registrar for your domain portfolio, see Transfer Your Domain to NiceNIC: A Practical Guide for Better Domain Control.

That guide discusses registrar selection, management capabilities, pricing considerations, and other practical reasons to move domains.

Frequently Asked Questions About Domain Transfers

How do I transfer a domain from one registrar to another?

For a typical gTLD, check eligibility, unlock the domain, obtain the authorization code, submit the transfer request with the gaining registrar, complete any required confirmation, and monitor the registry processing status.

Why is my domain transfer still pending after five days?

The five-calendar-day registry processing period may not have started when you first submitted your order. Check whether the request has reached the registry, whether authorization remains outstanding, and whether the domain has any active restrictions.

If the registry’s expected processing deadline has passed, contact the gaining registrar for the exact transfer status.

Can I transfer a domain before 60 days?

Under ICANN’s current policy, the losing registrar may deny a gTLD transfer during the first 60 days after initial registration or a previous inter-registrar transfer, subject to the applicable policy and limited exceptions.

A material Change of Registrant can also trigger a 60-day lock that the registrar is generally required to impose unless an available advance opt-out was selected.

Country-code domains may follow different rules.

Does transferring a domain change its ownership?

No. An inter-registrar transfer changes the registrar responsible for managing the domain registration.

A Change of Registrant changes the registered holder.

These are distinct operations, and changing ownership details can have separate authorization and transfer-lock consequences.

Can I transfer a domain without changing its nameservers?

Yes. In a normal registrar transfer, your existing nameservers can remain unchanged.

However, confirm that your DNS hosting provider will continue providing service after the transfer. This is especially important if your DNS is hosted by the registrar you are leaving.

What happens if a domain transfer fails?

The domain normally remains with its existing registrar if the transfer does not complete.

Identify the rejection reason, resolve the problem, and confirm whether you need to submit a new transfer request or obtain a fresh Auth Code.

Transfer fees and refund eligibility depend on the gaining registrar’s applicable terms.

Before You Transfer: Final Checklist

Most avoidable transfer problems come from overlooking a small number of details.

Before submitting your next domain transfer, confirm that:

• Your domain is eligible for transfer.
• No applicable transfer-prohibiting lock remains active.
• Your EPP/Auth Code or TLD-specific authorization information is correct.
• You can access any email or account required for verification.
• Your DNS hosting, website, and email will remain operational.
• You understand the transfer fee and any expiration-date implications.
• You have reviewed any special ccTLD registration or transfer requirements.

A registrar transfer is usually a manageable process when the domain is prepared correctly. The most important steps are checking eligibility, securing the right authorization, and understanding the status of the request.

If you are ready to move an eligible domain, check your transfer options and current pricing at NiceNIC.