It usually starts small. An email goes unanswered. Then another. The site is still up, so it's not an emergency yet. Then a renewal lapses, or you want one small change, and you realise you don't actually control any of it.
This happens more than anyone admits. Here is how to get your business back without panicking.
Step 1: Find out who the domain is registered to
Go to a WHOIS lookup and search your domain. You're looking for the registrar (GoDaddy, Namecheap, etc.) and, where it's visible, the registrant. If the registrant is your designer or their company, that is the most urgent problem — the domain is the one piece that's genuinely hard to recover later. If it's in your name, breathe; you're in a much stronger position.
Step 2: Hunt down the accounts before you need them
Search your email for receipts: "domain", "hosting", "renewal", the registrar's name, the designer's invoices. Founders almost always have more access than they think — a billing email here, a verification text there. Write down what you find: registrar login, host login, any CMS or builder account. Access you can locate is access you can recover.
Step 3: Lock the domain to your control first
The domain is the business. If it's in an account you can reach, log in, update the contact email to one you own, and enable auto-renew so it can't lapse during the mess. If it's in the designer's account, your goal is a transfer: you'll need the registrar, and either their cooperation or the registrar's account-recovery process. Start this before anything else — a site can be rebuilt in weeks; a lost domain can be gone for good.
Step 4: Get a copy of everything that still exists
While the site is up, save it. Export content and images from the platform if you can. If it's a custom build, ask the host for a backup or use their file manager. Even a rough copy is leverage and a fallback — far better than starting from a blank page if it comes down suddenly.
Step 5: Decide — recover, or rebuild and walk away
Sometimes the cleanest path is not chasing a silent vendor for months. If you control the domain, rebuilding on hosting you own is often faster and ends the dependency permanently. If the domain is stuck, focus all energy there and treat the site as replaceable. Either way, the finish line is the same: domain, hosting, and files in your accounts.
How to never be here again
When the next site gets built, register the domain yourself, in your name, in your own registrar account. Get the source files in writing as a deliverable. Keep your own logins. That's the whole idea behind owner-of-record, and it's five minutes that prevents this entire article.
If you're in the middle of this right now, you're not the first and it's usually recoverable. Email info@mule-digital.com with what you can see and we'll tell you straight where you stand — we've walked people through this before, and that's part of why /owner-of-record exists.