Your Web Designer Disappeared: Recovering a Website in Malta

First establish control of the domain, hosting and business accounts; then assess what can be recovered. Rebuilding immediately can destroy useful evidence, interrupt email or leave the same ownership problem unresolved.

Preserve the current position

Save the contract, invoices, correspondence, agreed scope and any access information already held by your business. Record the exact problem: a missed deadline, a non-working site, loss of contact or an account dispute. These situations require different responses, and silence alone does not establish fraud or abandonment.

Avoid deleting the existing installation or paying an unknown recovery service on the strength of a promise. If the site appears compromised, ask a qualified administrator to preserve a copy and contain the incident. Keep public statements factual while any dispute is unresolved.

Establish domain and email control

Find the domain registrar, registrant account and renewal contact. Use the registrar's official recovery process if you cannot sign in. The process depends on the domain extension and account evidence; ICANN guidance is relevant to domains within its remit, not a universal recovery procedure for every country-code domain.

Check where business email is hosted before changing DNS. A replacement developer should document existing mail records and how a change could affect delivery. Move control into an account belonging to your business through the provider's authorised process. Do not attempt to access someone else's account or bypass authentication.

Obtain a safe copy of what exists

Ask the authorised host for the available website files, databases and backups. Identify whether the recovered material includes source code, uploaded images, configuration and the latest content. Credentials may need rotating through approved account procedures after recovery; do not publish them in a support request or shared project document.

Have the replacement developer examine a copy in an isolated environment. Disable real email, payments and scheduled jobs there so testing cannot affect customers. Establish what works, what is incomplete and what depends on a third-party licence or service owned by the previous provider.

Decide between repair and replacement

A short technical assessment should describe the recoverable assets, important defects, security concerns and an estimate for each path. Repair can preserve URLs and content, but may be poor value if the implementation is undocumented or incompatible with the required features. Replacement still needs a plan for redirects, data and account continuity.

Keep commercial and legal questions separate from technical diagnosis. Ask a suitable adviser about disputed ownership, unpaid invoices or contractual remedies. A developer can assess code and access; it should not promise a legal entitlement or use account recovery to settle a payment dispute.

Make the new handover concrete

• Register core accounts in the business's name and identify recovery contacts.
• Agree a list of deliverables, source/data exports and third-party dependencies.
• Require a tested backup and a documented restoration procedure.
• Tie milestones to working functions, rather than screenshots alone.
• Set maintenance responsibilities and a practical exit process.

The goal is a recoverable business asset, not merely a replacement homepage. Use our designer interview checklist before the next contract, and insist that another competent provider could take over without starting the access investigation again.

Sources and review

Official references checked on 18 October 2026. Provider terms, funding calls and technical documentation can change; verify the applicable version before committing to a purchase or application.

• ICANN registrant rights and responsibilities for applicable domains