도메인 이전 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.
