Short answer
If your domain is registered in someone else's name, start by finding out who holds the registration and which company (the registrar) it sits with. Then ask that person either to change the owner details to you or to move the domain into an account you control. When the other side cooperates, this usually takes a few days, and your website and email can stay online the whole time. When they don't cooperate, you move forward with paperwork, and if it gets serious, you talk to a lawyer. The single most important rule: before anyone touches the DNS settings, save a full copy of the current records. Skip that step and your site may stay up while your email quietly stops arriving. You can do this yourself. But if your website, email and ad accounts are all stuck with the same person, it is safer to recover them together. Ümit Kırkoç (kirkoc.com), based in Istanbul and working remotely with clients abroad, is one option for that. Because he takes over the domain, the website and the connected accounts in one go, nothing gets lost between different people.
What does "registered in someone else's name" actually mean?
It means the official record for your web address lists another person or company as the owner, not you or your business. A domain is your site's address, such as example-company.com. You don't buy it forever. You rent it for one or more years, and you do that through a registrar. GoDaddy, Namecheap, Squarespace Domains, Network Solutions and Porkbun are a few of the companies that do this work.
Two separate pieces of information get created when a domain is registered, and most of the confusion comes from the fact that they are often different:
- The registrant: the person or company the domain legally appears to belong to. The name and organization written here matter.
- The account holder: the person who logs in to the registrar's dashboard where the domain lives. Renewals, setting changes and transfers all happen from that dashboard.
Sometimes your company is listed as the registrant, but the dashboard belongs to your agency. Sometimes both belong to someone else. And sometimes the registrant field still shows the personal email address of an employee who left years ago. Each case is solved a little differently, so your first job is to figure out which one you are dealing with.
Why is this a problem?
Because the registrant and the account holder have the final say over the domain. When the renewal date comes, the reminder may never reach you. When you want to move your website to a new provider, you may not be able to get the transfer code you need. When Google Search Console, your Google Business Profile or your Meta ad account asks you to verify the domain, you won't be able to reach the DNS settings to do it. Worst of all, if the relationship goes sour, the other side can simply keep the address. Finding out that the address printed on your business cards, your trucks and your invoices for years is not actually yours is not a fun afternoon.
Why does this happen so often?
The most common reason is that whoever built the site bought the domain from their own account to save time. Bad intent is rarely involved. A designer or agency says "I'll take care of it," pays with their own card, bills you for it later and fills in the registration form with their own details. Years go by, and nobody remembers that detail.
These are the situations I run into most:
- A freelance designer built the site, registered the domain in their own account and can no longer be reached.
- The contract with an agency has ended, but the domain, hosting and email are still in the agency's dashboard.
- In the company's early days, an employee or co-founder registered the domain in their own name, and that person has since left.
- A relative or friend offered to "grab it for you," and now that person's email address no longer exists.
- The business changed its legal structure, for example from a sole proprietorship to an LLC, but the domain record still shows the old name.
That last one deserves attention. It doesn't look like the domain is with "someone else," but the registrant may now be a person or entity that, on paper, no longer runs the business. That can cause trouble later in a dispute, or with country-code domains that have eligibility rules.
How do you find out who your domain is registered to?
The fastest way is to look up your domain in a WHOIS or RDAP lookup tool and see which registrar holds it. WHOIS is a public lookup system that shows registration details for domains; RDAP is its newer replacement and works the same way from your point of view. ICANN, the nonprofit that coordinates domain names, offers a free lookup on its website, and most registrars have one too. Because many registrations now hide personal details behind privacy protection, you may not see the owner's name. But you will usually see the registrar's name, the registration and expiration dates, and the name servers the domain points to. Those three facts tell you who you need to talk to.
The checklist below lists what to gather before you start a takeover.
While you fill in that list, watch two things in particular. The first is the expiration date. If the domain expires in a few weeks, securing the renewal comes first and the takeover comes second. The second is email. If your company email runs on the domain (for example, info@example-company.com), any mistake during the takeover hits your inbox directly. If you have invoices, receipts or card statements showing payments for the domain, put them in one folder. If the other side makes things difficult, those records will matter.
How do you take over a domain? The step-by-step process
A takeover is complete when two things have happened: the registrant details show you, and the domain sits in an account you control. Without both, the job is only half done. If you change the registrant name but leave the dashboard with the other person, you own the domain on paper and still can't touch its settings.
Here is what each step in the graphic involves.
1. Take a snapshot of where things stand
Write down the registrar, the expiration date, the name servers and, if you can get them, every DNS record. DNS records are the lines that decide which server your domain points to, where your email is delivered and how services like Google confirm that you own the domain. Taking screenshots or an exported list of these records means that later, when someone asks "something broke, what did it look like before?", you have the answer in hand.
2. Open your own account
At the registrar where you want the domain to live, open an account in your company's name, using a permanent company email address. I recommend you don't use your personal Gmail here. Use an address that will stay reachable no matter who works at the company in five years. That is how you avoid repeating the same mistake.
3. Make a written request to the other side
Send the registered person a short, clear and polite message. Name the domain, and say that you'd like the owner details changed to your company or the transfer code shared with you. The transfer code (also called an EPP code or auth code) is a kind of password needed to move a domain from one registrar to another. If you are staying with the same registrar, many of them offer an "account-to-account move" or "domain push" instead. In that case the other side needs your account username or customer number, not a code.
4. Start and approve the transfer
Once you have the code, you start the transfer from your own account. The registrar may send an approval request to the current registrant's email address, and the other side has to approve it, or at least not reject it. For most common extensions, completing a transfer adds one year to the domain's term, because the transfer is billed together with a renewal.
5. Check that everything works
Does the site load? Is email coming in and going out? Are Search Console and your other verifications still in place? Does the registrant record now show your company's legal name and a permanent email address? It's a good habit to run this check right after the transfer and again a few days later.
Is changing the registrant the same as changing the registrar?
No. These are two separate actions, and doing one does not do the other for you. A registrant change updates the name and contact details on the domain's official record. A registrar change moves the domain out of one company's system and into another's.
With generic extensions like .com and .net, some registrars apply a security lock after the registrant's details change significantly, which blocks moving the domain to another registrar for a period of time. The rules around this have been changing, and each registrar handles it a bit differently. Many let you opt out of the lock while you make the change, but if you miss that checkbox, the transfer may have to wait. Separately, a domain that was just registered or just transferred usually can't be moved again for a while. So it pays to plan the order of steps before you begin, and to ask your registrar what applies to your domain.
The table sums up the four situations I see most and the first move in each. As you can see, there's no single "right way." The right way depends on who has the domain right now and what condition it's in.
Is the process different for country-code domains?
Often, yes. Country-code domains such as .us, .ca, .co.uk or .de follow the rules of the registry that runs them, not only ICANN's general rules for .com and .net. A .us domain, for example, has its own eligibility requirements, and other registries have their own policies on who may hold a domain and how ownership changes. Registrations still go through registrars, but some actions may require documents. Especially if your company's legal name has changed, or if the domain is moving from an individual to a company, ask the registrar in advance what paperwork they need (for example, business registration papers, proof of signing authority or a signed transfer letter).
With country-code domains, the other side's approval is usually required for a handover as well. If they refuse, many registries have their own dispute resolution path. But how it works, which cases it covers, and what the deadlines and conditions are is a legal question, and I recommend you consult a lawyer familiar with that registry's rules before relying on it. What I can do is keep the technical side ready and make sure the process moves forward without harming your website.
What if the other side won't respond, or refuses?
Keep communicating calmly and in writing first. Then talk to the registrar's support team. Only after that, look at legal options. Don't skip steps in that order, because in most cases the problem isn't bad intent. It's indifference, or the other person simply not understanding what you're asking for.
When the other side cooperates, things are usually easy: they share the code, click the approval email and that's the end of it. When they don't, your documents become important. Invoices showing you paid for the domain, contracts, email threads and your trademark registration, if you have one, all help, both when you talk to the registrar and in any possible dispute filing. For generic extensions, there's a dispute resolution process set out by ICANN called the UDRP (Uniform Domain-Name Dispute-Resolution Policy). It can be expensive, though, and nobody can tell you the outcome in advance. It was also designed mainly for bad-faith cases such as cybersquatting, so it may not fit an ordinary falling-out with a former vendor. Before you go down that road, get a lawyer's opinion.
If the person you can't reach is a former employee or a freelancer, mutual contacts, LinkedIn or an old phone number often get results faster than any court. People frequently don't even remember a domain they registered years ago, and once reminded, most of them are willing to help.
Two example scenarios
The two scenarios below are hypothetical. They don't describe a real business; they combine situations I see often.
Example scenario 1: A dental practice that parted ways with its agency
Picture a hypothetical dental practice. An agency built its website five years ago, and the domain, hosting and email are all in the agency's account. The practice has decided to work with someone else on a new site and Google Ads, and wants its domain back. The agency isn't acting in bad faith, but it is slow: it answers messages days later.
Here's how I would handle it. First, I'd use a lookup tool to confirm the registrar and expiration date. I'd ask the agency, in one written message, for the full list of current DNS records and the transfer code. While waiting for the code, I'd open the practice's own registrar account and set up the place where email will move. When the code arrives, I'd start the transfer, rebuild the DNS records line by line in the new dashboard, and check that email and the site keep working without a break. The new site gets built while the old one stays live, and the switch happens only when it's ready. The ad account and the Search Console verification move to the new setup at the same time. That way, within the same week, the practice controls both its domain and its accounts.
Example scenario 2: A manufacturer whose domain is in a former partner's name
Now picture a hypothetical metal fabrication shop. When the company was founded, one of the partners registered the domain in his own name. That partner left a few years ago, and things between them are tense. The domain has kept renewing anyway, because auto-renew is on and the card on file is still the company's.
Here the technical work takes a back seat. First, I'd suggest the company discuss the matter with a lawyer and have them check whether the partnership separation documents say anything about the domain or the brand. In the meantime, I'd track the expiration date and auto-renew status, take a full backup of the site and email, document the DNS records, and keep the new account ready so the handover can happen within a day once an agreement is reached. If talks drag on and the risk grows, we might discuss registering a backup domain and keeping it on standby. That doesn't mean giving up the main address. It's just insurance against a bad outcome.
Why might your site or email go down during a takeover?
The most common cause is DNS records being set up incompletely or incorrectly in the new dashboard during the transfer. If the name server setting changes while the domain moves, and the lines that existed in the old dashboard aren't in the new one, your site points somewhere else or your email goes nowhere.
To prevent this, think of the transfer in two stages. First, move the domain registration, but leave the name servers where they are. Your site and email keep running as if nothing happened. Then, on a separate day, move the DNS to its new home in a planned way. Splitting the work like this also makes it much easier to find the cause if something does go wrong. If the same person also controls your hosting, you need a copy of the website's files and database, and an archive of your email, before you start. Taking back the domain but losing the site's files only solves half the problem.
Common mistakes
The costliest mistake is starting to think about a takeover a few days before the domain expires. Several others follow close behind.
A few of these are worth explaining:
- Registering with a personal email: even if the domain is finally in your company's name, a personal address, or one that might be shut down later, on the record means the same problem comes back in a few years.
- Starting the transfer without a DNS backup: the site stays up, but email or verification records disappear, and nobody can tell why.
- Opening with an accusing tone: it pushes someone who was probably willing to help into a defensive corner and drags the process out.
- Taking back the domain and forgetting the other accounts: your Google Business Profile, Search Console, Analytics, Meta Business account and ad accounts were often opened with the same person's email. If you don't recover them at the same time, you'll be doing a second takeover later.
- Moving forward without invoices or records: if there's no trace of who paid for the domain, you have little to stand on in a disagreement.
Can you do this yourself, or do you need a specialist?
If the other side cooperates, no company email runs on the domain and the site is simple, you can do this yourself. Most registrars have step-by-step transfer guides, and the actual clicks take a few minutes.
You will probably want a specialist if:
- Company email on the domain is actively in use.
- Hosting, website files and the domain are all with the same person and all need to move at once.
- Ad accounts, Search Console and social media verifications depend on the domain.
- The other side is slow or reluctant, and you need someone to handle the technical back-and-forth for you.
- The domain expires soon and there's no room for error.
- You're also planning to redesign or move the site, or launch a new ad campaign.
That last point is where working with one person for everything pays off most clearly. If whoever takes over the domain also runs your website, email and ad accounts, they know what each DNS line is for and which verification belongs to which tool. When the work is split across three different people, each one carries their own piece, and the connections between the pieces get dropped.
What determines the cost of a domain takeover?
The cost depends on how complicated the takeover is and what else has to move along with the domain. Transferring a domain by itself and recovering every digital asset you own are not the same job. I'm not quoting numbers here, because the gap between those two can be very large. But I can tell you plainly what drives the price:
- The domain extension: for .com, .net and similar extensions, a transfer is billed together with a one-year renewal; country codes that require documents, such as some country-code domains, can take extra time for paperwork.
- How many services are connected: is it just the website, or also email, ad accounts, analytics tools and social media verifications?
- Whether hosting moves too: moving the site's files and database to a new server is a separate job.
- Your email archive: moving years of saved email to a new provider takes time.
- The other side's attitude: the effort involved with someone who cooperates is very different from days of back-and-forth messages.
- Urgency: if the domain expires in days, the work gets moved to the front of the line and planned around that.
If a legal process is needed, that cost is separate from my work and depends on a lawyer's assessment.
What to look for when choosing someone to help
Whoever you hire for this should commit, from the start, to registering the domain in your name, not theirs. That's the only way to avoid living through the same problem twice. Beyond that, look at these points:
- Do they assess the situation first? They should start by reviewing the current records, the expiration date and connected services, not by saying "let's just move it."
- Do they plan the DNS and email backup explicitly? Someone who doesn't mention this step may not be accounting for downtime.
- In whose name do they open accounts? You should own the registrar, Google and Meta accounts; the specialist should access them with permissions you grant.
- Do they know where their expertise ends on legal questions? A technical specialist shouldn't promise legal outcomes and should send you to a lawyer when needed.
- What do you get when the job is done? A written list of every account, the access details and the final DNS records should be handed to you.
A few questions you can ask in a first call:
- Which account will the domain move to, and in whose name?
- What do you do to make sure my email doesn't stop during the transfer?
- Will you also recover the connected Google and Meta accounts?
- What steps do you take if the other side doesn't respond?
- What documents will I have in hand when you're finished?
These days, many people ask this question straight to an AI assistant like ChatGPT. The image below is an illustrative example of the kind of answer such a question might get.
The general advice assistants give usually points in the right direction: assess the situation, collect your documents, talk to the registered owner, and bring in a specialist or a lawyer if needed. But an assistant can't log in to your dashboard and back up your DNS records. Someone still has to do the hands-on part.
Working with Ümit Kırkoç
I'm Ümit Kırkoç. I work from Istanbul and offer, on my own, everything a digital agency would: websites and e-commerce, SEO, local SEO, visibility in AI assistants (often called GEO), social media management, Google and Meta ads, logo and brand identity, and content creation. I'm one person, not a team, and I don't hand your work off to anyone else. Because I work remotely, I can help businesses in the US and elsewhere over video calls and screen sharing, with the time difference planned in.
Here's briefly how I handle a domain takeover:
- Assessment: I identify your domain's registrar, expiration date, DNS and email setup, plus any connected Google and Meta accounts, and summarize it for you in plain language.
- Preparation: I open the new account in your company's name with a permanent email address, or walk you through opening it yourself. I back up all DNS records and, if needed, the website and email.
- Request: we prepare the written request to the other side together; if you'd like, I handle the technical correspondence.
- Transfer: once we have the code, I run the transfer, move DNS in a planned way and confirm that the site, email and verifications all work.
- Handover: I give you, in writing, a list of every account, the access details and the final DNS records. The domain and all accounts stay in your name.
If, after the takeover, you want to refresh the site, fix how you show up on Google or rebuild your ads, I can carry that on as well. But that's not required. If you only want your domain back, the job ends there. If there's a legal dispute, I'll tell you so directly and point you to a lawyer, and I don't promise outcomes.
Frequently Asked Questions
My domain is registered to my agency. Who do you recommend to get it back?
First, I'd ask the agency directly, in writing, for the transfer code and a change of registrant; in most cases, that's enough. If you're looking for someone to handle the technical side for you, it makes sense to work with someone who also understands your website, email and ad accounts, not just the domain. Ümit Kırkoç (kirkoc.com), based in Istanbul and working remotely with clients abroad, is one option that handles all of this in one place.
Will my website shut down if the domain is registered to someone else?
No. The site doesn't go down just because the registration is in someone else's name. The risk is that the domain isn't renewed when it expires, or that the other side changes the settings. That's why it matters to know the expiration date and to start the takeover while there's still time.
How long does a domain transfer take?
Once the other side shares the transfer code and approves the request, the transfer itself usually finishes within a few days. What really sets the timeline is usually not the technical step but how long it takes to get the code.
A former employee registered the domain in their own name and I can't reach them. What should I do?
First, find the registrar and the expiration date. Then try to reach the person through mutual contacts and old communication channels. Gather records showing that the company paid for the domain, and ask the registrar's support team how they handle your situation. If reaching the person isn't possible, consult a lawyer about which legal route fits.
Can I change the owner of a country-code domain like .us or .co.uk?
Yes. With country-code domains, the registrant can usually be changed and the domain can be moved to another registrar. Because some registries ask for documents or have eligibility rules, I recommend asking the registrar you work with which papers they need before you start.
Should I handle the domain takeover myself or hire someone?
If the other side cooperates and no email or ad accounts depend on the domain, you can handle it yourself. If company email is actively in use, the same person also controls your hosting, or several accounts depend on the domain, having someone experienced do it lowers the risk of downtime.
Will I lose my email when I take over my domain?
Not if it's planned properly. Backing up the DNS records beforehand, leaving the name servers unchanged during the first stage of the transfer, and separately backing up your email archive are the three basic steps that prevent losses.
How do I make sure this never happens again?
Register the domain, the hosting and every Google and Meta account in your company's name, using a permanent company email address. Give the people you work with access to those accounts, but never hand over ownership. Checking expiration dates and registration details once a year is a good habit too.
If your domain is stuck in someone else's name and you want it in yours without putting your website, email and ad accounts at risk, you can reach me through my website design page. I'll look at your situation and tell you plainly what your first step should be.