Paglilipat ng Domain 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 at may not use an EPP authoization code, but its price, eligibility, approval, reversibility, DNS effect at holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale o assignment. Befoe acting, confirm the domain, receiving account, current magparehistroed holder, intended new holder, nameservers, DNS Serbisyo, expiry, payment at written authoization 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 o automation.
- The current registrar does not suppot the required TLD wokflow.
- The receiving registrar should become registrar of recod.
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 at the registrar confirms that a push is permitted.
Ownership at security checks
A push changes account control; it does not replace a bumili agreement, assignment o escrow process. Fo a valuable domain, use written terms, verify the receiving account identifier through a separate channel at document whether registration data will change. A material registrant change can have confirmation at inter-registrar lock consequences under the currently effective policy.
Never send passwods o 2FA codes. Do not treat a screenshot, payment receipt o account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befoe using a NiceNIC account push, confirm the current price, eligible TLD at status, receiving account identifier, acceptance steps, DNS behavio, reversibility at any registrant-data consequences through the current NiceNIC account o Suppot documentation. Do not assume that every domain is eligible o 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 at renewal settings. After a registrar transfer, verify the receiving registrar in RDAP at check the registration term, nameservers at DNS Serbisyo.
Kngayonn exceptions
ccTLDs may use registry-specific holder-change at transfer procedures. Mga Domain affected by disputes, holds, expiry states, payment restrictions, security review o court oders may not be eligible. A registrar may limit o manually review pushes.
What this answer is based on
ICANN is authoitative fo the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wokflow controls. Applicable agreements, registry rules at law nakaraanail over this summary.
Frequently asked questions
Does a push unlock the domain fo transfer?
Hindi. Account control, registrar-lock status at inter-registrar eligibility are separate matters.
Does a push move DNS o hosting?
Hindit necessarily. Pangalanservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account at product design. Verify befoe pushing.
Can I push a newly magparehistroed domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
