How to Transfer a Domain Without Taking Your Website or Email Offline
November 2, 2026
Short answer: a domain transfer changes only the registrar that holds your registration. It does not move your website, your mailboxes or (unless you change it) your DNS. Downtime happens when DNS records go missing or get edited while the transfer is in flight. So: write down your DNS records, keep your nameservers where they are, change one thing at a time, and check eligibility before you start.
Last checked: 2 November 2026. This guide covers generic top-level domains such as .com, .net and .org, which follow ICANN’s Transfer Policy. Country-code domains (such as .uk or .mx) follow their own registry rules, so check those with the registry.
Before you start: know who does what
You need to know four things: who your registrar is, who hosts your DNS, where the website lives, and where email is delivered. If you are not sure, spend two minutes with Who controls your domain, DNS and website? first. Most transfer problems are someone changing the wrong provider.
Step 1: copy your DNS records
Your DNS records are the instructions that make your site and email work. Export them or take screenshots, and include every record type you use:
- A / AAAA / CNAME: where the website and subdomains point.
- MX: where email is delivered.
- TXT: SPF, DKIM and DMARC email-authentication records, and the verification codes that prove to other services you control the domain.
- SRV / CAA: used by some email, chat and certificate setups.
Also note each record’s TTL (time to live), the number of seconds other systems may cache the answer (RFC 1034 defines it). You need this if you decide to change anything later.
This copy is your safety net for the whole process. Whatever happens, you can rebuild the same records from it.
Step 2: keep DNS where it is during the move
The way to avoid downtime is to prevent two changes in flight at once. A transfer changes the registrar. Changing nameservers changes where your DNS is answered. Do them one after the other, never together:
- Transfer the domain with the current nameservers unchanged. When the transfer form offers to change nameservers, choose to keep the current ones. If your DNS is hosted by a separate company, the transfer does not touch it and visitors notice nothing.
- Check, then change DNS later if you want to. Once the transfer has completed and the ten-minute check in Step 5 passes, you can move DNS to a different host as its own, separate task. Do not change nameservers and transfer in the same week: if something breaks you will not know which change caused it.
- If your DNS is hosted by your current registrar, your records live on that registrar’s nameservers. Confirm after the transfer that the nameservers the domain now uses answer for every record in your Step 1 copy, and re-create any that are missing. The control panel that comes with a transferred domain lets you manage your DNS records, email, subdomains and website location in one place.
- If your domain uses DNSSEC, coordinate with your DNS provider before changing DNS hosts. A mismatch between the signing records at the registry and the new DNS host can make the domain fail to resolve for validating resolvers (RFC 4033 describes the system).
Step 3: check that the domain is eligible
ICANN’s Transfer Policy lists the limited reasons a registrar may or must refuse a transfer. The ones that catch people:
- Registered less than 60 days ago. The registrar may deny a transfer requested within 60 days of the domain’s creation date.
- Transferred less than 60 days ago. The same 60-day wait applies after a previous registrar transfer.
- Contact details changed recently. If the registrant name, organization or email was changed, the registrar may have applied a 60-day transfer lock. The policy lets you opt out of that lock before making the change, but the registrar does not have to offer it. (See “Rules that may change” below.)
- Domain locked. The registrar lock (the status
clientTransferProhibited) blocks transfers until you remove it. Registrars must give you a way to remove it, or remove it within five calendar days of your request. - Unpaid balance or expired. A registrar may deny a transfer for non-payment of the previous or current registration period. Renew first if the domain has lapsed.
- Dispute or legal hold. A domain in a UDRP, URS or court proceeding cannot be transferred.
The policy also says the registrar must tell you the reason when it denies a request.
Step 4: the transfer itself
Every ICANN-accredited registrar follows the same outline, though the screens differ. Our domain transfer page lists the preparation steps in the same order as below.
- Unlock the domain at your current registrar.
- Get the authorization code (also called the EPP code, auth code or transfer key). It is a per-domain code that proves you are the domain’s holder. Registrars either let you generate it yourself or must provide it within five calendar days of your request.
- Check the administrator’s contact email address. Transfer notices go to the contact email on file, not to your own inbox. If it is out of date, the notice may never reach you and the transfer can stall. (For .au domains, transfer notices go to the registrant contact’s email instead.)
- Cancel Protected or Private Registration if you have it. A privacy service can hide the contact email the transfer notices are sent to, which is the other common reason a transfer stalls.
- Start the transfer at the new registrar. Enter the domain and the code, and keep the current nameservers. To transfer to Hostinv.com, start on our domain transfer page.
- Respond to any confirmation email the registrars send. Many send one. If one arrives, answer it.
- Wait. Once the new registrar submits the request, the registry completes the transfer unless the current registrar objects within five calendar days. It can finish sooner if the current registrar approves it earlier.
What happens to the renewal date: under ICANN’s policy, a completed transfer extends the registration by one year, up to a maximum of ten years in total.
Step 5: a ten-minute check afterwards
- The website loads on both
wwwand the bare domain. - Email works in both directions (send one test from outside the domain and one to it).
- The DNS records match your inventory from Step 1.
- The SSL certificate on the site is still valid. If your certificate renewal relies on a DNS record, confirm that record is still present.
- Write down the renewal date and who is receiving the renewal notices.
- Note that the new registrar may refuse another transfer for 60 days, which is normal under the policy.
How Hostinv.com can help
Hostinv.com is an authorized reseller of domain names for business customers. Checkout and support are handled by our platform partner. When you transfer a domain to us, this is what the domain transfer page says comes with it:
- Domain locking, to guard against accidental or unwanted transfers of your domain and against others redirecting your nameservers.
- Total DNS control: manage your nameserver (DNS) records and set your email, FTP, subdomains and website location from a single control panel.
- Domain forwarding and masking, to send any domain you own to your website.
- Status alerts if something changes on the domain or suspicious activity is detected.
- Change of registration: reassign the domain (a fee applies) or update its contacts.
The page lists the same preparation steps you have just read, so you can follow this guide and our page side by side. Registration, renewal and transfer prices are shown on the page before you pay. Prices exclude applicable taxes and ICANN fees.
What can go wrong
| Symptom | Likely cause | What to do |
|---|---|---|
| New registrar says the code is invalid | Code expired, mistyped, or generated for another domain | Generate a fresh code and paste it without spaces. |
| Request refused as “transfer prohibited” | Registrar lock is still on | Remove the lock at the current registrar, then retry. |
| Request refused, domain “too new” | Within 60 days of registration or a previous transfer | Wait for the 60 days to pass. |
| Request refused after a contact change | The 60-day lock that follows a change of registrant | Ask the current registrar whether it applies and when it ends. |
| Transfer stays “pending” | Confirmation email went to an old or hidden address | Update the contact email at the current registrar and ask the new one to resend. |
| Website or email stopped | Nameservers or DNS records were changed along the way | Restore the records from your Step 1 inventory at the DNS host in use. |
| Transfer fails near expiry | The domain expired before the transfer completed | Renew at the current registrar, then restart the transfer. |
Rules that may change
ICANN’s Transfer Policy Review produced 47 recommendations, which were before ICANN’s Board at its June 2026 meeting (briefing materials). They include renaming the authorization code the “Transfer Authorization Code” and making it valid for 36 hours, replacing the 60-day waits after initial registration and after a transfer with 30-day ones, and removing the 60-day lock after a change of registrant. ICANN’s review page lists the implementation details as still to be determined, and ICANN’s published policy page (last updated 21 February 2024) still shows the 60-day rules above. Until ICANN publishes an effective date, the rules in this guide are the ones that apply.
Next step
When your domain is unlocked and you have the authorization code, start your transfer to Hostinv.com.
Disclosure
Hostinv.com is our platform partner’s introduction agent. You buy directly from the partner, under the partner’s terms. The registrar of record for domains is Wild West Domains. Hostinv.com is not a registrar and is not ICANN-accredited. The registrar of record sends domain renewal notices. Registration and renewal prices are shown on the storefront before checkout. Services are offered to business customers.
Sources
- ICANN Transfer Policy: denial reasons (3.7, 3.8), 60-day rules, lock and authorization-code obligations (section 5), five-day completion window, one-year extension (checked 2 November 2026).
- ICANN: 5 Things Every Domain Name Registrant Should Know About ICANN’s Transfer Policy: plain-language summary of who can start a transfer and what the code is (checked 2 November 2026).
- ICANN Lookup: finding the registrar and nameservers.
- GNSO: Transfer Policy Review and ICANN Board briefing materials, June 2026 (Board paper 2026.06.07.2a, Transfer Policy Recommendations): recommended changes.
- RFC 1034 (DNS and TTL) and RFC 4033 (DNSSEC).
- Hostinv.com domain transfer page: preparation steps, included features and where notices are sent (checked 2 November 2026).
