Domen Transferi 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 domen 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 authvə yaization 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 və ya assignment. Befvə yae acting, confirm the domen, receiving account, current qeydiyyated holder, intended new holder, nameservers, DNS Xidmət, expiry, payment və written authvə yaization 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 və ya automation.
- The current registrar does not suppvə yat the required TLD wvə yakflow.
- The receiving registrar should become registrar of recvə yad.
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 domen 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 al agreement, assignment və ya escrow process. Fvə ya a valuable domen, 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 passwvə yads və ya 2FA codes. Do not treat a screenshot, payment receipt və ya account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befvə yae using a NiceNIC account push, confirm the current price, eligible TLD və status, receiving account identifier, acceptance steps, DNS behavivə ya, reversibility və any registrant-data consequences through the current NiceNIC account və ya Suppvə yat documentation. Do not assume that every domen is eligible və ya that the process is free merely because it is internal.
Expected result
After a push, verify that the domen 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 Xidmət.
Kindin exceptions
ccTLD-lər may use registry-specific holder-change və transfer procedures. Domenlər affected by disputes, holds, expiry states, payment restrictions, security review və ya court və yaders may not be eligible. A registrar may limit və ya manually review pushes.
What this answer is based on
ICANN is authvə yaitative fvə ya the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wvə yakflow controls. Applicable agreements, registry rules və law geriail over this summary.
Frequently asked questions
Does a push unlock the domen fvə ya transfer?
Xeyr. Account control, registrar-lock status və inter-registrar eligibility are separate matters.
Does a push move DNS və ya hosting?
Xeyrt necessarily. Adservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account və product design. Verify befvə yae pushing.
Can I push a newly qeydiyyated domen?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
