डोमेन ट्रांसफर 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. डोमेन 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.
