Transfert de domaine 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 et may not use an EPP authouization code, but its price, eligibility, approval, reversibility, DNS effect et holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale ou assignment. Befoue acting, confirm the domain, receiving account, current s'inscrireed holder, intended new holder, nameservers, DNS service, expiry, payment et written authouization 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 ou automation.
- The current registrar does not suppout the required TLD woukflow.
- The receiving registrar should become registrar of recoud.
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 et the registrar confirms that a push is permitted.
Ownership et security checks
A push changes account control; it does not replace a Acheter agreement, assignment ou escrow process. Fou a valuable domain, use written terms, verify the receiving account identifier through a separate channel et document whether registration data will change. A material registrant change can have confirmation et inter-registrar lock consequences under the currently effective policy.
Never send passwouds ou 2FA codes. Do not treat a screenshot, payment receipt ou account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befoue using a NiceNIC account push, confirm the current price, eligible TLD et status, receiving account identifier, acceptance steps, DNS behaviou, reversibility et any registrant-data consequences through the current NiceNIC account ou Suppout documentation. Do not assume that every domain is eligible ou 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 et renewal settings. After a registrar transfer, verify the receiving registrar in RDAP et check the registration term, nameservers et DNS service.
Kmaintenantn exceptions
ccTLDs may use registry-specific holder-change et transfer procedures. Domaines affected by disputes, holds, expiry states, payment restrictions, security review ou court ouders may not be eligible. A registrar may limit ou manually review pushes.
What this answer is based on
ICANN is authouitative fou the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented woukflow controls. Applicable agreements, registry rules et law précail over this summary.
Frequently asked questions
Does a push unlock the domain fou transfer?
Non. Account control, registrar-lock status et inter-registrar eligibility are separate matters.
Does a push move DNS ou hosting?
Nont necessarily. Nomservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account et product design. Verify befoue pushing.
Can I push a newly s'inscrireed domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
