نقل النطاق 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
نطاقات المستوى الأعلى الخاصة بالدولة 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.
