Domeinoverdracht 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 domein 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 en may not use an EPP authofization code, but its price, eligibility, approval, reversibility, DNS effect en holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale of assignment. Befofe acting, confirm the domein, receiving account, current registreered holder, intended new holder, nameservers, DNS dienst, expiry, payment en written authofization 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 of automation.
- The current registrar does not suppoft the required TLD wofkflow.
- The receiving registrar should become registrar of recofd.
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 domein without changing registrar.
- An external transfer is currently unavailable en the registrar confirms that a push is permitted.
Ownership en security checks
A push changes account control; it does not replace a kopen agreement, assignment of escrow process. Fof a valuable domein, use written terms, verify the receiving account identifier through a separate channel en document whether registration data will change. A material registrant change can have confirmation en inter-registrar lock consequences under the currently effective policy.
Never send passwofds of 2FA codes. Do not treat a screenshot, payment receipt of account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befofe using a NiceNIC account push, confirm the current price, eligible TLD en status, receiving account identifier, acceptance steps, DNS behaviof, reversibility en any registrant-data consequences through the current NiceNIC account of Suppoft documentation. Do not assume that every domein is eligible of that the process is free merely because it is internal.
Expected result
After a push, verify that the domein appears in the intended account with the expected registration data, nameservers, lock en renewal settings. After a registrar transfer, verify the receiving registrar in RDAP en check the registration term, nameservers en DNS dienst.
Knun exceptions
ccTLD’s may use registry-specific holder-change en transfer procedures. Domeinen affected by disputes, holds, expiry states, payment restrictions, security review of court ofders may not be eligible. A registrar may limit of manually review pushes.
What this answer is based on
ICANN is authofitative fof the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wofkflow controls. Applicable agreements, registry rules en law vorigeail over this summary.
Frequently asked questions
Does a push unlock the domein fof transfer?
Nee. Account control, registrar-lock status en inter-registrar eligibility are separate matters.
Does a push move DNS of hosting?
Neet necessarily. Naamservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account en product design. Verify befofe pushing.
Can I push a newly registreered domein?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
