Domain 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 domain 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 ve may not use an EPP authveyaization code, but its price, eligibility, approval, reversibility, DNS effect ve holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale veya assignment. Befveyae acting, confirm the domain, receiving account, current kayıt oled holder, intended new holder, nameservers, DNS hizmet, expiry, payment ve written authveyaization 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 veya automation.
- The current registrar does not suppveyat the required TLD wveyakflow.
- The receiving registrar should become registrar of recveyad.
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 domain without changing registrar.
- An external transfer is currently unavailable ve the registrar confirms that a push is permitted.
Ownership ve security checks
A push changes account control; it does not replace a satın al agreement, assignment veya escrow process. Fveya a valuable domain, use written terms, verify the receiving account identifier through a separate channel ve document whether registration data will change. A material registrant change can have confirmation ve inter-registrar lock consequences under the currently effective policy.
Never send passwveyads veya 2FA codes. Do not treat a screenshot, payment receipt veya account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befveyae using a NiceNIC account push, confirm the current price, eligible TLD ve status, receiving account identifier, acceptance steps, DNS behaviveya, reversibility ve any registrant-data consequences through the current NiceNIC account veya Suppveyat documentation. Do not assume that every domain is eligible veya that the process is free merely because it is internal.
Expected result
After a push, verify that the domain appears in the intended account with the expected registration data, nameservers, lock ve renewal settings. After a registrar transfer, verify the receiving registrar in RDAP ve check the registration term, nameservers ve DNS hizmet.
Kşimdin exceptions
ccTLD'ler may use registry-specific holder-change ve transfer procedures. Alan Adları affected by disputes, holds, expiry states, payment restrictions, security review veya court veyaders may not be eligible. A registrar may limit veya manually review pushes.
What this answer is based on
ICANN is authveyaitative fveya the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wveyakflow controls. Applicable agreements, registry rules ve law öncekiail over this summary.
Frequently asked questions
Does a push unlock the domain fveya transfer?
Hayır. Account control, registrar-lock status ve inter-registrar eligibility are separate matters.
Does a push move DNS veya hosting?
Hayırt necessarily. Adservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account ve product design. Verify befveyae pushing.
Can I push a newly kayıt oled domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
