The Short Answer
Probably not all of it — and the piece you are most likely missing is not the piece you would guess.
"Your website" is not one asset. It is five, they are held in different places, and they can be separated from each other without anyone doing anything shady. Most owners we talk to hold three of the five and have never checked the other two. The two they are missing are usually the two that matter when a relationship ends.
This page is for people who already have a site and want to know where they stand. If you are still choosing a provider, the questions to ask before signing are in our done-for-you websites guide and the contract terms worth reading twice are in what to look for in a web design company. This one is the audit you run on what you already have.
Ownership Is Five Separate Things
| The asset | Who usually holds it | How to check | What it costs you to lose |
|---|---|---|---|
| The domain name | Whoever is the registered name holder — sometimes the designer | Log into the registrar yourself; see who gets the renewal email | Your address on the internet, your email, your search history |
| The registrar and DNS account | The person who set it up | Can you change a DNS record without asking anyone? | Control of where the domain points, including your email |
| The hosting or platform account | Often the provider, with you as a user | Is the account in your name and billed to your card? | The ability to keep the site online without them |
| The code and design files | Legally, often still the designer | Is there an ownership or assignment clause in writing? | The ability to move the site or hire anyone else to change it |
| The content | Usually you, for anything you wrote or shot | Do you hold the original copy, photos and logo files? | Years of writing, and the pages that earn your traffic |
Two more worth adding to the list, because they are commonly missed and both are free to fix: your Google Search Console and Analytics properties (are you Owner, or a user on someone else's property?) and your Google Business Profile, where the equivalent audit is in our Google Business Profile guide.
The Legal Default Surprises People
Here is the part that catches owners out, and it is worth being precise about because the folklore is wrong.
Paying for work does not automatically transfer the copyright in it. Under 17 U.S.C. §101, a commissioned work by someone who is not your employee is a "work made for hire" only if it is one of nine listed categories: a contribution to a collective work, part of a motion picture or other audiovisual work, a translation, a supplementary work, a compilation, an instructional text, a test, answer material for a test, or an atlas. A website is not on that list, and the categories have been read narrowly.
Separately, 17 U.S.C. §204(a) says a transfer of copyright ownership "is not valid unless an instrument of conveyance, or a note or memorandum of the transfer, is in writing and signed by the owner."
Put those together and the default is counterintuitive: if your agreement says nothing about ownership, the freelancer or agency may still hold the copyright in the code and the design, even though you paid the invoice in full. This is why competent contracts do not rely on "work for hire" wording at all — they contain an explicit assignment of the work to the client on payment. Ours does, and we quote it further down.
Three honest caveats. An in-house employee's work is a different clause of the same statute and normally belongs to the employer. Your own content — the copy you wrote, the photos you took or paid a photographer for — is a separate work from the code that displays it. And this is a plain-English explanation from someone who builds websites, not legal advice: if real money or a real dispute is involved, take your actual contract to an attorney.
What You Can Check in Ten Minutes
Do these in order. You do not need to tell anyone you are doing it.
- Log into your registrar. Not WHOIS — registrant details are commonly redacted for privacy now, so a lookup often tells you only which registrar holds the name. The real test is whether you have your own login, and whether the renewal notice lands in your inbox. If you have never seen a renewal email for your own domain, someone else is getting it.
- Try to change one DNS record. You do not have to save it. Either you can reach the DNS settings or you cannot, and that answer is the whole point of the exercise.
- Check whose name is on the hosting. An account in your business name, billed to your card, is yours. Being a user inside your provider's account is not the same thing, even when they are entirely honest about it.
- Find the code. A repository you can log into, or a dated zip of the site files, or nothing. "They have it" is the same as nothing on the day you need it.
- Find the originals. Full-resolution photos, the logo in a vector file, the text of your pages somewhere other than the live site. Anything you can only see by visiting your own website is something you can lose.
- Open Search Console and Analytics. Verify whether your access level is Owner. Years of search data does not transfer if the property belongs to someone else.
Score yourself honestly. Five or six is a healthy position. Three or fewer means an ordinary disagreement could become an outage.
What Happens If You Stop Paying
There are three common models and they behave completely differently. The contract language matters less than which model you are actually on.
Subscription or leased sites. No build fee, a monthly payment, often a 12 or 24 month minimum. Ownership of the design and code typically stays with the provider while you subscribe. Stop paying and the site generally comes down at the end of the billing period; you keep whatever is registered in your name, which is frequently just the domain. This is a legitimate model and plenty of businesses are well served by it. It should simply be disclosed plainly, and you should know you are renting.
Build fee plus a monthly plan, with ownership. You paid for the build, the code and content are assigned to you, and the monthly fee buys hosting, support and changes. Canceling ends those three services. It does not switch the software off, because the files are yours — they move to another host or another developer. The practical question is only how fast you can get a copy.
A proprietary platform. The quiet failure case. Some providers will tell you that you own your site while building it on a closed system that cannot run anywhere else. A site you own and cannot host is not meaningfully yours. Ask what the site is built on — standard code, an open platform, or their own closed system — as a question entirely separate from who owns it. The done-for-you websites guide covers how to spot this before signing.
The same logic applies to the software side of a business. Renting a per-seat system means canceling ends your access to your own operating history, which is the whole argument behind custom business software you own and the pricing math in what custom software costs.
If the Audit Goes Badly: What You Can Get Back
Work in this order, because it runs from "there is an enforced process" to "there is only goodwill." If the plan is to hand the site to someone else rather than simply to hold what is yours, the sequencing — and the Google accounts whose own rules set the timeline — is in how to move your website to a new developer.
1. The domain. This is the strongest position you have, because the rules are not up to your provider. ICANN's registrant FAQ states plainly that "it is your right to transfer your domain name registrations between registrars," and that your registrar "must provide you with the AuthInfo code within five (5) calendar days of your request." Request the code in writing, then move the registration into an account in your own name.
Two timing facts worth planning around, from the same source: a registrar may deny a transfer within 60 days of initial registration, and you cannot transfer to a different registrar within 60 days of changing the registrant name. So update the registrant details and transfer in the right order, or you will wait two months in between.
2. The content. Your words and your photos are usually yours regardless of what happens to the code. Anything already published can be re-collected from the live site — copy, service descriptions, blog posts, testimonials you were given permission to use. Do this while you still have access to everything, not after.
3. The code and the design files. Ask once, in writing, and cite the ownership clause if you have one. If your agreement is silent, be realistic: as above, they may be entitled to decline, and a long argument about a small website is rarely the best use of the next month.
4. Rebuild, if it comes to that. Unsatisfying, and often the right call. With the domain and the content in hand, a rebuild keeps your URLs, your search history and your copy — which is most of the actual value. What you lose is the build fee you already paid, not the asset. This is also why the audit above is worth running on a quiet Tuesday rather than during a dispute.
Our Answer, In Writing
We will hold ourselves to the same standard this page asks of everyone else, so here is our position where you can check it.
From our terms of service: "Upon full payment, clients own the websites we build for them, including custom design elements, content, and code." The one reservation, stated in the same place, is that we keep the right to show completed projects in our portfolio unless you ask us not to in writing.
On the commercial side, our published pricing is a $1,500 one-time build fee plus a monthly plan from $20, you can cancel with 30 days notice, and you own the site, content and domain. The domain is registered in your name. The code lives in a repository tied to your business. Canceling the plan ends hosting, support and changes — it does not end your website.
None of that makes us special; it is what the model should look like. It is on this page because it is checkable, which is the only kind of claim worth making about ownership.
If You Only Do One Thing
Log into your domain registrar today.
Not your website, not your email, not your hosting dashboard — the registrar where the domain itself is registered. If you can get in and your name is on the account, you are in a recoverable position no matter what else the audit turns up. If you cannot, you have found the thing to fix this week, and you now know the two sentences from ICANN that get it fixed.
If you would rather someone walk the list with you, a free consultation will do it, including the parts where the honest answer is that your current provider is treating you fairly.