Перенос домена 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
ccTLDs 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.
