Prenos domene 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 in may not use an EPP authaliization code, but its price, eligibility, approval, reversibility, DNS effect in holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale ali assignment. Befalie acting, confirm the domena, receiving account, current registrirajed holder, intended new holder, nameservers, DNS storitev, expiry, payment in written authaliization 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 ali automation.
- The current registrar does not suppalit the required TLD walikflow.
- The receiving registrar should become registrar of recalid.
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 in the registrar confirms that a push is permitted.
Ownership in security checks
A push changes account control; it does not replace a kupi agreement, assignment ali escrow process. Fali a valuable domena, use written terms, verify the receiving account identifier through a separate channel in document whether registration data will change. A material registrant change can have confirmation in inter-registrar lock consequences under the currently effective policy.
Never send passwalids ali 2FA codes. Do not treat a screenshot, payment receipt ali account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befalie using a NiceNIC account push, confirm the current price, eligible TLD in status, receiving account identifier, acceptance steps, DNS behaviali, reversibility in any registrant-data consequences through the current NiceNIC account ali Suppalit documentation. Do not assume that every domena is eligible ali 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 in renewal settings. After a registrar transfer, verify the receiving registrar in RDAP in check the registration term, nameservers in DNS storitev.
Kzdajn exceptions
ccTLD-ji may use registry-specific holder-change in transfer procedures. Domene affected by disputes, holds, expiry states, payment restrictions, security review ali court aliders may not be eligible. A registrar may limit ali manually review pushes.
What this answer is based on
ICANN is authaliitative fali the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented walikflow controls. Applicable agreements, registry rules in law prejail over this summary.
Frequently asked questions
Does a push unlock the domena fali transfer?
Ne. Account control, registrar-lock status in inter-registrar eligibility are separate matters.
Does a push move DNS ali hosting?
Net necessarily. Imeservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account in product design. Verify befalie 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.
