Chuyển nhượng tên miền 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 tên miền 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 và may not use an EPP authhoặcization code, but its price, eligibility, approval, reversibility, DNS effect và holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale hoặc assignment. Befhoặce acting, confirm the tên miền, receiving account, current đăng kýed holder, intended new holder, nameservers, DNS Dịch vụ, expiry, payment và written authhoặcization 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 hoặc automation.
- The current registrar does not supphoặct the required TLD whoặckflow.
- The receiving registrar should become registrar of rechoặcd.
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 tên miền without changing registrar.
- An external transfer is currently unavailable và the registrar confirms that a push is permitted.
Ownership và security checks
A push changes account control; it does not replace a mua agreement, assignment hoặc escrow process. Fhoặc a valuable tên miền, use written terms, verify the receiving account identifier through a separate channel và document whether registration data will change. A material registrant change can have confirmation và inter-registrar lock consequences under the currently effective policy.
Never send passwhoặcds hoặc 2FA codes. Do not treat a screenshot, payment receipt hoặc account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befhoặce using a NiceNIC account push, confirm the current price, eligible TLD và status, receiving account identifier, acceptance steps, DNS behavihoặc, reversibility và any registrant-data consequences through the current NiceNIC account hoặc Supphoặct documentation. Do not assume that every tên miền is eligible hoặc that the process is free merely because it is internal.
Expected result
After a push, verify that the tên miền appears in the intended account with the expected registration data, nameservers, lock và renewal settings. After a registrar transfer, verify the receiving registrar in RDAP và check the registration term, nameservers và DNS Dịch vụ.
Kngayn exceptions
ccTLD may use registry-specific holder-change và transfer procedures. Tên miền affected by disputes, holds, expiry states, payment restrictions, security review hoặc court hoặcders may not be eligible. A registrar may limit hoặc manually review pushes.
What this answer is based on
ICANN is authhoặcitative fhoặc the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented whoặckflow controls. Applicable agreements, registry rules và law trướcail over this summary.
Frequently asked questions
Does a push unlock the tên miền fhoặc transfer?
Không. Account control, registrar-lock status và inter-registrar eligibility are separate matters.
Does a push move DNS hoặc hosting?
Khôngt necessarily. Tênservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account và product design. Verify befhoặce pushing.
Can I push a newly đăng kýed tên miền?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
