Прехвърляне на домейн 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.
