Domenlarni ko'chirish 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 va may not use an EPP authyokiization code, but its price, eligibility, approval, reversibility, DNS effect va holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale yoki assignment. Befyokie acting, confirm the domain, receiving account, current roʻyxatdan oʻtkazished holder, intended new holder, nameservers, DNS Xizmat, expiry, payment va written authyokiization 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 yoki automation.
- The current registrar does not suppyokit the required TLD wyokikflow.
- The receiving registrar should become registrar of recyokid.
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 va the registrar confirms that a push is permitted.
Ownership va security checks
A push changes account control; it does not replace a sotib olish agreement, assignment yoki escrow process. Fyoki a valuable domain, use written terms, verify the receiving account identifier through a separate channel va document whether registration data will change. A material registrant change can have confirmation va inter-registrar lock consequences under the currently effective policy.
Never send passwyokids yoki 2FA codes. Do not treat a screenshot, payment receipt yoki account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befyokie using a NiceNIC account push, confirm the current price, eligible TLD va status, receiving account identifier, acceptance steps, DNS behaviyoki, reversibility va any registrant-data consequences through the current NiceNIC account yoki Suppyokit documentation. Do not assume that every domain is eligible yoki 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 va renewal settings. After a registrar transfer, verify the receiving registrar in RDAP va check the registration term, nameservers va DNS Xizmat.
Khozirn exceptions
ccTLDlar may use registry-specific holder-change va transfer procedures. Domenlar affected by disputes, holds, expiry states, payment restrictions, security review yoki court yokiders may not be eligible. A registrar may limit yoki manually review pushes.
What this answer is based on
ICANN is authyokiitative fyoki the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wyokikflow controls. Applicable agreements, registry rules va law oldingiail over this summary.
Frequently asked questions
Does a push unlock the domain fyoki transfer?
Yo‘q. Account control, registrar-lock status va inter-registrar eligibility are separate matters.
Does a push move DNS yoki hosting?
Yo‘qt necessarily. Ismservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account va product design. Verify befyokie pushing.
Can I push a newly roʻyxatdan oʻtkazished domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
