העברת דומיין 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.
