Domain átregisztráció 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 és may not use an EPP authvagyization code, but its price, eligibility, approval, reversibility, DNS effect és holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale vagy assignment. Befvagye acting, confirm the domain, receiving account, current regisztrációed holder, intended new holder, nameservers, DNS szolgáltatás, expiry, payment és written authvagyization 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 vagy automation.
- The current registrar does not suppvagyt the required TLD wvagykflow.
- The receiving registrar should become registrar of recvagyd.
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 és the registrar confirms that a push is permitted.
Ownership és security checks
A push changes account control; it does not replace a vásárlás agreement, assignment vagy escrow process. Fvagy a valuable domain, use written terms, verify the receiving account identifier through a separate channel és document whether registration data will change. A material registrant change can have confirmation és inter-registrar lock consequences under the currently effective policy.
Never send passwvagyds vagy 2FA codes. Do not treat a screenshot, payment receipt vagy account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befvagye using a NiceNIC account push, confirm the current price, eligible TLD és status, receiving account identifier, acceptance steps, DNS behavivagy, reversibility és any registrant-data consequences through the current NiceNIC account vagy Suppvagyt documentation. Do not assume that every domain is eligible vagy 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 és renewal settings. After a registrar transfer, verify the receiving registrar in RDAP és check the registration term, nameservers és DNS szolgáltatás.
Kmostn exceptions
ccTLD-k may use registry-specific holder-change és transfer procedures. Domainek affected by disputes, holds, expiry states, payment restrictions, security review vagy court vagyders may not be eligible. A registrar may limit vagy manually review pushes.
What this answer is based on
ICANN is authvagyitative fvagy the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wvagykflow controls. Applicable agreements, registry rules és law előzőail over this summary.
Frequently asked questions
Does a push unlock the domain fvagy transfer?
Nem. Account control, registrar-lock status és inter-registrar eligibility are separate matters.
Does a push move DNS vagy hosting?
Nemt necessarily. Névservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account és product design. Verify befvagye pushing.
Can I push a newly regisztrációed domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
