Domeeni ülekandmine 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 domeen 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 ja may not use an EPP authvõiization code, but its price, eligibility, approval, reversibility, DNS effect ja holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale või assignment. Befvõie acting, confirm the domeen, receiving account, current registreeried holder, intended new holder, nameservers, DNS teenus, expiry, payment ja written authvõiization 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õi automation.
- The current registrar does not suppvõit the required TLD wvõikflow.
- The receiving registrar should become registrar of recvõid.
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 domeen without changing registrar.
- An external transfer is currently unavailable ja the registrar confirms that a push is permitted.
Ownership ja security checks
A push changes account control; it does not replace a osta agreement, assignment või escrow process. Fvõi a valuable domeen, use written terms, verify the receiving account identifier through a separate channel ja document whether registration data will change. A material registrant change can have confirmation ja inter-registrar lock consequences under the currently effective policy.
Never send passwvõids või 2FA codes. Do not treat a screenshot, payment receipt või account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befvõie using a NiceNIC account push, confirm the current price, eligible TLD ja status, receiving account identifier, acceptance steps, DNS behavivõi, reversibility ja any registrant-data consequences through the current NiceNIC account või Suppvõit documentation. Do not assume that every domeen is eligible või that the process is free merely because it is internal.
Expected result
After a push, verify that the domeen appears in the intended account with the expected registration data, nameservers, lock ja renewal settings. After a registrar transfer, verify the receiving registrar in RDAP ja check the registration term, nameservers ja DNS teenus.
Kkohen exceptions
Riiklikud ccTLDd may use registry-specific holder-change ja transfer procedures. Domeenid affected by disputes, holds, expiry states, payment restrictions, security review või court võiders may not be eligible. A registrar may limit või manually review pushes.
What this answer is based on
ICANN is authvõiitative fvõi the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wvõikflow controls. Applicable agreements, registry rules ja law eelmineail over this summary.
Frequently asked questions
Does a push unlock the domeen fvõi transfer?
Ei. Account control, registrar-lock status ja inter-registrar eligibility are separate matters.
Does a push move DNS või hosting?
Eit necessarily. Nimiservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account ja product design. Verify befvõie pushing.
Can I push a newly registreeried domeen?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
