BUY WEBSITES
BUY DOMAINS
LOGIN
SIGNUP
Push vs Transfer: When Each Domain Move Makes Sense (and the Lock That Catches Buyers)
A push and a transfer both move ownership of a domain name, and people use the words as if they were the same thing. They are not. A push moves a domain between two accounts at the same registrar. A transfer moves a domain from one registrar to a different registrar.
That single difference decides everything else: whether you pay a fee, whether you wait minutes or a week, whether you need an authorization code, and whether the registration gains a year. Pick the wrong one and you either pay for a move that was free, or you wait days for a handoff that was supposed to be instant.
This guide gives you the at-a-glance comparison, the honest “when each makes sense” decision, and the one trap the registrar marketing pages skip: a push can quietly trigger a 60-day lock that blocks your next transfer. When you are acquiring an aged domain, getting this right is the difference between clean custody and a week of avoidable friction, which is why SEO Domains screens every listing for a clean transfer path before it is priced.
What a push and a transfer actually mean
A push moves a domain between two accounts at the same registrar. A transfer moves a domain from one registrar to a different registrar. Both change who controls the domain. The registrar boundary is the line that separates them, and it sets the fee, the speed, the authorization code, and the registration year.
The confusion is understandable, because the end result looks identical. After either move, a domain that used to sit in one place now sits in another. The mechanics underneath are different operations governed by different rules, and the rules are what this guide unpacks.
A push: an account-to-account move inside one registrar
A push hands a domain from your account to another account at the same registrar. NameSilo, which documents the operation plainly, describes it as moving a domain between two accounts at the one registrar, completed by entering the recipient’s username and confirming with a password, free for both parties and finished instantly. Porkbun runs the same operation and frames it the same way, with a recipient who has completed account verification.
Because the domain never leaves the registrar, nothing about its registration record has to be rebuilt. The expiry date stays put, no authorization code changes hands, and the domain is in the recipient’s account in the time it takes to confirm.
A transfer: a move to a different registrar
A transfer is the heavier operation. It moves a domain from its current registrar to a new one, which means the receiving registrar has to take over the registration entirely. ICANN, the body that sets the inter-registrar transfer policy for generic top-level domains, requires an authorization code for this, and the receiving registrar charges a fee that includes one year of renewal.
Name.com sets the practical expectation: a transfer typically runs up to seven days, the cost is generally lower than a straight renewal, and the domain’s expiration date is extended by a year when it lands. The move is real registrar-to-registrar migration, not a record edit.
Push (same registrar)
Moves the domain to another account at the same registrar. Instant, free, no authorization code, expiry date unchanged. Ownership and control move; the registration stays in place.
Transfer (different registrar)
Moves the domain to a new registrar. Five to seven days, a fee, an EPP authorization code required, and one year added to the registration. Ownership and the registration record both move.
Connecting (not a move at all)
Points the domain’s nameservers at a host while it stays where it is registered. No ownership change, no custody change. This is a DNS edit, and it is the operation people confuse with a transfer.
Push vs transfer at a glance: the eight differences
Eight dimensions separate a push from a transfer: the scope of the move, the cost, the speed, whether an authorization code is needed, the registration-year effect, the inter-registrar lock, reversibility, and what happens to DNS. The registrar boundary drives all eight. Read the table once and the “which one” question answers itself in nearly every case.
The registrar marketing pages each describe one side from their own product’s point of view. The table below consolidates the eight axes into a single comparison, with each row attributed to the source that documents it. Read top to bottom, it is the fastest way to settle a decision before you start clicking.
| Dimension | Push (same registrar) | Transfer (different registrar) |
|---|---|---|
| Scope of the move | Account to account, one registrar | Registrar to registrar |
| Cost | Free at most registrars (NameSilo, Fabulous) | Receiving registrar’s fee, lower than a renewal (Name.com) |
| Speed | Instant to a short confirmation window (NameSilo, Porkbun) | 5 to 7 days, expeditable to 1 to 2 (Name.com, NameSilo) |
| Authorization (EPP) code | Not required (NameSilo, dondominio) | Required (ICANN transfer policy) |
| Registration year | Unchanged, remaining time only (Fabulous, NameSilo) | One year added on completion (Name.com, Fabulous) |
| Inter-registrar lock | Not blocked by the 60-day transfer lock | Blocked for 60 days after registration or a prior transfer (ICANN) |
| Reversibility | Final and irreversible once accepted (dondominio) | Can be reversed within the transfer window before it completes |
| DNS and email | Untouched, nameservers stay as set | Untouched if you migrate nameservers first, at risk if you do not |
When a push makes sense
A push makes sense whenever both accounts live at the same registrar. It is instant, free, leaves the expiry date alone, and needs no authorization code. The classic cases are a same-registrar sale, moving a domain between your own accounts, and an escrow-backed handoff where the buyer already holds an account at that registrar.
The deciding question is simple. If the domain is already registered where the recipient holds an account, a push is the faster and cheaper move every time. There is no reason to pay a transfer fee or wait a week to cross a registrar boundary you do not need to cross.
The cases where a push is the right call
- A same-registrar sale. Buyer and seller both hold accounts at one registrar, so custody moves the instant the recipient accepts. This is the standard handoff for an in-marketplace purchase.
- Moving between your own accounts. Consolidating a portfolio, or splitting a client’s domain into a dedicated account, is an internal push with zero cost and no waiting.
- An escrow-backed deal at a shared registrar. When an escrow service holds payment, an instant push releases custody the moment funds clear, with no multi-day transfer hanging over the deal.
- Keeping the remaining registration. A push preserves the exact expiry date, so a domain with three years left stays at three years rather than resetting the clock.
The trade-off is that a push is final. Dondominio states the operation is irreversible once the receiving account accepts it, so the recipient username has to be correct before you confirm. The step-by-step mechanics of running one are covered in the Intra-registrar account push walkthrough.
When a transfer makes sense
A transfer makes sense when the domain has to end up at a different registrar than the one it sits on now. The common drivers are buying a domain you want on your own registrar, consolidating a portfolio under one provider, leaving a registrar you no longer trust, and gaining the extra year of registration that a transfer adds.
The price of a transfer is time and a fee, and in exchange you get registrar independence and a year of renewal folded in. When the destination registrar is non-negotiable, that price is worth paying, because a push cannot cross the boundary at all.
The cases where a transfer is the right call
- You want the domain on your registrar. If you bought a domain that sits at a registrar you do not use, only a transfer brings it home to the provider where you manage the rest of your portfolio.
- Consolidation under one provider. Pulling domains scattered across three or four registrars into one account simplifies billing, renewals, and DNS, and each migration is a transfer.
- Leaving a registrar you distrust. Name.com lists pricing, support, and renewal transparency as the reasons people move. A transfer is the exit, and it is the only way out of a registrar entirely.
- Gaining the extra year. A transfer adds one year of registration on completion, so a name close to expiry buys time and a new home in a single operation.
Before a transfer can start, the domain has to be unlocked and an authorization code retrieved, and the 60-day eligibility windows have to be clear. The full sequence is documented in the Inter-registrar domain transfer walkthrough, and the code itself in EPP code (auth code) explained.
The lock paradox: why “a push has no lock” is only half true
Every comparison calls a push the no-lock option, and that is true for the inter-registrar transfer lock. It is only half the picture. If a push changes the registrant, it can trigger ICANN’s separate 60-day Change of Registrant lock, which then blocks an inter-registrar transfer. The honest read is that a push avoids one lock and can start another.
This is the trap the registrar marketing pages skip, and the reason it matters to buyers. A push is sold as the clean, instant move with no waiting period attached. That holds for the transfer lock. It does not account for what happens when the push also changes who the registrant of record is.
Two different 60-day locks, and why they get confused
ICANN’s transfer policy carries two distinct 60-day windows, and conflating them is where buyers get caught. The first is the inter-registrar transfer lock: a domain cannot transfer to a new registrar within 60 days of its registration or its last transfer. A push does not trip this one, because a push is not an inter-registrar transfer.
The second is the Change of Registrant lock. Under ICANN’s Transfer Policy, in force since 1 December 2016, a material change to the registrant’s name, organization, or email is a Change of Registrant, and after one the domain can be locked from inter-registrar transfer for 60 days. A push that moves the domain to a new owner is a registrant change, so the same operation marketed as lock-free can start the second lock.
The opt-out is the done-right move, and the wording is precise: the opportunity exists before the change, not after it. A buyer who plans to transfer the domain onward soon after acquiring it wants that opt-out exercised at the moment of the registrant change, because once the lock starts, the next transfer waits out the full 60 days.
The done-wrong version is to push a freshly bought domain into your account, skip the opt-out, then discover the inter-registrar transfer you wanted is locked for 60 days. The fix is to plan the custody sequence before the push, not after. The full mechanics of the rule live in ICANN’s 60-day transfer rule.
Registrar terminology, and the custody-versus-connecting line
Registrars do not all call a push a push. The same account-to-account move appears as push, account move, change of ownership, and internal transfer depending on the provider. Worse, “transfer” gets used for connecting a domain by DNS, which moves nothing. Knowing the synonyms keeps you from clicking the wrong operation.
Two terminology problems trip people up. The first is that the push operation has a different label at every registrar. The second is that the word transfer is borrowed by tutorials that mean connecting, a DNS edit that leaves custody exactly where it was.
The same operation, four different names
| Registrar label you see | What it actually is | Tell |
|---|---|---|
| Push, domain push | Account-to-account move, same registrar | Asks for a recipient account or username, not a code |
| Change of ownership, change ownership | Account-to-account move, same registrar | Moves the domain to another account at the one registrar |
| Internal transfer, account transfer | Account-to-account move, same registrar | The word transfer, but no other registrar is involved |
| Transfer, transfer out, transfer in | Inter-registrar move | Asks for an authorization or EPP code |
| Connect, point, connect a domain | A DNS nameserver edit, not a move | Changes nameservers, never asks who owns the domain |
The practical rule is to read what the interface requests. If the registrar asks for a recipient’s account or username, the operation is a push and it stays inside that registrar. If it asks for an authorization code, the operation crosses to another registrar and it is a transfer. If it only asks for nameservers, nothing about ownership is moving at all.
That last case is the custody-versus-connecting line. A push and a transfer both change who controls the domain. Connecting points the domain at a different host while custody stays put, which is why a “transfer vs connect” tutorial answers a different question than this one. Whether the domain is locked at all is its own decision, covered in Transfer locking and when to unlock.
Just bought a domain: push or transfer, step by step
When you acquire a domain, the push-or-transfer decision follows a short sequence: confirm where the domain is registered, decide where it needs to end up, check the registrant-change implication, then run the matching operation. At each step the done-right move sits beside the specific mistake that costs you time or money.
This is the decision a buyer faces, and the comparison pages skip it because they answer “what is the difference” instead of “what do I do with the domain I just bought.” The five steps below walk the custody handoff from purchase to settled ownership.
-
Source a domain with a clean, verified custody path
The decision starts before the move, at acquisition. The done-right move is to buy a domain whose registrar, lock status, and registrant record are known and clean, so the handoff is predictable. Browse screened, transfer-ready aged and expired domains on the SEO Domains marketplace, where the custody path is checked before a listing is priced.
The mistake: buying an unvetted name from a raw drop list with an unknown lock state or a registrar that resists transfers out. A messy custody path turns a clean handoff into a week of support tickets.
-
Confirm which registrar the domain sits on
Establish where the domain is registered right now. The done-right move is to confirm the current registrar before choosing the operation, because the registrar boundary is the entire decision.
The mistake: assuming a push is possible across registrars. A push only works inside one registrar, so attempting it across two fails and wastes the attempt.
-
Decide where the domain needs to end up
If you already hold an account at the domain’s current registrar and are content to keep it there, a push settles custody instantly and free. If the domain has to live on a different registrar, a transfer is the only operation that crosses the boundary.
The mistake: running a transfer when both parties share a registrar. You pay a fee and wait a week for a move a free, instant push would have completed at once.
-
Check the registrant-change and lock implication
If the move changes the registrant and you intend to transfer the domain onward, the done-right move is to exercise ICANN’s Change of Registrant opt-out at the moment of the change, keeping the inter-registrar path open.
The mistake: pushing first, opting out never, then finding the onward transfer locked for 60 days. The opt-out has to happen before the registrant change, not after.
-
Run the operation and verify custody
For a push, confirm the recipient account is correct, then accept. For a transfer, unlock the domain, retrieve the EPP code, and initiate at the receiving registrar. The done-right move is a post-move check that DNS, email, and the expiry date are intact.
The mistake: skipping the verification and assuming email survived. The fix is a structured pass, set out in the Post-transfer checklist for aged domains.
The mistakes that turn a simple move into a problem
The errors that derail a push or a transfer are a short, repeatable list. The table consolidates them with the fix for each, so the operation runs clean the first time.
| The mistake | Why it costs you | The fix |
|---|---|---|
| Transferring when a push was possible | You pay a fee and wait a week for a free, instant move | Check whether both accounts share a registrar first |
| Attempting a push across registrars | A push only works inside one registrar, so it fails | Use a transfer for any cross-registrar move |
| Skipping the unlock before a transfer | The receiving registrar cannot pull a locked domain | Unlock and retrieve the EPP code before you initiate |
| Missing the Change of Registrant opt-out | An onward transfer is blocked for 60 days | Exercise the opt-out at the moment ownership changes |
| Assuming email and DNS survive automatically | A mail or site outage on the day of the move | Migrate nameservers ahead of a transfer, verify after |
| Pushing to the wrong recipient account | A push is final and cannot be reversed once accepted | Confirm the recipient username before you accept |
When a transfer does not complete despite a clean setup, the diagnostic walkthrough is in Transfer failures: common causes and fixes, and the broader timing and policy detail sits in the Transfer Process hub.
Push vs transfer frequently asked questions
The five questions buyers and sellers raise when they search for the difference between a domain push and a transfer, answered against the registrar documentation and ICANN’s transfer policy.
Q1What is a domain push?
A domain push moves a domain between two accounts at the same registrar. It is free at the registrars that offer it, finishes instantly or within a short confirmation window, needs no authorization code, and leaves the expiry date unchanged. NameSilo and Porkbun both document it as an account-to-account move confirmed by the recipient.
Q2Will I lose my email or website when I transfer a domain?
Not if you migrate nameservers before the transfer. A transfer moves the registration, not the DNS configuration, so email and the website stay live when the nameservers are pointed at the receiving setup ahead of the move. The risk of an outage comes from transferring first and configuring DNS afterward. A push does not touch DNS at all, since the domain never leaves the registrar.
Q3Does a push change the domain’s expiry date?
No. A push moves only the remaining registration, so a domain with two years left arrives in the new account with two years left. A transfer is the operation that adds time, folding one year of renewal into the move on completion, per Name.com and Fabulous.
Q4Can I transfer a domain to a new registrar right after buying it?
Not always. ICANN’s transfer policy blocks an inter-registrar transfer within 60 days of registration or a prior transfer. A Change of Registrant, which a push to a new owner can be, can also start a separate 60-day lock unless the opt-out is exercised before the change. If an onward transfer is the plan, handle the opt-out at the moment ownership changes.
Q5Is a push or a transfer the right move when I buy a domain?
Push if the seller and you share a registrar and you are content to keep the domain there, because the handoff is instant and free. Transfer if the domain has to end up on your own registrar, because a transfer is the only operation that crosses the registrar boundary, and it adds a year in the process. Starting from a domain with a clean, verified custody path makes either operation predictable.
Start from a transfer-ready domain: the foundation
The push-or-transfer decision is only as clean as the domain underneath it. A domain with a known registrar, a clear lock status, and a documented registrant record moves predictably, by push or by transfer. An unvetted name with an unknown custody path is where the friction starts. SEO Domains operates the curated marketplace where that custody path is screened before a domain is listed.
Why the custody path decides the experience
Every operation in this guide depends on the same underlying variable: the state of the domain you are moving. A clean, transfer-ready domain pushes or transfers without a fight, because its lock status, registrar, and registration record are known going in. A name pulled from a raw drop list with an unknown history is where a routine move turns into a support queue.
What a transfer-ready aged domain looks like
- A known current registrar, so the push-or-transfer choice is settled before you start.
- A clear lock status, with no surprise registrar lock blocking a transfer out.
- A documented registrant record, so a Change of Registrant and its opt-out can be planned.
- A clean backlink and history profile, so the aged domain you move is an asset worth the move.
A domain that passes these is one you can push or transfer with confidence. A domain that fails them is a liability before the first click, whichever operation you choose.
| Check | Unvetted drop (friction) | Transfer-ready domain (asset) |
|---|---|---|
| Current registrar | Unknown until you dig | Documented before purchase |
| Lock status | Surprise locks block the move | Clear, with a clean transfer path |
| Registrant record | Opaque, opt-out unplanned | Known, opt-out plannable |
| History and backlinks | Toxic or unverified | Screened before listing |
| Outcome at handoff | A week of support tickets | A clean push or transfer |
Browse transfer-ready aged and expired domains
The demand behind every push-or-transfer question is a clean domain you can move into your own control without friction. That is the product, not a registrar service and not a hosting plan. SEO Domains operates the curated marketplace where aged and expired domains are screened across their registrar status, custody path, and backlink profile before they are listed and priced.
