Usually, yes. A normal registrar transfer does not require you to move your website, email or DNS to the new registrar. If your current nameservers belong to your host or another DNS provider, you can normally keep using them. The main exceptions are registrars with their own DNS requirements and cases where your old registrar is also providing the DNS service.
Quick answer
Moving a domain to another registrar changes who manages the registration. It does not automatically mean changing where your DNS is hosted.
A registrar transfer and a DNS move are two different jobs. You can move a domain registration from one company to another while leaving the nameservers pointing to the same DNS provider.
That distinction matters because people often assume a registrar transfer means rebuilding DNS at the new registrar. It usually does not. With more than 300 domains to manage, I prefer to keep those jobs separate where practical: change the registrar when I need to, but leave working DNS alone unless there is a good reason to move it.
Your registrar looks after the registration. Your nameservers tell the internet where the authoritative DNS for the domain lives. They can be provided by completely different companies.
Usually, yes. If the nameservers are provided by your web host, Cloudflare or another independent DNS provider, the transfer normally leaves them pointing to the same place.
For a typical transfer between registrars, the nameserver values attached to the domain are not something you need to replace just because the registrar changes. Namecheap, for example, states that nameservers normally remain the same during and after a transfer.
That means a domain can move from Registrar A to Registrar B while the website remains on the same hosting account and the email continues using the same mail service.
If you are still deciding where to move the domain, our domain transfer price comparison can help you compare the transfer cost before starting.
Changes from the old registrar to the new one.
Can normally remain exactly the same.
Does not have to move with the domain.
Can remain unchanged if the DNS continues to point to it.
Stay with the existing DNS provider if you keep the same nameservers.
A registrar move does not, by itself, mean changing the registrant.
It is simplest when your DNS is already independent of the registrar you are leaving.
If your nameservers belong to your hosting company, a dedicated DNS provider or a service such as Cloudflare DNS, there is usually nothing to change. The new registrar simply continues publishing the existing nameserver delegation.
This is one reason I like keeping important DNS separate from the registrar where it makes sense. If I later find a better registrar, I can move the registration without turning a straightforward transfer into a hosting or email migration at the same time.
If you are new to transfers, our guide to how long a .com transfer can take explains the timing separately from the DNS side.
ICANN specifically notes that changing web-hosting provider, nameservers or a hosting IP is separate from transferring the registration between registrars.
The biggest risk is assuming that every registrar works the same way. Some registrars have DNS requirements, and old registrar-hosted nameservers can stop being useful once the domain leaves.
Cloudflare Registrar requires domains registered with it to use Cloudflare nameservers. If you are transferring a domain into Cloudflare Registrar, the domain must already be active on Cloudflare, and Cloudflare’s own documentation says you cannot use another DNS provider’s nameservers while the domain is registered there.
If Cloudflare is one of the registrars you are considering, our Cloudflare Registrar review covers the service in more detail.
This is the scenario I would check most carefully. The nameserver values may remain unchanged after the transfer, but that does not guarantee the old registrar will continue serving the DNS zone once the domain has left its platform.
For example, if the domain uses the old registrar’s default nameservers rather than nameservers supplied by a separate host or DNS provider, the DNS service may be removed after the transfer. That can take the website or email offline even though the nameserver fields themselves were never changed.
Before transferring away, check who actually operates the current nameservers and whether that DNS service continues after the domain leaves the registrar.
A nameserver change is separate from the standard 60-day transfer restriction. If you are worried about triggering a lock while preparing a move, read our guide on whether changing nameservers causes a 60-day domain lock.
Do a quick DNS check before you press transfer. It is much easier to fix a dependency on the old registrar while the domain is still there.
If your reason for moving is price or service rather than DNS, it is worth choosing the new registrar on those merits. Our guide to choosing a domain registrar covers the things I would compare before moving a portfolio.
Unless I am deliberately changing DNS provider, I would normally leave working nameservers alone during a registrar move. It reduces the number of things changing at once and makes any problem much easier to isolate.
In brief
Keep the existing nameservers if the new registrar supports them and the DNS service will continue after the transfer. The two things to check are registrar-specific requirements and whether the old registrar is currently providing the DNS zone.
