Recover Website Content When You Have Lost Hosting Access

If you have lost access to the company or person who manages your website hosting, this guide explains the practical ways to recover your website files, databases and email data.


If you are first trying to work out who controls your domain name, DNS or website hosting, read How to check who controls a domain name, DNS and website hosting.


Important: BinaryLane provides self-service infrastructure to account holders. Some BinaryLane customers provide services to their own clients. We cannot disclose another customer’s account details, grant a third party access to their server or services, make DNS changes for them, or retrieve data from their customer-managed server.

TABLE OF CONTENTS

Check for existing access

Before changing DNS or cancelling any service, check whether you already have access to a hosting control panel, backup system, source-code repository, or a local copy of the website.

Check for hosting control panel access

Many hosting providers offer a control panel, such as cPanel or Plesk, separately from the main hosting account. Search old emails, password managers and internal documentation for login details.

If you can access a control panel, download or export:

  • Website files, commonly from public_html, www or the site’s document-root directory.
  • Database backups, usually SQL export files.
  • Email mailboxes, forwarders and aliases, where email is hosted with the website.
  • Application settings, PHP version, cron jobs and other configuration needed to restore the site.

Tip: Download a copy of the site and database before changing DNS or making other hosting changes, even if the current website is still online.

Check for backups

Look for backups held independently of the old hosting account. Useful places include:

  • A hosting-panel backup tool, such as JetBackup or a provider-specific backup section.
  • Your organisation’s local computers, file storage or backup system.
  • A source-code repository and any deployment documentation.
  • Previous web developers, IT providers or agencies that may have supplied a handover copy.

A complete website recovery normally needs both the website files and its database. A files-only copy may not restore a content-management system, online store or other database-backed application.

Contact the hosting provider

If you know who provides the hosting, contact them using the account holder’s normal support path. They may be able to assist their verified account holder with account access, exports or available backups.

If the website runs on a BinaryLane server that belongs to another customer, that customer is responsible for the server and its data. BinaryLane cannot provide third-party access or disclose information about that customer’s account.

If you cannot access the service or a backup

Recovery options are limited if you cannot access the hosting service and no backup exists. You can still try the following:

  • Wayback Machine:search the Internet Archive for archived public pages. This may help recreate public content, but does not restore databases, email, login-protected pages or original assets reliably.
  • Local copies: check computers, shared storage, email attachments, CMS exports and previous deployments.
  • Contact the original provider: use the contact details you already hold for the web developer, IT provider or agency. Where appropriate, check the Australian Business Register for public business details.
  • Independent advice: if significant business assets are involved and the responsible party remains unavailable, consider obtaining independent legal advice.

Move recovered content to new hosting

Once you have recovered the content, use this order to reduce downtime:

  1. Set up the new hosting service that you control.
  2. Restore the website files, database and required configuration.
  3. Test the restored site using the new provider’s preview method or temporary address, if available.
  4. Update DNS at the provider that controls the domain’s DNS zone. See our domain, DNS and website-hosting guide if you are unsure where this is managed.
  5. Keep the old service active until the replacement site has been tested and DNS changes have taken effect, where you have control of the old service.


Important: Do not cancel the old hosting service until you have confirmed that the replacement website works and that any required data has been copied.


Prevent this happening again

  • Keep the domain registration in your organisation’s name, with a business-controlled email address.
  • Keep administrator access to the registrar, DNS provider and hosting account under your organisation’s control.
  • Maintain regular backups of website files, databases and email data that your organisation can access independently.
  • Document the providers and account owners for the domain, DNS zone, hosting service and source-code repository.
  • Review who has access when staff, developers or providers change.

Need help with a BinaryLane account you control?

If you need help with a BinaryLane service in your own account, submit a ticket.