How to Recover Your Website When the Agency Stops Responding

Your website is online, but you no longer control it. The agency that built it has stopped answering e-mails. Calls go straight to voicemail. And you need to update a page, renew the domain, or simply find out where everything lives.

This situation is far more common than you’d think. An agency shuts down, a freelancer changes careers, an overloaded provider quietly drops clients without saying so. The result: your main shop window depends on someone who has vanished.

The good news: in most cases you can recover everything — domain, hosting, code, content, data — without starting from scratch and without taking your site offline. Here is how to recover your website from a former provider, step by step.

Recognising ghosting (and not confusing it with a delay)

A busy provider can take a week to reply. Not pleasant, but not abandonment either. Ghosting is a pattern that repeats:

• Several follow-ups by e-mail and phone, with no answer over three to four weeks.
• Repeated promises — “I’ll get to it this week” — never followed by action.
• The site goes down or gets hacked, and nobody reacts.
• Maintenance invoices keep arriving while nothing is actually being done.
• A company struck off or in liquidation, an agency website that is itself abandoned.

The moment you recognise this pattern, change gears. Stop the informal follow-ups and send a registered letter with acknowledgement of receipt: a formal request for the return of your access credentials, your code and your data, with a clear deadline. This letter isn’t meant to threaten — it documents your request, sets a date, and will carry weight if things need to be settled legally later.

Keep a record of everything as well: screenshots of the site, e-mails sent, invoices paid. That is your file.

First things first: who owns what?

Before recovering anything, you need to know what actually belongs to you. A website is not a single object — it’s a stack of elements, each with its own owner:

• The domain name (your site’s address)
• The hosting (the server where the site lives)
• The source code (the files that make the site run)
• The database (your content, form submissions, orders, clients)
• The content and media (copy, photos, logo, videos)
• The third-party accounts (payments, e-mailing, analytics, Google listing)

Dig out your contract and your invoices. Look for intellectual property and rights-assignment clauses. Then check, element by element, in whose name each item is registered. We’ve detailed the full method in how to check who really owns your website — start there if you’re not sure of anything.

This diagnosis shapes everything that follows: a domain registered in your name and one registered in the agency’s name are not recovered the same way.

Recovering the domain name

This is your most important asset. A website can be rebuilt; ten years of reputation attached to a lost address cannot.

First reflex: a WHOIS lookup to identify the holder and the registrar. For a .lu domain, the official registry is DNS-LU. Three scenarios:

The domain is in your name. Contact the registrar directly, prove your identity, and get the account access back. The agency no longer needs to be in the loop.

The domain is in the agency’s name. You need a change of holder. Concretely, the agency must give you the authorisation code — also called the EPP code or auth code — that allows the domain to be moved to your own registrar account. This is exactly what your registered letter should demand. If the agency has vanished or is in liquidation, contact the registrar with your evidence: contract, invoices, registered trademark, pages of the site naming your company. Procedures exist for these cases; they are simply slower.

In every scenario: watch the expiry date. A domain that isn’t renewed eventually falls back onto the open market, where anyone can buy it. If the deadline is close, fix this before anything else.

Recovering the hosting

Two possible situations.

The hosting is an account in your name that the agency managed for you: reset the password via the billing e-mail address, take back control, then change every credential the agency held.

The hosting is the agency’s own account — the most common case. You won’t recover the account itself, and that’s fine. What you need is a complete copy: all the site’s files, plus an export of the database in a standard format. Those two elements are enough to reinstall your site with a new hosting provider.

Put this request in writing in your letter. Your data — contact enquiries, order history, client records — belongs to you. For your clients’ personal data, GDPR works in your favour: the provider processes it on your behalf, not for itself.

And if nothing moves, all is not lost: a site’s public pages can be copied and its content rebuilt. It’s work, but it’s doable — sometimes faster than legal proceedings.

Recovering the source code

This is where the contract matters most. Two questions to settle:

• Does the contract assign the rights to the code to you? If so, it’s yours, and the agency must hand it over.
• Is the contract silent? In practice, code often remains the property of its author, but you keep a right of use over what you paid for. A copy of the deployed files — the ones on the hosting — can still be demanded in most cases.

Ask for a complete handover: the files, any dependencies, and the instructions needed to run the site. The test is simple: a competent developer should be able to take everything over without ever calling the previous provider.

Let’s be direct about one thing. If the site was built on the agency’s proprietary system, or if the code is genuinely unrecoverable, a rebuild is sometimes faster and cheaper than a legal standoff. That’s not a failure — it’s arithmetic. What must be saved first: the domain, the content, the data. The code can be rewritten.

Recovering third-party accounts (Stripe, Mailchimp…)

A modern website relies on a constellation of services. Make the list, then take them back one by one:

• Online payments (Stripe, PayPal) — critical: your money flows through them.
• E-mailing (Mailchimp, Brevo) — your contact list is a business asset.
• Google Business Profile — your customer reviews live there.
• Google Search Console and analytics tools.
• Forms, online booking, chat modules.
• Social media accounts linked to the site.

Two levers. If the account was created with one of your company’s e-mail addresses, the “forgot password” procedure is often enough. If the account is in the agency’s name, every platform has a transfer or claim procedure — Google, for instance, lets you claim a business listing you legitimately own. For payment accounts, contact support directly with your company documents: these platforms know how to handle this case.

Migrating without downtime

Once the pieces are recovered, don’t cut anything off in a hurry. A clean migration follows a precise order:

1. Full backup first. Files and database, verified, stored on your side.
2. New hosting installed and tested on a temporary address, while the old site keeps running.
3. Mind the e-mails. If your business addresses depend on the same provider, their configuration — the MX records — must be replicated before touching the domain. This is the most common oversight, and the most painful one.
4. DNS switch. Lower the cache duration (the TTL), then point the domain at the new server. The transition happens within hours, with no visible interruption.
5. Redirects preserved. Every old address must lead to the same content or redirect cleanly, to protect the search rankings you’ve earned.
6. Cancel last. The old hosting is only terminated once the new site has been checked from every angle.

Done properly, a migration is invisible to your visitors and to Google alike.

Locking things down so you’re never blocked again

Once you’re out of trouble, put the rules in place that make the problem impossible to repeat:

• The domain name is registered in your name, in an account whose credentials you hold.
• The hosting is a contract between you and the hosting company — the provider is a guest there, not the owner.
• The contract assigns the rights to the code to you and requires a copy at every major update.
• Every third-party account is created with one of your company’s e-mail addresses.
• You keep one document up to date: list of credentials, who holds what, renewal dates.
• The contract includes an exit clause: what happens, concretely, if the collaboration ends.

A serious provider will accept these terms without arguing. One who refuses is telling you something important about what comes next.

And a rescue isn’t just damage control — it’s often the chance to do better than before. A well-executed rebuild changes the game: Solenergie went from zero leads to full order books in 60 days.

How we work at Slash.lu

We regularly take over websites whose provider has stopped responding. The approach is always the same: an inventory of what can be recovered, recovery of the domain and the data, a migration without downtime, then — if the site deserves it — a rebuild with everything registered in your name.

You deal with a single point of contact from start to finish, not an intermediary. And you walk away owning every building block: domain, hosting, code, content.

To see how we build websites that belong to their clients, browse our web design service . And before signing with a new provider, re-read what a professional website must deliver, regardless of budget.

We can talk it through for 30 minutes. Book a slot. Whether you work with us afterwards or not.

Your website belongs to you. If it’s stuck with an unreachable provider, that’s fixable — methodically, and often faster than you’d expect.