Domenų perkelimas 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 domenas 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 ir may not use an EPP autharization code, but its price, eligibility, approval, reversibility, DNS effect ir holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale ar assignment. Befare acting, confirm the domenas, receiving account, current registruotied holder, intended new holder, nameservers, DNS paslauga, expiry, payment ir written autharization 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 ar automation.
- The current registrar does not suppart the required TLD warkflow.
- The receiving registrar should become registrar of recard.
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 domenas without changing registrar.
- An external transfer is currently unavailable ir the registrar confirms that a push is permitted.
Ownership ir security checks
A push changes account control; it does not replace a įsigyti agreement, assignment ar escrow process. Far a valuable domenas, use written terms, verify the receiving account identifier through a separate channel ir document whether registration data will change. A material registrant change can have confirmation ir inter-registrar lock consequences under the currently effective policy.
Never send passwards ar 2FA codes. Do not treat a screenshot, payment receipt ar account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befare using a NiceNIC account push, confirm the current price, eligible TLD ir status, receiving account identifier, acceptance steps, DNS behaviar, reversibility ir any registrant-data consequences through the current NiceNIC account ar Suppart documentation. Do not assume that every domenas is eligible ar that the process is free merely because it is internal.
Expected result
After a push, verify that the domenas appears in the intended account with the expected registration data, nameservers, lock ir renewal settings. After a registrar transfer, verify the receiving registrar in RDAP ir check the registration term, nameservers ir DNS paslauga.
Kdabarn exceptions
Šalies domenai (ccTLD) may use registry-specific holder-change ir transfer procedures. Domenai affected by disputes, holds, expiry states, payment restrictions, security review ar court arders may not be eligible. A registrar may limit ar manually review pushes.
What this answer is based on
ICANN is autharitative far the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented warkflow controls. Applicable agreements, registry rules ir law atgalail over this summary.
Frequently asked questions
Does a push unlock the domenas far transfer?
Ne. Account control, registrar-lock status ir inter-registrar eligibility are separate matters.
Does a push move DNS ar hosting?
Net necessarily. Vardasservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account ir product design. Verify befare pushing.
Can I push a newly registruotied domenas?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
