My Web Designer Owns My Domain: How to Get Your Website Back (2026)

Most people who call us about this say the same sentence: my web designer owns my website. In practice that is three separate things, and you may own some of them and not others. There is the domain, which is the name people type. There is the hosting, which is the server the site lives on. And there are the files and the content, which is the design, the code, the words and the photos. Each one can be held by a different party and each one is recovered differently.

The reason this matters is that the panic usually attaches to the wrong thing. Losing hosting is an inconvenience, because a site can be moved to new hosting in an afternoon. Losing the files is a cost, because the site can be rebuilt. Losing the domain is the one that actually hurts, because the domain is where your reviews, your Google Business Profile, your printed materials, and every link anyone has ever made to you all point. So before you do anything else, find out who holds the domain.

We see this most often with businesses whose first site was built five or ten years ago by a friend, a freelancer, or a small shop that has since stopped answering. A Costa Mesa restaurant we spoke to last year had been paying a designer monthly for years without realising the domain sat in that designer's personal GoDaddy account. Nothing was malicious. Nobody had thought about it. That is the usual story.

Go to ICANN's registration data lookup, type your domain, and look at two fields: the registrar, which is the company the domain is registered through, and the registrant, which is the person or organisation the registrar treats as the holder. If the registrant is you or your business, you own the domain regardless of who built the site or who logs in to manage it. If the registrant is your designer, their agency, or a name you do not recognise, keep reading.

Two things can muddy the result. Many domains use a privacy service, so the registrant shows as a proxy company rather than a real name. That does not mean the designer owns it, only that the details are hidden, and the registrar can tell you whose account the domain lives in if you can prove you are involved. The second is that the lookup shows the registrant, not who has the login. Plenty of business owners are the registrant of record on a domain sitting in an account they have never seen. That is a much easier problem, and we cover it below.

Write down the registrar, the registrant, the expiry date, and the name servers. The expiry date in particular tells you how urgent this is. A domain that lapses gets a short grace period and then goes to auction, and a business name with years of history behind it will be bought by somebody within hours.

The registrant of record is who the registrar recognises as the holder of the domain. If that is your designer, then as far as the registrar is concerned it is their domain, and no amount of explaining that you paid for it will get a support agent to hand it over. What decides it is the agreement between you and the designer. If your contract says the domain is yours, or that it transfers to you on request or at the end of the engagement, you have a clear path. If there is no contract, or it is silent on the domain, you are relying on goodwill.

So the first move is not a lawyer and not the registrar. It is a plain, polite, written request to the designer asking them to transfer the domain to an account in your name, with a date. Most of these situations resolve here, because the designer never wanted the domain, they registered it as a convenience during the build and forgot. Give them the exact steps: unlock the domain, generate the transfer authorisation code, and send it to you, or simply change the registrant to you at the same registrar, which is faster.

ICANN's own explanation of what a change of registrant involves is worth reading before you send that message, because it tells you what the designer will be asked to confirm and lets you pre-empt the questions.

This is the part that catches people out. Under ICANN's transfer policy, a domain cannot be moved to a different registrar within 60 days of its initial registration or within 60 days of a previous transfer. Registrars have also been applying a third lock of 60 days after a change of registrant, though many let you opt out of that one before the change is made, and ICANN has voted to retire it. Until your registrar actually drops it, plan as if it applies.

In practice this means the order of operations matters. If the designer changes the registrant to you and then you immediately try to transfer the domain to your own registrar, you may find it locked for two months. The cleaner sequence is usually to transfer the domain to a registrar account you control first, using the authorisation code, and have the registrant details updated as part of that move. Or, if you are staying at the same registrar, ask the designer to push the domain into your account there, which sidesteps the inter-registrar lock entirely.

The other reason to move quickly rather than perfectly is that a relationship that is cordial today may not be cordial in sixty days. If the designer is willing right now, take whichever path completes fastest and tidy up the registrar choice later.

Once the domain is safe, turn to the site itself, and here it depends entirely on what it was built on. If the site is on a platform like Wix or Squarespace, there is no set of files to hand over. The site exists inside that platform's account and cannot be exported as a working website. What you can recover is the content, meaning the words and the images, and the only practical route to keeping the design is being added to the account as an owner. We wrote about that specific trap in our piece on outgrowing Wix and Squarespace.

If the site is WordPress, ask for a full export and a copy of the database, or for admin access to the hosting so you can take it yourself. If it is custom code, ask for the repository or a zip of the source. In every case, ask for the images at original resolution, because those are the thing most often lost and most annoying to recreate.

One honest caveat on the content. The words and photos you supplied are yours. The design and the code are a different question, and in the United States whether they belong to you or to the person who made them depends on what your agreement says, with the default in the absence of a written assignment often favouring the creator. If you are about to have an argument about it, that is the point to spend an hour with a lawyer rather than a forum.

Escalate in order, and keep everything in writing. Start with a formal request that references your contract if you have one, gives a deadline, and says what you will do next. If the designer has simply gone quiet, try every channel you have, including the business address on their invoices, because the aim at this stage is a response, not a fight.

If that fails, contact the registrar with your evidence: invoices showing you paid for the domain, the contract, any emails where the designer acknowledged it was yours. Registrars will not adjudicate a contract dispute, but they do act on evidence of fraud and they will tell you what their process is. ICANN's dispute mechanisms are mostly designed for disputes between registrars or for trademark cases involving bad faith, so they are rarely the right tool for an ordinary falling out with a freelancer.

The last resort is legal, and for a small business that usually means a demand letter and, if needed, small claims court, where the amounts involved are generally within limits. Before you get there, do the arithmetic honestly. If the domain is a generic name with little history, it can be cheaper to register a new one and rebuild than to fight. If it is the name every customer knows you by, it is worth the fight, and our redesign checklist lays out what a rebuild involves if you end up going that way.

If you do end up on a new domain, understand what you are giving up. Every link to the old address, every citation in a directory, and the address on your Google Business Profile all point somewhere you no longer control. Google treats the new domain as a new site. You can recover a good part of the standing with proper redirects, but only if you still control the old domain long enough to set them up, which is exactly the thing in dispute.

That is why the order in this article is the order it is. Domain first, always. Files second. Rankings are a consequence of the first two and cannot be protected on their own. If you find yourself rebuilding on a new address, the work is the same local work that any new site needs, and our local SEO step by step guide is the place to start once the site is live.

Update the Google Business Profile, every directory listing you can find, your social profiles, and your email signature on the same day the new site goes live. The businesses that lose the most in a domain move are the ones that leave the old address on their profile for six months.

The fix is simple and almost nobody does it. Register the domain yourself, in an account in your name, with your email address and your card on file. Then give your designer whatever technical access they need, which is usually the ability to change name servers or DNS records and nothing more. A good designer will not object. Many will insist on it, because it protects them too.

Do the same with hosting. The hosting account should be yours, with the designer added as a user. Our guide to what hosting actually costs covers why paying for it directly rather than through a designer's bundle is usually both cheaper and safer. And get one sentence in writing before the build starts: the domain, the hosting account, the files and the content belong to the client. That sentence is worth more than the rest of the contract combined.

Finally, ask for the files at launch, not later. A zip of the site and the images on the day it goes live, kept somewhere you control, means that whatever happens to the relationship, the work you paid for is already in your hands.

This is the reason ownership is on every one of our trade website pages and priced on the page rather than discussed later. The domain is registered in your name from the start. The files are delivered at launch. There is no platform you have to keep paying to keep the site online, and no clause that hands anything back to us if you stop working with us. It is not a selling point so much as the absence of a trap, and once you have been caught in the trap it is the first thing you check.

If you are looking at a WHOIS result right now and it does not say your name, the fastest thing to do is send us the domain. We will tell you who the registrar is, what the lock situation looks like, and what the sequence should be, within 24 hours, whether or not you ever hire us. Getting the domain back is the urgent part. Deciding what to do with it afterwards can wait.