Overføring av domene 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 domenet 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 og may not use an EPP authellerization code, but its price, eligibility, approval, reversibility, DNS effect og holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale eller assignment. Befellere acting, confirm the domenet, receiving account, current registrered holder, intended new holder, nameservers, DNS tjeneste, expiry, payment og written authellerization 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 eller automation.
- The current registrar does not suppellert the required TLD wellerkflow.
- The receiving registrar should become registrar of recellerd.
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 domenet without changing registrar.
- An external transfer is currently unavailable og the registrar confirms that a push is permitted.
Ownership og security checks
A push changes account control; it does not replace a kjøp agreement, assignment eller escrow process. Feller a valuable domenet, use written terms, verify the receiving account identifier through a separate channel og document whether registration data will change. A material registrant change can have confirmation og inter-registrar lock consequences under the currently effective policy.
Never send passwellerds eller 2FA codes. Do not treat a screenshot, payment receipt eller account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befellere using a NiceNIC account push, confirm the current price, eligible TLD og status, receiving account identifier, acceptance steps, DNS behavieller, reversibility og any registrant-data consequences through the current NiceNIC account eller Suppellert documentation. Do not assume that every domenet is eligible eller that the process is free merely because it is internal.
Expected result
After a push, verify that the domenet appears in the intended account with the expected registration data, nameservers, lock og renewal settings. After a registrar transfer, verify the receiving registrar in RDAP og check the registration term, nameservers og DNS tjeneste.
Knån exceptions
ccTLDs may use registry-specific holder-change og transfer procedures. Domenenavn affected by disputes, holds, expiry states, payment restrictions, security review eller court ellerders may not be eligible. A registrar may limit eller manually review pushes.
What this answer is based on
ICANN is authelleritative feller the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wellerkflow controls. Applicable agreements, registry rules og law forrigeail over this summary.
Frequently asked questions
Does a push unlock the domenet feller transfer?
Nei. Account control, registrar-lock status og inter-registrar eligibility are separate matters.
Does a push move DNS eller hosting?
Neit necessarily. Navnservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account og product design. Verify befellere pushing.
Can I push a newly registrered domenet?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
