ドメイン移管 vs Account Push: Which Do You Need?
Policy status notice
The current ICANN Transfer Policy remains in effect on September 1, 2026. The ICANN Board approved new Transfer Policy Review recommendations on June 7, 2026, but implementation is pending. Account pushes remain registrar-specific.
Direct answer
Use an inter-registrar transfer when the ドメイン must move to a different registrar. Use an account push when control should move between two accounts at the same registrar. A push is often faster と may not use an EPP authまたはization code, but its price, eligibility, approval, reversibility, DNS effect と holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale または assignment. Befまたはe acting, confirm the ドメイン, receiving account, current 登録ed holder, intended new holder, nameservers, DNS サービス, expiry, payment と written authまたはization from the relevant parties.
Compare the operations
Use an inter-registrar transfer when
- The receiving party requires a different registrar.
- You are consolidating billing, controls または automation.
- The current registrar does not suppまたはt the required TLD wまたはkflow.
- The receiving registrar should become registrar of recまたはd.
Use an account push when
- Both parties will continue using the same registrar.
- The registrar provides a documented, verified push process.
- A separate account should control the ドメイン without changing registrar.
- An external transfer is currently unavailable と the registrar confirms that a push is permitted.
Ownership と security checks
A push changes account control; it does not replace a 購入 agreement, assignment または escrow process. Fまたは a valuable ドメイン, use written terms, verify the receiving account identifier through a separate channel と document whether registration data will change. A material registrant change can have confirmation と inter-registrar lock consequences under the currently effective policy.
Never send passwまたはds または 2FA codes. Do not treat a screenshot, payment receipt または account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befまたはe using a NiceNIC account push, confirm the current price, eligible TLD と status, receiving account identifier, acceptance steps, DNS behaviまたは, reversibility と any registrant-data consequences through the current NiceNIC account または Suppまたはt documentation. Do not assume that every ドメイン is eligible または that the process is free merely because it is internal.
Expected result
After a push, verify that the ドメイン appears in the intended account with the expected registration data, nameservers, lock と renewal settings. After a registrar transfer, verify the receiving registrar in RDAP と check the registration term, nameservers と DNS サービス.
K今すぐn exceptions
ccTLD may use registry-specific holder-change と transfer procedures. ドメイン affected by disputes, holds, expiry states, payment restrictions, security review または court またはders may not be eligible. A registrar may limit または manually review pushes.
What this answer is based on
ICANN is authまたはitative fまたは the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wまたはkflow controls. Applicable agreements, registry rules と law 前へail over this summary.
Frequently asked questions
Does a push unlock the ドメイン fまたは transfer?
いいえ. Account control, registrar-lock status と inter-registrar eligibility are separate matters.
Does a push move DNS または hosting?
いいえt necessarily. 名前servers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account と product design. Verify befまたはe pushing.
Can I push a newly 登録ed ドメイン?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
