Who owns your website? If you paid a designer or agency to build it, the honest answer is often “not you.” The domain name may be registered in the designer’s name, the hosting account may be on their login, the CMS admin may be locked to them, and the code, design and copy may legally belong to them too. None of that makes them a scammer; most of the time it’s just a contract that never said who owns what. But it does mean you’re dependent on someone else for your own online presence, and that’s a fixable problem. This guide is the audit and the transfer manual: find out what you actually own, then move each asset into your name.
This article is the “already in it” companion to our hiring series. If you’re still choosing a designer, our web designer red flags guide covers what to watch for before you sign; if you’re preparing to ask about ownership, our questions to ask a web designer covers the exact questions, including who should own the domain. This article covers the middle case: you have a website, and you want to know who owns it and how to take it back.
Key Takeaways
- Website ownership is not one thing. It’s the domain name, the hosting account, the CMS login, and the copyright in the code, design and copy, each of which can be owned by different people.
- Paying for a website does not make you its owner. IP Australia’s rule is that IP created by a contractor belongs to the contractor unless the contract says otherwise.
- The domain is the most important asset, and it’s transferable. Under auDA rules you can move a .com.au domain to your name, or to a different registrar, with no registrar-transfer fee.
- Start with an audit: log into the domain registrar account, check the hosting bill, and try the CMS admin login. That tells you exactly which assets you hold and which you don’t.
- Transfers can be blocked if a domain is under dispute, so if a designer won’t cooperate, the path is through the official ownership and recovery processes, not a fight.
First, Find Out What You Actually Own
You almost certainly don’t own everything, even if you paid for it. Run this audit to find out which assets are actually in your name; it takes about twenty minutes and uses only the accounts you already have.
| Asset | What to check | How |
|---|---|---|
| Domain name | Who is the registrant on the .com.au licence? | Log into the registrar account, or check WHOIS for the registrant name |
| Hosting account | Whose name is the hosting bill and control panel in? | Check the hosting invoice and the account holder on the control panel |
| CMS login | Can you log in as an administrator, or only as a limited user? | Try logging into the CMS (WordPress, Shopify, etc.) with your own credentials |
| Dependent accounts | Who controls Analytics, Search Console, Google Business Profile, ecommerce and payment accounts? | Check the email and login on each account’s settings |
Be honest with yourself about the results. Most “locked out” situations aren’t malice; the designer registered the domain in their name for convenience, paid the hosting bill on their card, and never transferred anything because the contract didn’t require it. The audit tells you what to work on, not who to blame.
Who Owns Your Website’s IP in Australia?
The most misunderstood part of ownership is copyright. In Australia, the default rule is clear: IP created by a contractor belongs to the contractor, unless the contract says otherwise (IP Australia, “Who owns intellectual property?”, retrieved 2026-08-28). That means the code, the design, the written content and the images a web designer produces for you are theirs by default, not yours, until the agreement transfers them to you.
This is why “I paid for it, so it’s mine” doesn’t hold up. Paying for a website gets you the finished site running on your domain, but the underlying IP stays with the creator unless the contract says it transfers. If you have a written contract, look for the clause that assigns intellectual property to you. If it’s not there, that’s the gap, and it’s a gap you can close with a written IP transfer agreement, even after the fact, if the designer agrees.
This matters for the same reason the domain matters: without ownership of the code and design, you can’t cleanly take the website elsewhere, rebuild it without infringing, or sell it later. Our web design contract guide explains how an ownership clause should read before you sign. This article is about what to do when you already have a site and the ownership wasn’t written down.
The Domain Is the Crown Jewel
Of all the assets, the domain name matters most. Your domain is the one thing that’s genuinely hard to replace. If you lose the hosting you can rebuild the site, and if you lose the CMS you can recover the content, but your domain name is your permanent address on the internet, and the person named as the registrant controls it.
For a .com.au domain, ownership is governed by auDA, the administrator of the .au namespace. The registrant named on the licence is the legal holder of that domain name, and they must meet the eligibility requirements for .au domains. If your designer registered the domain in their name, they are the registrant, which is exactly why the domain is the asset to prioritise when you want to take control back (auDA: transfer a .au domain name, retrieved 2026-08-28).
If you don’t know who the registrant is, find out now. Log into the account at the domain registrar, or use a WHOIS lookup, and check the registrant name against your own. If it matches your business, you’re in the strong position; if it doesn’t, the next section is for you.
How to Transfer the Domain Back to You
You don’t negotiate domain ownership from scratch. auDA sets out two distinct transfers, and the first decision is which one applies to your situation (auDA: transfer a .au domain name, retrieved 2026-08-28):
- Transferring the registrant (changing who owns it). This is what you want when the domain is in the designer’s name and you want it in yours. Contact the current domain provider and start the registrant change. The new registrant must enter into a new licence agreement, meet all the eligibility requirements, and pay the licence fee.
- Transferring to a different registrar (changing the provider). This is when you keep the same owner but move the domain to a registrar you control. You need the transfer authorisation code, sometimes called the domain name password or EPP authInfo code, which you can get from the current registrar or through the .au domain password recovery tool. Provide it to the new registrar to start the transfer.
Two details make this easier than most people expect. First, there’s no fee for transferring a .au domain licence between registrars. Second, the registrant change and the registrar change are separate: you can move the domain to a registrar you trust and change the registrant to your name in the same process or at different times.
The one thing that blocks a transfer is a dispute. auDA won’t transfer a domain that’s subject to a complaint to the Licence Review Panel, under internal review, or under the .au Dispute Resolution Policy (auDRP) proceedings. So if a designer is refusing to cooperate, the answer isn’t to fight them directly; it’s to work through the official process, which is designed to resolve exactly this kind of dispute fairly.
Hosting, CMS & the Accounts Your Site Depends On
Once the domain is under your control, the other assets follow a similar pattern, with each one having its own ownership and its own transfer path, and none of them are automatic.
- Hosting. The hosting account is tied to whoever pays the bill and holds the control panel login. To move it to your name, the current account holder (usually the designer) needs to transfer the account or give you access, and you take over the billing. If they won’t, the hosting provider has its own account recovery process.
- CMS. Logging into your CMS as an administrator is the minimum; that gives you the content and the ability to manage the site. If you’re only a limited user, the admin needs to promote you, or you’ll need to regain control through the CMS provider’s recovery process.
- Dependent accounts. Google Analytics, Google Search Console, your Google Business Profile, and any ecommerce or payment accounts each have their own ownership settings. Check who controls them, and move them into your name using each platform’s account access and ownership transfer flows.
This is the part that takes patience, because every asset needs someone to action the transfer, and for hosting, CMS and dependent accounts, that usually means the designer cooperating. The domain is the piece you can force through the official auDA process; the rest mostly require goodwill, a contract that says you own them, or a platform’s recovery flow.
What If the Designer Won’t Cooperate?
If the designer won’t hand anything over, don’t panic and don’t escalate into a fight. There’s a defined order to follow.
- Go through official ownership and recovery processes first. For the domain, use the auDA transfer process and understand that a dispute blocks the transfer, so if there’s a genuine disagreement over ownership, it gets resolved through auDA’s dispute mechanisms, not by one party seizing control. For hosting, CMS and accounts, use each platform’s account recovery and ownership transfer flows.
- Keep evidence. Save your contract, emails, invoices and any messages that show what was agreed about ownership and access. These matter if you need to escalate.
- Know when it’s a scam, not a dispute. Refusing to cooperate is different from disappearing with your money. If the company also shows the hallmarks of a fake operation (no ABN, a virtual address, a brand-new domain, reviews appearing in a burst), then you may be dealing with a scam rather than a contract gap. Our guide to checking if a web design company is legitimate covers that investigation separately.
Be realistic about timelines. Recovering assets from an uncooperative party can take weeks and follow formal processes, and a court order is the slowest path of all. The better strategy is almost always prevention: get the ownership terms in writing before you sign, which is what the next section covers.
What “Owning Your Website” Means for Future Projects
Everything in this article becomes easier if you never have to do it after the fact. For your next project, or to clean up your current one, make ownership part of the agreement from the start.
- Write down who owns each asset. The domain, the hosting, the CMS, the code, the design, the content and the dependent accounts should each have a named owner in the contract, and for a client project the answer should normally be you.
- Include the transfer obligation. The contract should say the designer must transfer the domain registrant, hosting, CMS admin and dependent accounts to you at the end of the project, and on request if you part ways.
- Confirm it before paying. Our questions to ask a web designer includes exactly which ownership questions to ask, and our web design contract guide covers how the clause should read. Use both before you sign.
This isn’t about distrusting web designers. Most of us happily put ownership in the client’s name from day one. It’s about making the default explicit, so neither side discovers a problem years later when the relationship changes.
When Ownership Is Really a Scam
One honest boundary: holding a client’s assets is not, by itself, a scam. Most of the time it’s a contract that never specified ownership, a designer who registered the domain for convenience, or an agency that simply never did the handover. Calling that a scam would be wrong, and it would send people down the wrong path.
What makes it a scam is the combination: a designer who takes your money, delivers nothing, won’t respond, and was never a real registered business to begin with. If you’re in that situation, the transfer manual above doesn’t apply the same way, because there’s no cooperative counterparty and possibly no real company. Run the company-verification checks first, and if the signs point to a fake operation, report it to Scamwatch rather than trying to negotiate a handover. Our guide to verifying a web design company walks through that investigation step by step.
Frequently Asked Questions
Who owns my website after I pay for it?
Not automatically you. In Australia, IP created by a contractor belongs to the contractor unless the contract says otherwise, so the code, design and content stay with the designer unless the agreement transfers them. The domain name is separate: the registrant named on the .com.au licence owns it. Audit each asset to see who actually holds it.
Does my web designer own my domain?
It depends on who is registered as the registrant. If the designer registered the domain in their name, they are the legal holder. The good news is that a .com.au domain can be transferred to you through auDA’s official process: the new registrant enters a new licence agreement, meets the eligibility requirements, and pays the licence fee.
How do I transfer my domain from my web designer?
Two routes under auDA: to change the owner (registrant), contact the current domain provider and start a registrant change to your name. To change the registrar (provider) while keeping the owner, get the EPP authInfo code from the current registrar (or the .au password recovery tool) and provide it to the new registrar. There’s no fee for a registrar transfer of a .au licence.
What if my web designer won’t give me access?
Work through the official processes first: auDA’s domain transfer and each platform’s account recovery flows for hosting, CMS and dependent accounts. Keep evidence of what was agreed. If the company also shows scam hallmarks (no ABN, virtual address, new domain), it may be a scam rather than a contract dispute, so check that separately.
Can I get my website if there’s no contract?
Copyright defaults to the contractor without a contract, so you’d need the designer to agree to a written IP transfer. The domain is more workable: if it’s registered to you, you hold it; if it’s not, use auDA’s transfer process. This is exactly why a written contract with an ownership clause matters before work starts.
Conclusion: Audit, Transfer, Prevent
Who owns your website is a question with a concrete answer for each asset, and a concrete path to fix it. Start with the audit to see who actually holds your domain, hosting, CMS and accounts. Transfer the domain through auDA’s official process, move the other assets through each platform’s ownership flows, and treat an uncooperative counterparty as a process problem, not a fight. Then make sure the next project puts ownership in writing from day one. If you’re not sure where your website stands, tell us what you have and we’ll walk you through what it takes to put it in your name. When the ownership terms are set, our small business website development service is built on the same transparency we’d expect from anyone we hired.
