โอนย้ายโดเมน 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
ccTLDs 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.
