Доменді ауыстыру 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 домен 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 және may not use an EPP authнемесеization code, but its price, eligibility, approval, reversibility, DNS effect және holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale немесе assignment. Befнемесеe acting, confirm the домен, receiving account, current тіркеуed holder, intended new holder, nameservers, DNS қызмет, expiry, payment және written authнемесеization 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 немесе automation.
- The current registrar does not suppнемесеt the required TLD wнемесеkflow.
- The receiving registrar should become registrar of recнемесеd.
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 домен without changing registrar.
- An external transfer is currently unavailable және the registrar confirms that a push is permitted.
Ownership және security checks
A push changes account control; it does not replace a сатып алу agreement, assignment немесе escrow process. Fнемесе a valuable домен, use written terms, verify the receiving account identifier through a separate channel және document whether registration data will change. A material registrant change can have confirmation және inter-registrar lock consequences under the currently effective policy.
Never send passwнемесеds немесе 2FA codes. Do not treat a screenshot, payment receipt немесе account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befнемесеe using a NiceNIC account push, confirm the current price, eligible TLD және status, receiving account identifier, acceptance steps, DNS behaviнемесе, reversibility және any registrant-data consequences through the current NiceNIC account немесе Suppнемесеt documentation. Do not assume that every домен is eligible немесе that the process is free merely because it is internal.
Expected result
After a push, verify that the домен appears in the intended account with the expected registration data, nameservers, lock және renewal settings. After a registrar transfer, verify the receiving registrar in RDAP және check the registration term, nameservers және DNS қызмет.
Kқазірn exceptions
ccTLD-тер may use registry-specific holder-change және transfer procedures. Домендер affected by disputes, holds, expiry states, payment restrictions, security review немесе court немесеders may not be eligible. A registrar may limit немесе manually review pushes.
What this answer is based on
ICANN is authнемесеitative fнемесе the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wнемесеkflow controls. Applicable agreements, registry rules және law артқаail over this summary.
Frequently asked questions
Does a push unlock the домен fнемесе transfer?
Жоқ. Account control, registrar-lock status және inter-registrar eligibility are separate matters.
Does a push move DNS немесе hosting?
Жоқt necessarily. Атыservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account және product design. Verify befнемесеe pushing.
Can I push a newly тіркеуed домен?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
