This is one of the most common and least discussed problems in the Australian web industry. It usually surfaces at the worst moment: the agency raises prices, disappears, or you simply want to move — and you discover the domain was registered to them, the hosting login was never yours, and the site was built on a proprietary platform that cannot be exported.
The five-minute ownership audit
Run through these checks now, while your relationship with your provider is fine. Each takes about a minute:
- Domain: look up your domain’s WHOIS record (auDA’s lookup for .au, or any WHOIS tool for .com). The registrant should be your business name and ABN — not your agency’s. Also confirm you have the login to the registrar account (e.g. VentraIP, Crazy Domains, GoDaddy).
- Hosting: can you log in to the hosting control panel yourself, today, without asking anyone? If hosting is "included" in a monthly fee to your agency, ask whose name the hosting account is in.
- CMS admin: do you have an administrator-level login to the CMS (WordPress, Shopify, etc.) — not an "editor" account that cannot add users or export data?
- Code and content: for custom-built sites, ask where the source code repository lives and whether you have access. For builder platforms, check what the export function actually exports (often content only, not design or functionality).
What auDA rules mean for your .com.au domain
Australian .au domains are governed by auDA licensing rules: a .com.au or .net.au must be registered to an eligible Australian entity — normally your business with its ABN — and the registrant of record is the legal licence holder. If your web company registered the domain under its own name "to make things easy", the licence that your entire online identity depends on belongs to them.
The fix is a registrant transfer (change of registrant) to your business, which your current provider has to cooperate with. Do this while things are amicable. If a provider resists transferring a domain that represents your trading name and brand, that resistance is itself the answer to whether you should stay.
If a provider will not hand over access
Escalate in this order. First, request specific credentials in writing: registrar login or registrant transfer, hosting access, CMS admin, and a copy of the code and database. Vague requests get vague answers; itemised requests create a paper trail.
Second, check your contract and invoices — if you paid for the build, the default position in most Australian service arrangements is that you are entitled to the deliverable, though IP clauses vary and some agencies legitimately license rather than sell. Third, for .au domains where you are the rightful registrant but are being blocked, raise a complaint through your registrar and auDA. Finally, factor in the economics: past a certain point, rebuilding cleanly on infrastructure you own outright costs less than fighting. Our website rescue tier exists for exactly this situation — a $350 audit that maps what you actually control, credited toward a fix-up or rebuild from $2,750 if you proceed.
How to buy a website so this never happens
Set the ownership terms before the project starts. Register the domain yourself, in your registrar account, even if the agency manages DNS for you. Require that hosting is in your name (or contractually transferable on request without fees). Ask directly: "If we part ways in two years, what exactly do I walk away with, and what does the handover cost?" A good studio has a crisp answer.
This is how we structure every Fantom Labs build: your domain, your hosting account, your analytics, and the site code handed over — the ongoing relationship has to be earned by the work, not enforced by the lock-in.
Frequently asked questions
My web designer registered my domain in their name. Is that legal?
It happens frequently and is usually a convenience shortcut rather than malice, but for .au domains the registrant should be the eligible Australian entity the domain represents — your business. Request a registrant transfer to your ABN-holding entity; a cooperative provider will action it quickly.
Do I own the code if I paid for the website?
Check your agreement. Paying for a build usually entitles you to the deliverable, but some agencies license their platform or theme rather than transferring it. If the site runs on the agency’s proprietary builder, there may be no meaningful code to own — which is the strongest argument for asking this question before you sign.
What should a website handover include?
Registrar access or registrant transfer for the domain, hosting account access, administrator CMS access, source code and database copies (or repository access), any third-party service logins (analytics, search console, email), and DNS records documentation.
Can I move my website away from Wix or Squarespace?
You can move your content and domain, but not the site itself — builder platforms do not export working sites. Moving means rebuilding on a new stack, which is why we treat outgrowing a builder as a planned migration. See our Squarespace and Wix migration guide.
Sources
Not sure what you actually control?
The $350 website rescue audit maps your domain, hosting, platform and SEO position in plain language — and is credited toward any fix-up booked within 30 days.
Related
Published 19 July 2026 by the Fantom Labs studio team, Perth WA.