انتقال دامنه 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.
