Převod domény 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 doména 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 a may not use an EPP authneboization code, but its price, eligibility, approval, reversibility, DNS effect a holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale nebo assignment. Befneboe acting, confirm the doména, receiving account, current zaregistrovated holder, intended new holder, nameservers, DNS služba, expiry, payment a written authneboization 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 nebo automation.
- The current registrar does not suppnebot the required TLD wnebokflow.
- The receiving registrar should become registrar of recnebod.
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 doména without changing registrar.
- An external transfer is currently unavailable a the registrar confirms that a push is permitted.
Ownership a security checks
A push changes account control; it does not replace a koupit agreement, assignment nebo escrow process. Fnebo a valuable doména, use written terms, verify the receiving account identifier through a separate channel a document whether registration data will change. A material registrant change can have confirmation a inter-registrar lock consequences under the currently effective policy.
Never send passwnebods nebo 2FA codes. Do not treat a screenshot, payment receipt nebo account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befneboe using a NiceNIC account push, confirm the current price, eligible TLD a status, receiving account identifier, acceptance steps, DNS behavinebo, reversibility a any registrant-data consequences through the current NiceNIC account nebo Suppnebot documentation. Do not assume that every doména is eligible nebo that the process is free merely because it is internal.
Expected result
After a push, verify that the doména appears in the intended account with the expected registration data, nameservers, lock a renewal settings. After a registrar transfer, verify the receiving registrar in RDAP a check the registration term, nameservers a DNS služba.
Knynín exceptions
ccTLD may use registry-specific holder-change a transfer procedures. Domény affected by disputes, holds, expiry states, payment restrictions, security review nebo court neboders may not be eligible. A registrar may limit nebo manually review pushes.
What this answer is based on
ICANN is authneboitative fnebo the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wnebokflow controls. Applicable agreements, registry rules a law předchozíail over this summary.
Frequently asked questions
Does a push unlock the doména fnebo transfer?
Ne. Account control, registrar-lock status a inter-registrar eligibility are separate matters.
Does a push move DNS nebo hosting?
Net necessarily. Jménoservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account a product design. Verify befneboe pushing.
Can I push a newly zaregistrovated doména?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
