The developer stopped answering. You never had the logins.
This is the most common version of the problem and the most avoidable in hindsight. One person built it, hosted it under their own accounts, and was the only route to changing anything. Then they stopped replying.
Usually nothing is malicious. Freelancers get busy, take full-time jobs, get ill, or simply move on from a client they were never formally offboarded from. The effect on you is identical either way: a working system you cannot touch.
Before you hire anyone, including us.
These are in order, and none of them cost anything. Working through them will also tell you how serious your situation actually is.
- 01
Write down what you can actually log into.
Not what you assume you have — what you can sign into right now. Domain registrar, hosting panel, CMS admin, database, email, analytics, payment processor, code repository. The gaps are the actual problem.
- 02
Check the domain first and separately.
Run a WHOIS lookup. If the registrant is the developer or their company, start a transfer conversation immediately, because a lapsed domain takes your email and your site down together.
- 03
Reset what you can reset from your own email.
Any service where your address is on the account can usually be recovered with a password reset. Do those before asking anyone for help — it often recovers more than people expect.
- 04
Keep the requests short, dated and written.
One clear message asking for the specific credentials, sent to every channel you have. If this later becomes a dispute, the record of a reasonable request matters more than its tone.
- 05
Do not change hosting or DNS while you are guessing.
Moving a site you do not yet understand is how a recoverable situation becomes an outage. Understand it first, move it second.
Four questions that settle it.
- Can you sign into the domain registrar? This is the single most important answer.
- Is there a code repository you can reach, or is the running server the only copy?
- If the server vanished tonight, what would you still have?
- Is anyone's personal data in it, and would you be able to answer a request about that data?
The first job is access, not code — and access recovery is usually faster and cheaper than people fear. Once you can reach the system, a diagnostic tells you whether what you have is worth continuing with or is better replaced, with a number attached either way.
If you want someone to read it properly.
A paid diagnostic is from $750, two to five days, scoped on a short call before you pay anything. You get what is actually there, what is wrong, what it costs to fix, and a plan you keep — with us or with anyone else.