Դոմենի փոխանցում 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.
