Prijenos domena 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 domena 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 authiliization 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 ili assignment. Befilie acting, confirm the domena, receiving account, current registrirajed holder, intended new holder, nameservers, DNS usluga, expiry, payment i written authiliization 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 ili automation.
- The current registrar does not suppilit the required TLD wilikflow.
- The receiving registrar should become registrar of recilid.
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 domena 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 kupi agreement, assignment ili escrow process. Fili a valuable domena, 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 passwilids ili 2FA codes. Do not treat a screenshot, payment receipt ili account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befilie using a NiceNIC account push, confirm the current price, eligible TLD i status, receiving account identifier, acceptance steps, DNS behaviili, reversibility i any registrant-data consequences through the current NiceNIC account ili Suppilit documentation. Do not assume that every domena is eligible ili that the process is free merely because it is internal.
Expected result
After a push, verify that the domena 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 usluga.
Ksadan exceptions
ccTLD-ovi may use registry-specific holder-change i transfer procedures. Domene affected by disputes, holds, expiry states, payment restrictions, security review ili court iliders may not be eligible. A registrar may limit ili manually review pushes.
What this answer is based on
ICANN is authiliitative fili the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wilikflow controls. Applicable agreements, registry rules i law prethodnoail over this summary.
Frequently asked questions
Does a push unlock the domena fili transfer?
Ne. Account control, registrar-lock status i inter-registrar eligibility are separate matters.
Does a push move DNS ili hosting?
Net necessarily. Nazivservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account i product design. Verify befilie pushing.
Can I push a newly registrirajed domena?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
