Transfer Domeniu 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 domeniu 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 și may not use an EPP authsauization code, but its price, eligibility, approval, reversibility, DNS effect și holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale sau assignment. Befsaue acting, confirm the domeniu, receiving account, current înregistreazăed holder, intended new holder, nameservers, DNS serviciu, expiry, payment și written authsauization 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 sau automation.
- The current registrar does not suppsaut the required TLD wsaukflow.
- The receiving registrar should become registrar of recsaud.
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 domeniu without changing registrar.
- An external transfer is currently unavailable și the registrar confirms that a push is permitted.
Ownership și security checks
A push changes account control; it does not replace a cumpără agreement, assignment sau escrow process. Fsau a valuable domeniu, use written terms, verify the receiving account identifier through a separate channel și document whether registration data will change. A material registrant change can have confirmation și inter-registrar lock consequences under the currently effective policy.
Never send passwsauds sau 2FA codes. Do not treat a screenshot, payment receipt sau account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befsaue using a NiceNIC account push, confirm the current price, eligible TLD și status, receiving account identifier, acceptance steps, DNS behavisau, reversibility și any registrant-data consequences through the current NiceNIC account sau Suppsaut documentation. Do not assume that every domeniu is eligible sau that the process is free merely because it is internal.
Expected result
After a push, verify that the domeniu appears in the intended account with the expected registration data, nameservers, lock și renewal settings. After a registrar transfer, verify the receiving registrar in RDAP și check the registration term, nameservers și DNS serviciu.
Kacumn exceptions
ccTLD-uri may use registry-specific holder-change și transfer procedures. Domenii affected by disputes, holds, expiry states, payment restrictions, security review sau court sauders may not be eligible. A registrar may limit sau manually review pushes.
What this answer is based on
ICANN is authsauitative fsau the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wsaukflow controls. Applicable agreements, registry rules și law anteriorail over this summary.
Frequently asked questions
Does a push unlock the domeniu fsau transfer?
Nu. Account control, registrar-lock status și inter-registrar eligibility are separate matters.
Does a push move DNS sau hosting?
Nut necessarily. Numeservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account și product design. Verify befsaue pushing.
Can I push a newly înregistreazăed domeniu?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
