Direct answer
Find out three separate things before anything else: whose name the domain is registered in, which company you pay to keep it registered, and which service answers for its DNS records. They are often three different parties, and a developer or agency may hold any of them. Once you know, the aim is that your business is the registrant, a login you control sits at the registrar, and every DNS record is written down before anyone changes it. Rules for transfers, locks and authorisation codes differ by registrar and by domain ending, so the registrar's own current help pages are the authority. This page is a checklist of decisions and records, not a legal determination of who owns a domain and not a promise that any change will be free of interruption.
Registrant versus registrar versus DNS host
These three words describe different roles, and mixing them up is how people believe they own something they only have a login for.
- Registrant: the person or company the domain is registered to. This is the name on the registration record.
- Registrar: the company where the registration is kept and renewed. It is where you log in to manage the domain.
- DNS host: the service that holds the records saying where the website, email and other services for the domain live. It can be the registrar or a completely different provider.
How to find out who holds each one
Start with what you can see without anyone's help. A public lookup service for domain registration will usually show the registrar and may show registrant details, although some records are masked and what is shown depends on the domain ending and on privacy settings, so treat it as a clue rather than proof. A public DNS lookup shows which name servers answer for the domain, which points to the DNS host.
Then confirm from the inside: ask who can log in to the registrar account, whose email address is on that account, and whose card pays the renewal. The person who set the domain up is not always the person named on it, and the name on the account is not always the name on the registration. Write down what you learn for each of the three roles.
If the developer holds it
When the domain sits in a developer's or agency's account, there are usually three routes, and the right one is a decision about how much you need to change:
- Invite you as an administrator on their account: quick, but the account and the registration stay theirs, so it is a stopgap rather than ownership.
- Change the registrant to your business inside the same registrar: the domain stays where it is, and the registration record now names you.
- Move the domain to a registrar account you own: the registration and the account both become yours, but it goes through the registrar's transfer process.
What to check with the registrar before choosing
Transfer locks, authorisation codes, confirmation emails and waiting periods can apply, and they differ between registrars and between domain endings. Do not assume them from another domain you have moved. Read the current help pages of both the registrar that holds the domain and, if you are moving, the one that will receive it, and ask their support when something is unclear. If a transfer needs an email confirmed by the current registrant contact, make sure that mailbox is reachable before you start.
DNS record inventory before any change
Export or copy every DNS record before you touch anything, including the ones nobody remembers adding. Group them so you can see what each one is for:
- Website: the records that point the bare domain and the www address to the host
- Email: records that route incoming mail and the ones that identify who may send for the domain
- Verification records: text entries added to prove ownership to analytics, search, email and other third-party tools
- Third-party services: subdomains for a help desk, a booking tool, an app or a staging site
Email records
Email is the part people forget and then miss when it stops. Records for receiving mail, for sending from your domain through a newsletter or CRM tool, and for showing that a sender is allowed to use your domain all live in DNS. If you move DNS to a new host, recreate every one of them first and compare the two lists line by line. Ask whoever runs your email which records they depend on rather than guessing from the names.
Renewal and expiry owner
A domain that lapses takes the website and email with it, so name a person responsible for renewal and put the payment method under your control. Use a role mailbox, such as an address shared by two named people, for billing and renewal notices so that the reminder does not vanish when one person leaves. Check whether automatic renewal is available and switched on at your registrar, and note in the register who checks it and how often.
Two-step sign-in and recovery contact
Turn on two-step sign-in for the registrar account and record who holds the second factor. Make sure the recovery contact is a business mailbox rather than a personal address. This is an operational safeguard to reduce the chance of being locked out; it is not a security or compliance claim, and the options available depend on the registrar.
What to record afterwards
Add the domain to your third-party account register, described in who owns the code and accounts after a custom build. Record the registrant name, registrar, the account owner and administrators, the DNS host, the renewal contact and payment method, the two-step sign-in holder, and the date of the last review. Keep the exported DNS record list with it.
Where LATYNEX fits
LATYNEX can help you build the inventory, decide which of the routes above suits your situation, and set up the hosting and deployment side so the site keeps pointing at the right place once you control the domain. That work sits inside development infrastructure setup.
LATYNEX is not the right fit when the blocker is a registrar-side matter: a locked transfer, a lost account or a dispute about the registration is a registrar support ticket, and we cannot act on your behalf inside their systems. It is also not the right fit for a question about who legally owns the name. That is for a lawyer, and nothing here determines it.
Questions
Does the person who bought the domain own it?+
Not necessarily. Ownership on paper follows the registrant on the registration record, and control follows the registrar login. Both should be your business. For a dispute, take legal advice.
Can I move a domain without my website or email going down?+
This page cannot promise that. What lowers the risk is a complete DNS record inventory, matching records recreated before any switch, and reading the registrar's current transfer guidance.
What is the difference between changing the registrant and transferring the domain?+
Changing the registrant updates whose name is on the registration, usually at the same registrar. A transfer moves the domain to a different registrar. Which is available, and how, depends on the registrars and the domain ending.
Why does DNS matter if I already control the registrar login?+
The DNS host may be a different service still run by the developer. If so, they can change where your site and email point even though the registration is yours.
Who should be the billing contact?+
A role mailbox that at least two people can read, with a payment method owned by the business, so renewal notices survive staff changes.