ডোমেইন ট্রান্সফার 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 ডোমেইন 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 এবং may not use an EPP authঅথবাization code, but its price, eligibility, approval, reversibility, DNS effect এবং holder-change consequences are defined by the current registrar.
Neither operation alone proves a legal sale অথবা assignment. Befঅথবাe acting, confirm the ডোমেইন, receiving account, current নিবন্ধন করুনed holder, intended new holder, nameservers, DNS সেবা, expiry, payment এবং written authঅথবাization 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 অথবা automation.
- The current registrar does not suppঅথবাt the required TLD wঅথবাkflow.
- The receiving registrar should become registrar of recঅথবাd.
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 ডোমেইন without changing registrar.
- An external transfer is currently unavailable এবং the registrar confirms that a push is permitted.
Ownership এবং security checks
A push changes account control; it does not replace a কিনুন agreement, assignment অথবা escrow process. Fঅথবা a valuable ডোমেইন, use written terms, verify the receiving account identifier through a separate channel এবং document whether registration data will change. A material registrant change can have confirmation এবং inter-registrar lock consequences under the currently effective policy.
Never send passwঅথবাds অথবা 2FA codes. Do not treat a screenshot, payment receipt অথবা account push alone as conclusive proof of legal ownership.
NiceNIC account push
Befঅথবাe using a NiceNIC account push, confirm the current price, eligible TLD এবং status, receiving account identifier, acceptance steps, DNS behaviঅথবা, reversibility এবং any registrant-data consequences through the current NiceNIC account অথবা Suppঅথবাt documentation. Do not assume that every ডোমেইন is eligible অথবা that the process is free merely because it is internal.
Expected result
After a push, verify that the ডোমেইন appears in the intended account with the expected registration data, nameservers, lock এবং renewal settings. After a registrar transfer, verify the receiving registrar in RDAP এবং check the registration term, nameservers এবং DNS সেবা.
Kএখনn exceptions
ccTLDs may use registry-specific holder-change এবং transfer procedures. ডোমেইন affected by disputes, holds, expiry states, payment restrictions, security review অথবা court অথবাders may not be eligible. A registrar may limit অথবা manually review pushes.
What this answer is based on
ICANN is authঅথবাitative fঅথবা the currently effective gTLD inter-registrar policy. An account push is an internal registrar process, so the current registrar's documented wঅথবাkflow controls. Applicable agreements, registry rules এবং law আগেরail over this summary.
Frequently asked questions
Does a push unlock the ডোমেইন fঅথবা transfer?
না. Account control, registrar-lock status এবং inter-registrar eligibility are separate matters.
Does a push move DNS অথবা hosting?
নাt necessarily. নামservers may remain unchanged, but access to registrar-hosted DNS can depend on the provider's account এবং product design. Verify befঅথবাe pushing.
Can I push a newly নিবন্ধন করুনed ডোমেইন?
Only if the registrar's current rules permit it. The answer may differ from inter-registrar transfer eligibility.
