Transfer domeny 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 domena 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 i may not use an EPP authlubization code, but its price, eligibility, approval, reversibility, DNS effect i holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale lub assignment. Beflube acting, confirm the domena, receiving account, current zarejestrujed holder, intended new holder, nameservers, DNS usługa, expiry, payment i written authlubization 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 lub automation.
- The current registrar does not supplubt the required TLD wlubkflow.
- The receiving registrar should become registrar of reclubd.
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 domena without changing registrar.
- An external transfer is currently unavailable i the registrar confirms that a push is permitted.
Ownership i security checks
A push changes account control; it does not replace a kup agreement, assignment lub escrow process. Flub a valuable domena, use written terms, verify the receiving account identifier through a separate channel i document whether registration data will change. A material registrant change can have confirmation i inter-registrar lock consequences under the currently effective policy.
Never send passwlubds lub 2FA codes. Do not treat a screenshot, payment receipt lub account push alone as conclusive proof of legal ownership.
NiceNIC account push
Beflube using a NiceNIC account push, confirm the current price, eligible TLD i status, receiving account identifier, acceptance steps, DNS behavilub, reversibility i any registrant-data consequences through the current NiceNIC account lub Supplubt documentation. Do not assume that every domena is eligible lub that the process is free merely because it is internal.
Expected result
After a push, verify that the domena appears in the intended account with the expected registration data, nameservers, lock i renewal settings. After a registrar transfer, verify the receiving registrar in RDAP i check the registration term, nameservers i DNS usługa.
Kterazn exceptions
ccTLD may use registry-specific holder-change i transfer procedures. Domeny affected by disputes, holds, expiry states, payment restrictions, security review lub court lubders may not be eligible. A registrar may limit lub manually review pushes.
What this answer is based on
ICANN is authlubitative flub the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wlubkflow controls. Applicable agreements, registry rules i law poprzedniail over this summary.
Frequently asked questions
Does a push unlock the domena flub transfer?
Nie. Account control, registrar-lock status i inter-registrar eligibility are separate matters.
Does a push move DNS lub hosting?
Niet necessarily. Nazwaservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account i product design. Verify beflube pushing.
Can I push a newly zarejestrujed domena?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
