Μεταφορά Domain 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
ccTLDs may use registry-specific holder-change και transfer procedures. Domains 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.
