Transferring a domain to SEOHost.net changes who bills you for the name and which dashboard manages it. It does not change what the name points at. Unlock the domain at your current registrar, copy the authorisation code, and start the transfer below: the site stays up the whole way through.
Enter a domain you already own. Transfer and renewal rates for its extension are shown in the order form.
People put transfers off because they picture a migration. It is not one. A registrar transfer changes a single record at the registry, who is responsible for the name, and deliberately leaves everything technical exactly as it was.
Know the domain already? Open the transfer form and enter it there: you will need the authorisation code from your current registrar in the same step.
Five steps. Four are yours; the last belongs to the registry and runs on its own schedule. Nothing is irreversible until the registry completes it, and a transfer that fails simply leaves the domain where it is.
At your current registrar
EPP code, copied out
Transfer form + code
Sent to the registrant
Out of everyone's hands but the registry's
You: sign in to the registrar holding the name, open the domain, switch off the toggle labelled "registrar lock", "transfer lock" or "theft protection". Why: the lock sets clientTransferProhibited at the registry, and while it is there the request is refused outright. Any WHOIS lookup confirms it has gone.
You: on the same page, ask for the authorisation code: EPP code, auth code, transfer key. Some registrars show it on screen, others email it to the registrant address. Copy it exactly, including case. Why: it is the registry's proof the request came from the holder. Codes expire quickly, so use it the same day.
You: open the transfer form, type the full domain, paste the code, complete the order. Why: this is where the real checks happen: the form asks the registry whether the name is transferable now, and shows the transfer and renewal rates for that extension. If a precondition is unmet you find out here, before anything is charged.
You: watch the registrant address and click the approval link when it arrives, then check your old registrar's panel: many have an "approve" or "accelerate transfer" button that releases the name instead of waiting out the policy window. Why: this is the most common reason a transfer stalls, and WHOIS privacy is the most common reason the email never arrives.
You: nothing. Why it still matters: we are not going to give you a number here. Under the ICANN Transfer Policy the losing registrar gets a window of up to five calendar days to respond before a generic-extension transfer proceeds; country-code registries write their own rules entirely. Some registrars release a name quickly once you approve on their side, others use every hour they are allowed. That window is registry policy, not a service level any host can shorten, so start transfers well before a renewal date, not on top of one. When it completes, the domain appears in your account with its nameservers and DNS records exactly as they were.
These are registry and ICANN rules rather than ours, which is the useful part: they apply wherever you transfer to, they are all checkable in a WHOIS lookup or your current registrar's panel, and each is a fixable reason a transfer gets refused.
The ICANN Transfer Policy locks a generic domain for 60 days after it is first registered, and for another 60 days after any previous registrar transfer. No host can waive it. Check the creation date and last transfer date in a WHOIS lookup before you plan the move.
The lock exists to stop a domain being moved by someone who should not be moving it, so it does its job by blocking you too until you switch it off. A WHOIS lookup showing clientTransferProhibited means it is still on. Turn it off immediately before you start, not weeks ahead.
The confirmation email goes to the registrant or administrative address in the record, whatever that record says today. If WHOIS privacy is masking it, switch privacy off for the duration of the transfer, or confirm the privacy service forwards mail to you, and switch it back on afterwards. An address at a company you left is the version of this that ends in a support ticket.
Updating the registrant name or email can trigger its own 60-day lock unless the change was made with that lock opted out. Separately, a name past its expiry date or in the registry redemption period must be renewed or redeemed at the current registrar first: a transfer cannot rescue a lapsed domain.
Country-code extensions such as .uk, .de and .eu are the exception to almost all of this: their registries set their own mechanism, lock behaviour and sometimes their own paperwork, and several do not use authorisation codes at all. If that is what you are moving, ask us first with the domain name.
The three things people most expect to lose in a transfer are the three things a transfer is specifically designed not to touch.
A registrar transfer does not touch your hosting, files, databases or certificates. Nothing is copied anywhere and no server changes hands. Visitors carry on hitting the same site at the same address throughout, because as far as the internet is concerned nothing about the name's resolution has changed.
The nameservers recorded against the domain move across as they are, so whichever DNS provider answers today carries on answering. A records, MX records and TXT verification stay put and email keeps flowing. Change nameservers as a separate step after the transfer completes, never in the middle of one.
For most generic extensions the registry adds a year to the term as part of the transfer rather than restarting the clock, so the remaining months stack rather than disappear. What that year costs sits in the order form beside the renewal rate for the extension, because transfer pricing is set per TLD and belongs on a live price list, not on a page like this one.
On one site, keeping the name at one company and the hosting at another costs you a second login. On thirty, it costs a second renewal calendar, a second support queue and a DNS layer nobody owns end to end, which is exactly where multi-site networks quietly break.
Once the name is in this account it sits beside the addresses it should resolve to. Assigning one of your dedicated IPs is a field in the IP Manager, not an export from one panel and a re-typed import into another. What is left to wait on is resolver caching, a property of the internet rather than of us: drop the TTL a day early and the switch lands quickly.
Class C dedicated IPs from $1.70/IP/mo on a 3-year term →Own ns1 and ns2 per domain, included rather than sold on. This is the quiet failure mode of a diverse-IP network: fifty sites on fifty distinct addresses, all pointed at one shared nameserver pair anyone can look up in a single public record. A transferred name gets its own pair the day it arrives.
Wider separation · Class B from $2.40/IP/mo on a 3-year term →Domains, hosting, IP allocations, SSL and invoices in one account. Every name shows its own expiry date, auto-renew is a switch, and reminders go out before the date rather than after it. Sites are lost to an unnoticed renewal at a registrar nobody logged into for a year far more often than to anything algorithmic.
Domain registration →Every domain on a hosting account here gets a certificate issued without a purchase, a CSR or a copy-paste. If the name you are moving is still on plain HTTP, or on a certificate you renew by hand, that job disappears at the same time the registration does.
SSL certificates →One domain is a form. Forty is a project, and what makes it a project is not the typing, but that each name needs its own lock switched off and its own authorisation code before anything else can happen.
Work through your current registrar once, unlocking every name and collecting every authorisation code into a list, and only then come here. The other way round means starting forty transfers that all sit waiting on preconditions you have not met, then chasing forty confirmation emails to work out which is which. Use the scratchpad beside this to build the list as you go, and if the batch is large or spread across several registrars, open a ticket and we will walk it with you.
This box is a scratchpad, not a live checker. It counts what you have typed so you know the size of the batch, and nothing in it is sent anywhere. Transferability, the authorisation code for each name and the rates for each extension are all handled in the order form.
Straight answers about auth codes, timing, downtime and what happens when a transfer is refused. Still stuck? Open a ticket, we answer 24/7/365.
A transferred domain is half the job. The other half is what it resolves to, and whether two of your sites resolve to the same neighbourhood.
Every site on its own dedicated IP in its own Class C block, drawn from 1,300+ distinct blocks across 800 American and 500 European addresses, with private ns1/ns2 on each domain.
From $1.70/IP/mo on a 3-year term · explore SEO hosting USA →First-octet diversity, the widest separation we sell. Only 255 Class A blocks exist in the world and we hold 10% of them, which is why order sizes are small and the addresses are worth reserving early.
From $3.40/IP/mo on a 3-year term · explore Class A USA →A certificate is issued for each domain on a hosting account here without a purchase or a CSR, so a name that arrives on plain HTTP does not stay there, and a hand-renewed certificate stops being a diary entry.
Explore SSL certificates →Unlock it, copy the authorisation code, start the transfer: your DNS keeps answering throughout, your remaining registration time comes with you, and the name lands in the same account as your dedicated IPs, your SSL and a 30-day money-back guarantee on the hosting beside it.
Rather talk to a person?
Answers come from our published material. Never send passwords or card details.
What this site keeps
One item keeps pages working and remembers the choice you make here. A second one, entirely optional, tallies which guides get opened at all, so we can retire the ones nobody reaches. Nothing here follows you off this site.