Helper CTO Series 21 | Can't Find the Original Vendor: Getting Your Domain, Hosting, and Source Code Back

"They registered it for us back then, and we couldn't reach them after that." The website is still running, but the moment you need to change a word, switch hosting, or hand the system to someone new, you discover the domain, hosting, and source code aren't actually in your hands. You weren't careless back then — nobody told you these needed to be registered under your company's name. How to trace all three back, and what options are left if you can't, in one place.

The Three Sentences You Hear Most: It's Not in Your Hands

Owners who can't find their original vendor usually open with one of three sentences:

• "They registered the domain and hosting for us back then": both sit under the vendor's account, and you just pay the renewal every year.
• "The code is with them": you have a URL, but not a copy of the source code of your own.
• "I think we were given the login once": you were, but it's sitting in a former employee's inbox.

The first step is the same for all three: confirm who it's registered to, who's paying for it, and who has login access. Most of this checking doesn't need the vendor's cooperation. The same checklist from 12 things to reclaim when a developer leaves applies here too.

Match Each Item to Where You Check

Not knowing where to check is the most common sticking point. Match the location first:

The most urgent is the domain — it has an expiration date. The database has no backup, so once it's gone, it's really gone.

Three Things, Three Ways to Reclaim Them

Once you've matched the location, how you reclaim each one differs. For the domain, check the registration:

• Registrant is your company: you just need the password — use the registrar's "forgot password" with the registered email.
• Registrant is the vendor: you need them to transfer it or hand over a transfer code — you can't do this yourself.
• Check the expiration date first: there's a grace period after it lapses, but once that passes, someone else may register it first.

For hosting, follow the money:

• You're the one paying: bring your payment records to the host's support team — they can usually switch the admin over.
• Hosting is bundled into a maintenance fee: the account is under the vendor's name, and what you're paying is effectively a sublease.
• Ask support directly whether company documentation can transfer admin rights — every host has a process for this.

For source code, check the repository:

• Opened under a company account: just recover the account — that code has always been yours.
• Opened under the vendor's personal account: that code was never actually yours.
• If the site is running, there's a working copy of the code sitting on the server somewhere — pull down the whole thing.
• A former employee's computer, the original point of contact, or a zip file the vendor once emailed all count too.

The copy on the server isn't necessarily the latest, but having one working copy of the code gives you something to work with.

If You Can't Get It Back, What's Left

When something is stuck with the vendor, it falls into one of three situations:

• The vendor still exists but isn't responding: switch to a formal written request stating exactly what you need, a deadline, and who it should go to next.
• The vendor no longer exists: contact the registrar's and host's support teams and ask whether company documentation can transfer admin rights.
• They claim the code is theirs: that's outside our expertise — please have a legal professional make that call.

When ownership is in question, what we can do is lay out the technical facts for a professional to review. There's one path many people don't think of: you don't necessarily need everything back. If you have the domain and can export the data, rebuilding is often faster than fighting for it — the outsourcing mindset for a labor-scarce era piece covers this: the assets that matter are the data and the process.

Once You Get It Back, Run a Health Check First

The moment you get everything back, you're holding a pile of accounts and a package of code. The worst move is rushing to hand it to a new vendor to start making changes. Get clear on three things first:

• Whether the code is the latest version, and whether someone else can take it over.
• Whether the hosting and domain settings have issues, or any backdoors were left behind.
• What's still missing, and how urgent it is to recover.

A health check only needs visibility into the code — it can start even before every credential is collected. Next, make sure this doesn't happen again: register everything under your company's name, keep passwords somewhere your company controls, and put together a minimal documentation set for the next person; the full approach is in the system operations handover guide.

When Nerdtechnic Takes Over a System Like This, We Promise You Four Things

• The health check only needs to see the code — no production credentials required, and it can start even before every access right is collected.
• There are only three possible conclusions: ready to take over as-is, needs cleanup first, or a rebuild would actually be cheaper.
• Takeover, maintenance, improvement, and ongoing development — the same team handles all four from start to finish.
• When the engagement ends, the documentation and records stay with you — changing hands never turns into a black box.

Getting things back is a one-time event. Having someone accountable for the long run is what you actually lack.

Getting the domain, hosting, and source code back is only the first step — after that, someone needs to be responsible for it. Nerdtechnic takes over systems like this as your Helper CTO — like an in-house tech lead, just not on your payroll. The first step is a 60-minute system health check: we just need to see the code, no production credentials required, and within 3–5 business days you'll get a one-page report you can actually understand. If the package you just got back leaves you unsure whether it even still works, we'll help you get a clear picture of its condition first — then you decide whether to work with us: Helper CTO: System Maintenance Plan.