What Happens Between Asking and Finishing
A domain transfer usually takes between a few hours and seven days, and the long end is almost always a person or a lock, not the internet. Moving the registration to a new registrar does not move your website or your email by itself, so a transfer done in the right order is invisible to visitors.
This is for the person who owns a business domain and wants to move it from one registrar to another, or who has been handed one and is not sure where it lives. The first half explains the steps and how long each takes. The second half covers what goes wrong and how to move without taking the site or the email down.
Find Out Where the Domain Is Registered Today
Before anything else, look the name up at ICANN Lookup. It shows the current registrar, the creation and expiry dates, and the status codes, including whether a transfer lock is set. Those four facts answer most of the questions you will be asked later, and the creation date tells you at once whether the 60-day rule below applies.
Also find out who holds the login. On domains bought years ago by a web designer, a former employee, or a previous agency, the account may belong to someone else. Getting access to that account, or asking the holder to start the transfer, comes before any technical step, and it is the slowest part of many transfers.
A transfer changes who renews the domain, nothing else
Two different things get called "the domain." The registration is the record at your registrar saying you hold the name. The DNS is the set of records that say where the website and mail go. A transfer moves the first. If your nameservers stay the same, the second keeps working through the whole move, which is why you can change registrars without anyone noticing.
The trouble starts when the two are bundled. Many registrars host your DNS by default, so leaving them also leaves your DNS behind unless you copy the records first. We come back to this in the second half; it is the most common cause of a transfer that "broke the website."
Release the lock and get the authorization code first
A registrar places a transfer lock on every domain, shown as the status clientTransferProhibited. You have to turn it off in your account at the current registrar. You then ask for the authorization code, sometimes called the EPP code or auth code, which is a one-time secret that proves you control the name. The new registrar asks for it at the start of the order.
Under ICANN's transfer policy (the 2016 version of the text, checked October 2026), a registrar that does not offer self-service has five calendar days from your request to give you the code and remove the lock. Most offer it instantly in the account. ICANN has been reviewing this policy, so treat any day counts here as the floor to check, not a promise from your registrar.
The old registrar has five days to answer, and silence counts as yes
After you order the transfer at the new registrar, the old one is asked to release the name. The same policy says that if the current registrar fails to respond within five calendar days, the transfer is approved by default. That is why transfers often finish on day five without anyone clicking anything.
You can usually move faster. Once the order is in, look for an email at the address on the domain record asking you to approve, or a pending-transfer screen in your old registrar's account. Approving it there typically completes the transfer in minutes to hours, depending on the registry. If the email address on the record is dead, the approval email goes nowhere, and you are back to waiting out the five days.
The 60-day rules decide whether you can start at all
The policy lets a registrar refuse a transfer in three situations that catch people by surprise. A domain cannot move within 60 days of its creation date. It cannot move within 60 days of a previous transfer. And a change of registrant, such as correcting the owner name, can trigger its own 60-day lock, though a registrar may let you opt out of that lock before you make the change.
The practical advice: do not edit the owner details and request a transfer in the same week unless the registrar tells you it will not lock the domain. Make the contact corrections first and give them time to settle.
A transfer adds a year to what you already paid
A completed transfer extends the registration by one year, up to a ten-year total. You are not losing the time you already paid for; it is added to it. Many registrars charge the renewal fee at the point of transfer, and some bundle the first year of hosting or privacy at a promotional price that rises later. Read the line items before confirming.
Moving close to expiry is allowed, but do not leave it to the last day. A domain that expires mid-transfer can fall into a grace period where recovery costs extra, and how expired names are handled differs between registrars and registries, so renew first if the date is close.
Moving Without Taking Anything Down
A clean transfer is mostly preparation: record what the DNS holds today, keep it answering the whole time, and change the nameservers only when the new copy is ready. The steps below are the order that avoids downtime.
Copy Every DNS Record Before You Start
Export the zone or screenshot every record at the current DNS host. You are looking for the A and CNAME records that serve the website, the MX records that deliver mail, the TXT records for SPF, DKIM, and DMARC, and the less obvious ones: verification records for Google and Microsoft, and any subdomains pointing at other services. The DNS record types guide explains what each one does and which ones break things when they go missing.
Missing TXT records are the quiet failure. The website comes back and email starts landing in spam two days later, because the SPF or DKIM record did not make the trip. The SPF and DKIM posts show what those records should look like.
Keep the nameservers where they are until the new zone is ready
If your DNS is hosted at the old registrar, the safe sequence is to build the identical zone at the new host first, confirm each record by querying it, and only then change the nameservers. During the switch, resolvers around the world update at different times, so both copies should answer correctly for a while. Do not delete the old zone for a few days.
The alternative is to keep DNS at a separate provider entirely, so the registrar can change without touching it. That separation is why many businesses keep the registration and the DNS in different places.
Turn off DNSSEC before the move, or carry it across
If DNSSEC is enabled, the registry holds a DS record that must match the keys at your DNS host. Move the DNS without updating or removing that record and validating resolvers will treat your domain as broken. The simplest path is to remove the DS record at the old registrar, wait for the record's lifetime to expire, transfer, and re-enable DNSSEC at the new place. If you do not know whether it is on, a DNSSEC checker on the domain will tell you.
Check the Contact Email and Privacy Settings
The approval message and the confirmation go to the registrant email on the record. If that mailbox is on the domain you are transferring, and the MX records are about to change, you can lock yourself out of your own approval. Use an address on a different domain for the length of the transfer.
Privacy protection can also be dropped by a transfer. If the new registrar does not include it by default, your name and address may appear in public records until you switch it back on, so check the setting afterwards.
Verify After the Move, Then Lock It Again
When the registrar says the transfer is complete, confirm that the website loads, that mail sends and receives in both directions, that the registrar lock is back on, and that auto-renew is on. A transfer lock that came off at the start of the process does not always return on its own. Put the new expiry date in a calendar you control.
Do not close the old account the same day. Keep it open for a few weeks in case an unexpected record or email forwarding rule surfaces.
If you would rather not do this alone, Domain Management from Cascadia watches the expiry date, the registrar lock, and the nameservers every day, with renewal warnings at 60, 30, and 7 days. It lists transfers handled for you, transfer attempts surfaced early, and nameservers checked after any transfer, and the domain stays registered in your name. If you are comparing registrars first, the domain registrar comparisons are a place to start, and DNS management covers the records themselves. Related reading: the DMARC alignment post covers what to recheck once mail is flowing from the new setup.
