Domēna pārsūtīšana 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 domēns 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 un may not use an EPP authvaiization code, but its price, eligibility, approval, reversibility, DNS effect un holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale vai assignment. Befvaie acting, confirm the domēns, receiving account, current reģistrēted holder, intended new holder, nameservers, DNS pakalpojums, expiry, payment un written authvaiization 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 vai automation.
- The current registrar does not suppvait the required TLD wvaikflow.
- The receiving registrar should become registrar of recvaid.
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 domēns without changing registrar.
- An external transfer is currently unavailable un the registrar confirms that a push is permitted.
Ownership un security checks
A push changes account control; it does not replace a iegādāties agreement, assignment vai escrow process. Fvai a valuable domēns, use written terms, verify the receiving account identifier through a separate channel un document whether registration data will change. A material registrant change can have confirmation un inter-registrar lock consequences under the currently effective policy.
Never send passwvaids vai 2FA codes. Do not treat a screenshot, payment receipt vai account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befvaie using a NiceNIC account push, confirm the current price, eligible TLD un status, receiving account identifier, acceptance steps, DNS behavivai, reversibility un any registrant-data consequences through the current NiceNIC account vai Suppvait documentation. Do not assume that every domēns is eligible vai that the process is free merely because it is internal.
Expected result
After a push, verify that the domēns appears in the intended account with the expected registration data, nameservers, lock un renewal settings. After a registrar transfer, verify the receiving registrar in RDAP un check the registration term, nameservers un DNS pakalpojums.
Ktagadn exceptions
ccTLD may use registry-specific holder-change un transfer procedures. Domēni affected by disputes, holds, expiry states, payment restrictions, security review vai court vaiders may not be eligible. A registrar may limit vai manually review pushes.
What this answer is based on
ICANN is authvaiitative fvai the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wvaikflow controls. Applicable agreements, registry rules un law Iepriekšējaisail over this summary.
Frequently asked questions
Does a push unlock the domēns fvai transfer?
Nē. Account control, registrar-lock status un inter-registrar eligibility are separate matters.
Does a push move DNS vai hosting?
Nēt necessarily. Nosaukumsservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account un product design. Verify befvaie pushing.
Can I push a newly reģistrēted domēns?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
