Domain-Transfer 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 Domain 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 und may not use an EPP authoderization code, but its price, eligibility, approval, reversibility, DNS effect und holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale oder assignment. Befodere acting, confirm the Domain, receiving account, current registrierened holder, intended new holder, nameservers, DNS Dienstleistung, expiry, payment und written authoderization 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 oder automation.
- The current registrar does not suppodert the required TLD woderkflow.
- The receiving registrar should become registrar of recoderd.
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 Domain without changing registrar.
- An external transfer is currently unavailable und the registrar confirms that a push is permitted.
Ownership und security checks
A push changes account control; it does not replace a Kauf agreement, assignment oder escrow process. Foder a valuable Domain, use written terms, verify the receiving account identifier through a separate channel und document whether registration data will change. A material registrant change can have confirmation und inter-registrar lock consequences under the currently effective policy.
Never send passwoderds oder 2FA codes. Do not treat a screenshot, payment receipt oder account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befodere using a NiceNIC account push, confirm the current price, eligible TLD und status, receiving account identifier, acceptance steps, DNS behavioder, reversibility und any registrant-data consequences through the current NiceNIC account oder Suppodert documentation. Do not assume that every Domain is eligible oder that the process is free merely because it is internal.
Expected result
After a push, verify that the Domain appears in the intended account with the expected registration data, nameservers, lock und renewal settings. After a registrar transfer, verify the receiving registrar in RDAP und check the registration term, nameservers und DNS Dienstleistung.
Kjetztn exceptions
ccTLDs may use registry-specific holder-change und transfer procedures. Domains affected by disputes, holds, expiry states, payment restrictions, security review oder court oderders may not be eligible. A registrar may limit oder manually review pushes.
What this answer is based on
ICANN is authoderitative foder the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented woderkflow controls. Applicable agreements, registry rules und law zurückail over this summary.
Frequently asked questions
Does a push unlock the Domain foder transfer?
Nein. Account control, registrar-lock status und inter-registrar eligibility are separate matters.
Does a push move DNS oder hosting?
Neint necessarily. Nameservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account und product design. Verify befodere pushing.
Can I push a newly registrierened Domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
