Most business owners find out who owns their website at the worst possible moment: the developer stops answering email, the domain renewal lapses, or a redesign stalls because nobody can log in to anything. If you have ever wondered who owns your website, the honest answer is that a website is five separate assets, and many businesses control fewer of them than they think.
This is not a rare problem. Disputes between owners and the developers who registered "their" domain are common enough that ICANN publishes consumer guidance on registrant rights, and copyright law contains a default rule that surprises almost everyone: paying for a website does not automatically make you the owner of its design or code.
This article covers the five assets that make up a website, how to audit your access to each one this week, what the law says when there is no contract, and what to do if a developer has effectively locked you out.
A Website Is Five Assets, Not One
Your website is really five separate things: the domain name, the hosting account, the software it runs on, the content, and the connected accounts around it. Each can have a different owner, so auditing them separately is the only way to know where you stand.
The domain is the address (yourbusiness.com), rented annually through a registrar. Hosting is the server space where the site's files live. The software is the platform or code that renders the pages. The content is your text, photos, and video. The connected accounts are everything wired into the site: Google Business Profile, Analytics, Search Console, your email service, your booking or payment tools.
Here is the uncomfortable part: you can pay for all five for years and legally control none of them. A developer may have registered the domain under their own name, opened the hosting account on their own card, and kept every password. That is rarely malicious; it is often just how a quick, cheap project got set up in 2019. It becomes a serious problem the day the relationship changes.
How to Check Who Owns Your Website's Domain
The registrant listed in your domain's registration record is the legal holder of the domain, regardless of who paid for it, so checking that record is the first step in finding out who owns your website. You can look up any domain free at ICANN's registration data lookup tool.
Privacy services redact most personal details now, so the lookup may not show a name. It will always show the registrar (GoDaddy, Namecheap, and so on), the creation and expiration dates, and the status codes. That is enough to act on: do you have a login at that registrar that shows this domain in your account? If not, someone else is the registrant, probably whoever built the site.
Two timing rules from ICANN's registrant FAQ matter when you fix this. First, changing the registrant's name, organization, or email typically triggers a 60-day lock during which the domain cannot move to a different registrar; some registrars let you opt out, but they are not required to offer it. Second, once you request a transfer authorization code, your registrar must provide it within five calendar days. So if you are reclaiming a domain and also want to move it to your own registrar, plan the order of operations. ICANN's own guidance suggests completing the transfer before changing contact information, and starting well before any deadline such as a renewal or a business sale.
While you are in the record, check the expiration date. An expired domain eventually returns to the open market, and domains with real traffic get snapped up quickly. Multi-year renewal plus auto-renew on a company card is cheap insurance.
The 10-Point Access Audit
You can establish how much of your website you actually control in about an hour, using one test: for each item below, can someone at your company, not your vendor, log in today, under an account registered to a company email address? Mark each item yes or no.
- Domain registrar login. You can sign in and see the domain listed in an account your company owns.
- Registrant identity. The registrant on record is your company, not a vendor or an employee who might leave.
- DNS control. You know where the DNS records are managed (often the registrar, sometimes the host) and can reach them.
- Hosting account. The hosting subscription is in your company's name and billed to your card, not a line item inside an agency's reseller account.
- CMS administrator access. You have an administrator-level login to the site itself, not an "editor" account that cannot add users.
- Site backups. You hold a recent backup of the site's files and database somewhere your vendor cannot revoke.
- Google Business Profile ownership. Your company account is the primary owner, with any agency added as a manager.
- Analytics and Search Console. Your Analytics property and Search Console verification live under a company Google account.
- Email and marketing tools. The accounts for your email platform, booking system, and payment processor belong to you, with vendors as invited users.
- Content files. You keep original copies of your photos, videos, and logo files outside the website.
Scoring is blunt on purpose. Items 1, 2, 4, and 5 are the load-bearing walls: a "no" on any of them means a vendor dispute could take your site offline, so fix those first. Items 6 through 10 determine how painful a migration would be. A business with ten yeses can change vendors in a week; a business with four noes is negotiating from weakness. If you are planning a rebuild, run this audit first. Our guide to redesigning a website without losing rankings assumes you have this access, and so does every reputable developer's onboarding.
Who Owns the Design When There's No Contract?
Under U.S. copyright law, an independent contractor who builds your website owns the copyright in what they created unless a written agreement says otherwise. That default surprises most owners, but it comes straight from the U.S. Copyright Office's Circular 30 on works made for hire: a commissioned work from a non-employee only qualifies as a "work made for hire" if it falls into one of nine narrow statutory categories (translations, tests, atlases, and the like; website design is not on the list) and the parties signed an agreement expressly saying so. Fail either condition and the creator is the author and owner.
In practice, a freelancer who built your site on a bare invoice likely holds the copyright to the design and any custom code, while you have, at best, an implied license to keep using it. That is murky territory you do not want to test in a dispute. Your own materials are different: text you wrote and photos you took were always yours. The gray zone is everything the vendor produced.
The fix costs nothing at contract time. Before your next web project, make sure the agreement includes four things: an assignment clause transferring all rights in the delivered design, code, and graphics to your company upon final payment; a statement that all accounts (domain, hosting, CMS) will be created in your company's name from day one; a handover clause requiring credentials and a full backup at launch and at termination; and a list of any third-party components (themes, plugins, stock photos) that are licensed rather than owned. A developer who resists all four is telling you something. None of this is legal advice; for an existing dispute or a business sale, have a lawyer review the specifics.
Website Builders: What You Can and Can't Take With You
With site builders like Wix and Squarespace, ownership of the design is mostly beside the point, because the site cannot leave the platform in usable form. Wix states plainly in its support documentation that sites must be hosted and operated on Wix's servers and cannot be exported to run elsewhere. Squarespace exports more: an XML file with layout pages, one blog, and text and image blocks. But store pages, event pages, audio and video blocks, style settings, and custom CSS do not come with you. Leaving either platform means rebuilding, and budgeting for it.
Open-source platforms sit at the other end. WordPress software is licensed under the GPL, per WordPress.org, and a standard WordPress site's files and database can move to any competent host, provided you have the hosting and admin access from the audit above. Portability is a property of the platform plus your access, not the platform alone.
None of this means builders are the wrong choice. Lock-in is an acceptable trade when the site is simple, the monthly cost is low, and you would rebuild rather than migrate anyway. It is the wrong trade when the site carries years of blog content and search rankings, runs e-commerce, or is a core asset you would expect to sell with the business. Decide with your eyes open, and weigh the three-year cost rather than the first-month price; we break that math down in how much a small business website costs.
What to Do When Your Developer Disappears
If your developer has gone silent and you lack access, act in this order: secure what you can reach, document everything, then recover the domain first, because it is the one asset you cannot rebuild. Here is the sequence that works.
- Save a copy of the live site today. Before anything changes, save every important page from your browser and download your key images. It is not a real backup, but it preserves your content and proof of what existed.
- Put your requests in writing. Email the developer a specific list (registrar login or domain transfer, hosting credentials, CMS admin, backup files) with a reasonable deadline. Stay civil; most cases are neglect, not hostage-taking.
- Run the ICANN lookup. Identify the registrar and expiration date so you know how much runway you have and where to direct a recovery request.
- Work the registrar's recovery process. If the domain was registered on your behalf, registrars have procedures for disputes and account recovery; business records showing you paid for the domain help. If the registrant record is genuinely the developer, you are negotiating a transfer, not claiming an account, which is why step 2 matters.
- Mind the clocks. Remember the 60-day rules: a registrant change can lock the domain against transfer, and expiration starts a countdown you do not control. Sequence changes accordingly.
- Rebuild hosting in parallel. If hosting is unrecoverable, a new host plus your saved content gets a replacement site live under the same domain once you control DNS. Rankings survive a rehost far better than months of downtime.
- Escalate proportionately. A lawyer's letter resolves many stalemates for a few hundred dollars. Formal domain dispute processes exist for bad-faith cases, but they are slow; treat them as a last resort and get advice first.
Then make the lesson permanent: finish the 10-point audit, move every account to company ownership, and store credentials in a password manager at least two people in the business can reach.
Frequently Asked Questions
My developer registered my domain in their own name. Is that legal?
Usually yes, which is exactly the problem. Whoever is listed as registrant holds the domain, and ICANN's rules protect the registrant on record. Your position rests on your contract, your payment records, and the registrar's dispute procedures. Ask for a registrant change or transfer in writing first; most developers hand domains over without a fight once asked plainly.
I paid in full for my website. Doesn't that make me the owner?
Payment alone does not transfer copyright. Under U.S. Copyright Office guidance, work by an independent contractor is only a "work made for hire" in narrow categories that exclude web design, so without a signed assignment clause the designer typically owns the design and custom code. You own what you supplied, like your text, photos, and logo, and a short written assignment can fix the rest.
Can I move my domain to my own registrar as soon as I get access back?
Sometimes not immediately. Changing the registrant's name, organization, or email can trigger a 60-day lock against transfers to another registrar, and some registrars will not waive it. If a move matters, ask about the lock before making contact changes, or transfer first and update contacts after. Your registrar must give you the transfer authorization code within five calendar days of your request.
What happens to my website if my web agency shuts down?
It depends on whose name is on the accounts. If the domain and hosting are yours, you hire a new developer and barely notice. If they lived inside the agency's accounts, your site can vanish when their bills stop being paid. That is why the audit prioritizes registrar, hosting, and admin access, and why a current backup you hold yourself is non-negotiable.
Should I move my site off Wix or Squarespace?
Only if the platform is now costing you more than a rebuild would. Builders are a fair trade for simple sites. Consider moving when you need features the platform cannot add, when content and rankings have grown into a real asset, or when e-commerce fees outweigh hosting costs. Budget for a rebuild, not an export, since most of a builder site does not transfer.
Put This to Work in Your Business
Style Strand Media builds websites our clients own outright — domain, hosting, and code in your name from day one — and we start every engagement with this kind of access audit, for businesses across North Myrtle Beach and the Grand Strand as well as remote clients. Explore our website design and development work or our broader digital marketing strategy services.



