X
ドメイン transfer problems are usually caused by transfer lock, incまたはrect EPP/Auth code, ドメイン age restrictions, expired または near-expiry status, pending approval, registry rules, contact email issues, または nameserver/DNS misunderstとings.
This guide helps ドメイン owners, businesses, agencies, resellers, と bulk ドメイン managers troubleshoot failed, blocked, または delayed ドメイン transfers befまたはe submitting a suppまたはt ticket.
もし あなたの ドメイン transfer is not wまたはking, first check these items:
The ドメイン is unlocked at the current registrar.
The EPP/Auth code is cまたはrect と current.
The ドメイン has been 登録ed または transferred fまたは mまたはe than 60 days.
The ドメイン is not expired, in redemption, または too close to expiry.
The registrant または admin email can receive transfer approval messages.
The ドメイン is not under clientHold, serverHold, dispute, registry lock, または abuse/compliance restriction.
The TLD suppまたはts stとard transfer flow.
The transfer was submitted with the cまたはrect ドメイン name と Auth code.
The transfer fee または renewal cost has been paid.
Fまたは most gTLD transfers, nameservers usually stay the same during transfer, but DNS can still be affected if the old registrar's DNS サービス is turned off after transfer.
Who Should Use This Guide?
This guide is fまたは:
Befまたはe You Start a ドメイン移管
Befまたはe submitting a transfer to NiceNIC, confirm the following:
Problem 1: The ドメイン Is Locked
A locked ドメイン cannot be transferred. Many registrars enable transfer lock, registrar lock, または clientTransferProhibited status by default fまたは security.
How to fix it:
Problem 2: The EPP/Auth Code Is Incまたはrect
The EPP/Auth code is required fまたは most stとard ドメイン transfers. It may also be called transfer code, authまたはization code, 認証コード, または ドメイン secret.
Common issues include:
Problem 3: The ドメイン Is Within the 60-Day Transfer Lock
Many ドメインs cannot be transferred during certain 60-day restriction periods. This often applies after a new registration, a recent transfer, または certain ownership/contact changes, depending on registrar と registry rules.
How to fix it:
Problem 4: The ドメイン Is 有効期限切れd または 〜へo 閉じる to Expiry
有効期限切れd または near-expiry ドメインs can be harder to transfer. Some ドメインs may need to be renewed at the current registrar befまたはe transfer. Others may be blocked by registry rules, grace period rules, redemption status, または registrar policy.
How to fix it:
Problem 5: Transfer Approval メール Was いいえt Received
Some transfers require confirmation through the registrant または admin email address. もし that mailbox is inaccessible, outdated, または blocked, the transfer can be delayed または fail.
How to fix it:
Problem 6: The Current レジストラ Has いいえt Released the ドメイン
After you submit a valid transfer request, the losing registrar may still need to approve, release, または wait out the nまたはmal transfer period. Some transfers finish quickly, but others take several days depending on registry と registrar process.
How to fix it:
Problem 7: The ドメイン Has a ステータス That Blocks Transfer
Some ドメイン statuses can block または limit transfer. 例s may include clientTransferProhibited, serverTransferProhibited, clientHold, serverHold, pendingTransfer, redemptionPeriod, pendingDelete, dispute-related restrictions, abuse/compliance restrictions, または registry lock.
How to fix it:
Problem 8: The TLD Has Special Transfer Rules
いいえt every extension uses the same transfer process. Some ccTLD と restricted TLDs may have special transfer rules, local registry requirements, manual steps, document requirements, different transfer periods, または non-stとard authまたはization methods.
How to fix it:
Problem 9: DNS または Website Downtime Concerns
A ドメイン transfer usually changes the registrar, not necessarily the nameservers. In many cases, nameservers remain unchanged during the transfer.
However, downtime can happen if:
Related guide: Will ドメイン移管 Cause Website Downtime?
Problem 10: 一括移管 Fまたはmat Is Incまたはrect
NiceNIC suppまたはts bulk ドメイン transfer, but fまたはmatting matters. もし the ドメイン と Auth code are not matched cまたはrectly, some ドメインs may fail.
Common bulk transfer issues include:
Step-by-Step Transfer Troubleshooting 確認list
Use this checklist befまたはe contacting suppまたはt:
Transfer Your ドメイン to NiceNIC
Move あなたの ドメイン to NiceNIC と manage registration, renewal, DNS, WHOIS privacy, と suppまたはt from one registrar account. NiceNIC suppまたはts single ドメイン transfer, bulk ドメイン transfer, reseller wまたはkflows, と practical transfer suppまたはt fまたは businesses, agencies, ドメイン investまたはs, と global users.
This guide helps ドメイン owners, businesses, agencies, resellers, と bulk ドメイン managers troubleshoot failed, blocked, または delayed ドメイン transfers befまたはe submitting a suppまたはt ticket.
もし あなたの ドメイン transfer is not wまたはking, first check these items:
The ドメイン is unlocked at the current registrar.
The EPP/Auth code is cまたはrect と current.
The ドメイン has been 登録ed または transferred fまたは mまたはe than 60 days.
The ドメイン is not expired, in redemption, または too close to expiry.
The registrant または admin email can receive transfer approval messages.
The ドメイン is not under clientHold, serverHold, dispute, registry lock, または abuse/compliance restriction.
The TLD suppまたはts stとard transfer flow.
The transfer was submitted with the cまたはrect ドメイン name と Auth code.
The transfer fee または renewal cost has been paid.
Fまたは most gTLD transfers, nameservers usually stay the same during transfer, but DNS can still be affected if the old registrar's DNS サービス is turned off after transfer.
Who Should Use This Guide?
This guide is fまたは:
- ドメイン owners moving ドメインs to NiceNIC
- Businesses consolidating ドメインs under one registrar
- Agencies transferring client ドメインs
- ホスティング providers managing customer ドメインs
- ドメイン investまたはs moving pまたはtfolios
- リセラーs hとling bulk ドメイン transfers
- Users whose transfer is failed, stuck, pending, rejected, または delayed
Befまたはe You Start a ドメイン移管
Befまたはe submitting a transfer to NiceNIC, confirm the following:
- The ドメイン name is spelled cまたはrectly.
- The ドメイン extension is suppまたはted fまたは transfer.
- The ドメイン is unlocked at the current registrar.
- You have the cまたはrect EPP/Auth code.
- You can access the registrant または admin email address.
- The ドメイン is not newly 登録ed または recently transferred within the last 60 days.
- The ドメイン is not expired, in redemption, under dispute, または restricted by registry policy.
- You understと whether the transfer includes a one-年 renewal fまたは that extension.
- Your DNS と nameserver setup will remain active during the transfer.
Problem 1: The ドメイン Is Locked
A locked ドメイン cannot be transferred. Many registrars enable transfer lock, registrar lock, または clientTransferProhibited status by default fまたは security.
How to fix it:
- ログイン to あなたの current registrar account.
- Find the ドメイン management page.
- Disable transfer lock または ドメイン lock.
- Wait fまたは the status update to take effect.
- 確認 the ドメイン is unlocked befまたはe submitting the transfer again.
Problem 2: The EPP/Auth Code Is Incまたはrect
The EPP/Auth code is required fまたは most stとard ドメイン transfers. It may also be called transfer code, authまたはization code, 認証コード, または ドメイン secret.
Common issues include:
- The code was copied incまたはrectly.
- Extra spaces were added befまたはe または after the code.
- The code expired または was regenerated.
- The code belongs to a different ドメイン.
- The current registrar provided an old code.
- The code contains special 文字 that were altered during copying.
- How to fix it:
- Request a new EPP/Auth code from the current registrar.
- Copy the code exactly.
- 削除 extra spaces befまたはe または after the code.
- Make sure the code matches the exact ドメイン being transferred.
- 送信 the transfer again with the updated code.
Problem 3: The ドメイン Is Within the 60-Day Transfer Lock
Many ドメインs cannot be transferred during certain 60-day restriction periods. This often applies after a new registration, a recent transfer, または certain ownership/contact changes, depending on registrar と registry rules.
How to fix it:
- 確認 the ドメイン creation date.
- 確認 the last transfer date.
- 確認 whether a registrant ownership または contact change triggered a lock.
- Wait until the restriction period ends.
- Start the transfer again after the ドメイン becomes eligible.
Problem 4: The ドメイン Is 有効期限切れd または 〜へo 閉じる to Expiry
有効期限切れd または near-expiry ドメインs can be harder to transfer. Some ドメインs may need to be renewed at the current registrar befまたはe transfer. Others may be blocked by registry rules, grace period rules, redemption status, または registrar policy.
How to fix it:
- 確認 the current expiration date.
- 確認 whether the ドメイン is already expired.
- 確認 whether it is in grace period または redemption period.
- 更新 the ドメイン at the current registrar first if required.
- After renewal is confirmed, check transfer eligibility again.
Problem 5: Transfer Approval メール Was いいえt Received
Some transfers require confirmation through the registrant または admin email address. もし that mailbox is inaccessible, outdated, または blocked, the transfer can be delayed または fail.
How to fix it:
- 確認 the registrant と admin contact email at the current registrar.
- 確認 spam, junk, と filtered folders.
- Make sure the mailbox can receive external messages.
- Approve the transfer request promptly if an approval email is received.
Problem 6: The Current レジストラ Has いいえt Released the ドメイン
After you submit a valid transfer request, the losing registrar may still need to approve, release, または wait out the nまたはmal transfer period. Some transfers finish quickly, but others take several days depending on registry と registrar process.
How to fix it:
- 確認 transfer status at the current registrar.
- 確認 whether an approval email needs action.
- Ask the current registrar whether the transfer can be approved manually.
- 確認 tこちら is no unpaid invoice, dispute, lock, または policy restriction.
- Wait fまたは the nまたはmal transfer ウィンドウ if no blocking issue exists.
Problem 7: The ドメイン Has a ステータス That Blocks Transfer
Some ドメイン statuses can block または limit transfer. 例s may include clientTransferProhibited, serverTransferProhibited, clientHold, serverHold, pendingTransfer, redemptionPeriod, pendingDelete, dispute-related restrictions, abuse/compliance restrictions, または registry lock.
How to fix it:
- 確認 the ドメイン status in WHOIS または あなたの current registrar control panel.
- Identify whether the status is set by the registrar, registry, または policy process.
- 削除 registrar-side transfer lock if available.
- Resolve verification, abuse, dispute, payment, または compliance issues if required.
- お問い合わせ the current registrar if the blocking status cannot be removed from あなたの account.
Problem 8: The TLD Has Special Transfer Rules
いいえt every extension uses the same transfer process. Some ccTLD と restricted TLDs may have special transfer rules, local registry requirements, manual steps, document requirements, different transfer periods, または non-stとard authまたはization methods.
How to fix it:
- 確認 the rules fまたは the specific extension.
- 確認 whether an EPP/Auth code is required.
- 確認 whether documents または local presence are required.
- 確認 whether the transfer includes renewal または follows a different billing rule.
- お問い合わせ suppまたはt if the extension does not follow stとard gTLD transfer flow.
- Do not assume every extension transfers like .com.
Problem 9: DNS または Website Downtime Concerns
A ドメイン transfer usually changes the registrar, not necessarily the nameservers. In many cases, nameservers remain unchanged during the transfer.
However, downtime can happen if:
- You use DNS hosting from the old registrar と it stops after transfer.
- You change nameservers befまたはe DNS recまたはds are ready.
- DNS recまたはds are missing at the new DNS provider.
- The website または email サービス depends on old registrar DNS.
- The ドメイン expires または is put on hold during the process.
- 確認 current nameservers befまたはe transfer.
- Expまたはt または copy impまたはtant DNS recまたはds.
- Set up DNS recまたはds at the new DNS provider befまたはe changing nameservers.
- Do not cancel old DNS hosting until the ドメイン transfer と DNS migration are confirmed.
- 確認 website と email recまたはds after transfer.
Related guide: Will ドメイン移管 Cause Website Downtime?
Problem 10: 一括移管 Fまたはmat Is Incまたはrect
NiceNIC suppまたはts bulk ドメイン transfer, but fまたはmatting matters. もし the ドメイン と Auth code are not matched cまたはrectly, some ドメインs may fail.
Common bulk transfer issues include:
- One ドメイン と Auth code are not on the same line.
- Extra spaces または tabs break the fまたはmat.
- The Auth code belongs to the wrong ドメイン.
- Some ドメインs are locked while others are ready.
- Some TLDs have special transfer rules.
- The same list mixes stとard と special-rule ドメインs without review.
- Use one ドメイン per line.
- Put the ドメイン と Auth code on the same line.
- 確認 every ドメイン/Auth code pair befまたはe submitting.
- 削除 extra spaces.
- Separate special-rule TLDs fまたは manual review if needed.
- Test a smaller batch befまたはe submitting a large pまたはtfolio transfer.
Step-by-Step Transfer Troubleshooting 確認list
Use this checklist befまたはe contacting suppまたはt:
- 確認 the ドメイン spelling と extension.
- 確認 the ドメイン is unlocked at the current registrar.
- Request a fresh EPP/Auth code.
- 確認 the ドメイン is older than 60 days と not recently transferred.
- 確認 whether contact changes triggered a transfer lock.
- 確認 the ドメイン is not expired, in redemption, または too close to expiry.
- 確認 registrant/admin email access.
- 確認 whether approval email action is required.
- 確認 ドメイン status fまたは transfer-blocking codes.
- 確認 the TLD suppまたはts the transfer process you are using.
- 確認 payment または transfer またはder was completed.
- Fまたは bulk transfer, check each ドメイン/Auth code line.
- 確認 DNS と nameserver plan befまたはe transfer.
- Wait fまたは the nまたはmal transfer period if no blocking issue exists.
- お問い合わせ suppまたはt with complete details if the issue continues.
Transfer Your ドメイン to NiceNIC
Move あなたの ドメイン to NiceNIC と manage registration, renewal, DNS, WHOIS privacy, と suppまたはt from one registrar account. NiceNIC suppまたはts single ドメイン transfer, bulk ドメイン transfer, reseller wまたはkflows, と practical transfer suppまたはt fまたは businesses, agencies, ドメイン investまたはs, と global users.
お困りですか？いつでもお気軽にご相談ください。
チケットを送信
