How a domain transfer works

A domain transfer moves one specific thing: which registrar manages the registration. It does not, by itself, move the website, the email, or the DNS records that point at them. Understanding that separation is most of what makes a transfer boring—in the good sense—because the failures people fear usually come from the services bundled around the domain, not the transfer itself.

What a transfer changes

After a transfer, the domain lives in an account at the new registrar, renews there, and follows that registrar’s terms. For most common endings a transfer also extends the registration, typically adding a year, though the exact treatment varies by ending and situation. The nameservers and DNS records are, in principle, untouched: the domain keeps answering exactly as before while management changes hands.

Inventory before anything else

The exception hiding in “in principle” is bundling. If the losing registrar also hosts the DNS zone—or the email, or forwarding rules—those services may end when the registration leaves. The safe sequence starts with an inventory: where is DNS actually hosted, what records exist (especially the MX and authentication records email depends on), and does the registrant contact email still work? If DNS lives with the old registrar, stand it up somewhere independent first and let it settle. A transfer planned this way has nothing left to break.

The sequence

The mechanics are consistent for most common endings: unlock the domain at the current registrar, obtain the authorization code (sometimes called an EPP or transfer code), and start the transfer at the receiving registrar. Approvals then flow by email or account confirmation, and the transfer completes—often within a day when approved promptly, and otherwise within about five days. The domain resolves normally throughout. Afterward, verify the essentials: lock re-enabled, contacts correct, auto-renewal configured, DNS still answering as expected.

The locks and waiting periods

Transfers have calendar rules. A domain generally cannot transfer within 60 days of its initial registration, and changes to registrant details or a completed transfer commonly start another 60-day hold, depending on the registrars involved. A domain that has already expired may need renewal or redemption first, at different cost. Country-code endings follow their own procedures, which can differ substantially. None of these rules block a well-planned transfer; they decide when it can happen, which is why transfers belong on a calendar rather than in an emergency.

Does the website go down?

Not because of the transfer. Downtime during a transfer is almost always the bundling problem wearing a disguise: the DNS zone disappeared with the old registrar’s services, and the transfer got the blame. Separate the two concerns—move or confirm DNS hosting first, transfer the registration second—and the website and email should not blink.

How Doory handles transfers

Transfers into Doory’s management start at the domain search and continue through the portal checkout, where the connected registrar confirms eligibility, supported endings, and current pricing. Before anything moves, the existing zone is inventoried so nameservers, website records, and email authentication carry over deliberately. Timelines follow the registrars and registries involved—Doory sequences the steps and verifies the result rather than promising a particular date.

The useful conclusion

A transfer is a change of custody, not a migration. Inventory the DNS, unlock, authorize, approve, verify—and treat the 60-day rules as scheduling facts rather than surprises. Done in that order, moving a domain is one of the least dramatic changes a business can make to its infrastructure, which is exactly how it should feel.

Related service:Search and manage domains.