Find out who actually owns your website, before you need to know

1. The domain name

The most important, and the one most often wrong.

Your domain can be registered in a developer's or agency's name, on their account, with their billing. If that relationship ends badly, or they simply disappear, recovering it ranges from tedious to genuinely not possible.

Check it: look up your domain on any WHOIS service (who.is, or your registrar's lookup). Many registrations are privacy-protected, which hides the name — in that case log into the registrar directly. If you cannot log in because you have no account, that is your answer.

What you want: the domain registered to you or your company, in an account you can log into, with your card on it.

2. The code and the design files

Where does the site actually live as source? A GitHub account, a hosting panel, a page-builder account, or a folder on somebody's laptop.

Check it: ask, plainly — "if I wanted to move to another developer next month, what exactly would you hand over?" A straightforward answer is a good sign. Vagueness is the finding.

Watch for: proprietary page builders where the site cannot meaningfully be exported. You are not buying a website there, you are renting one, and that can be a fine arrangement as long as you know that is what it is.

3. The hosting

Check it: can you log into the hosting account? Is the card on it yours?

If hosting is bundled into a monthly fee and you have no login, you cannot move the site without their cooperation, and you cannot keep it online if they stop working.

4. The content

Photos, copy, logo. Photographers and designers routinely licence work for a specific use rather than transferring copyright, and stock images are licensed per-project.

Check it: ask whether the logo was transferred to you or licensed, and whether the photos are yours to use anywhere. Get it in writing. This one is almost never malicious and almost always undocumented.

Anything can be rebuilt except your domain name. That one carries your search history, your links, and every card you have ever printed.

1. WHOIS your domain. Note who is listed and when it expires.
2. Try to log into the registrar. If you cannot, you do not control it.
3. Try to log into the hosting. Same test.
4. Email whoever built it: "Could you confirm the domain, hosting and code are in my name, and send me the login details for my records?"

That last email is completely normal and any competent professional will answer it without friction. A defensive or evasive reply tells you what you needed to know.

Do not start a fight. In the overwhelming majority of cases this is carelessness, not hostage-taking. Someone registered the domain to get the project moving and never transferred it.

Ask politely for a transfer. Domain transfers are a standard process: they unlock it and give you an authorisation code, you initiate at your own registrar. It takes a few days.

If that goes nowhere, escalate calmly to the registrar — most have a dispute process — and be aware there are formal arbitration routes for domain disputes. They are slow and cost money, which is exactly why doing this check while the relationship is good is worth twenty minutes.

In any future agreement:

• The domain is registered to you, on your account, with your card. Give the developer access if it helps. Access is not ownership.
• You get the source code, in an account you control, at the end of the project.
• Hosting is in your name, even if someone else manages it.
• Content and logo copyright transfer to you in writing on final payment.

None of this is unusual or insulting to ask for. It is what a professional arrangement looks like, and the people worth hiring will offer most of it before you ask.