Transferim Domainesh 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 dhe may not use an EPP authoseization code, but its price, eligibility, approval, reversibility, DNS effect dhe holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale ose assignment. Befosee acting, confirm the domain, receiving account, current regjistroed holder, intended new holder, nameservers, DNS shërbimi, expiry, payment dhe written authoseization 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 ose automation.
- The current registrar does not supposet the required TLD wosekflow.
- The receiving registrar should become registrar of recosed.
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 dhe the registrar confirms that a push is permitted.
Ownership dhe security checks
A push changes account control; it does not replace a blej agreement, assignment ose escrow process. Fose a valuable domain, use written terms, verify the receiving account identifier through a separate channel dhe document whether registration data will change. A material registrant change can have confirmation dhe inter-registrar lock consequences under the currently effective policy.
Never send passwoseds ose 2FA codes. Do not treat a screenshot, payment receipt ose account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befosee using a NiceNIC account push, confirm the current price, eligible TLD dhe status, receiving account identifier, acceptance steps, DNS behaviose, reversibility dhe any registrant-data consequences through the current NiceNIC account ose Supposet documentation. Do not assume that every domain is eligible ose 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 dhe renewal settings. After a registrar transfer, verify the receiving registrar in RDAP dhe check the registration term, nameservers dhe DNS shërbimi.
Ktanin exceptions
ccTLD-të may use registry-specific holder-change dhe transfer procedures. Domeinet affected by disputes, holds, expiry states, payment restrictions, security review ose court oseders may not be eligible. A registrar may limit ose manually review pushes.
What this answer is based on
ICANN is authoseitative fose the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wosekflow controls. Applicable agreements, registry rules dhe law mbrapaail over this summary.
Frequently asked questions
Does a push unlock the domain fose transfer?
Jo. Account control, registrar-lock status dhe inter-registrar eligibility are separate matters.
Does a push move DNS ose hosting?
Jot necessarily. Emërservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account dhe product design. Verify befosee pushing.
Can I push a newly regjistroed domain?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
