დომენის გადმოტანა 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.
