2/3 Greenhill Road,
Wayville Adelaide SA 5034
Back to Blog

Web Designer Disappeared? How to Take Back Your Website (Australia)

October 12, 2026
Web Design
18 min read

If your web designer has disappeared, identify who controls the domain, hosting and website admin. They are separate assets, so each may have a different recovery route. Check the domain first and contact its registrar if you are the registered holder. Then contact the host through the account holder’s normal support process. If you can access WordPress or the hosting panel, make a backup before changing passwords or moving the site. If the files cannot be recovered, check the Wayback Machine for archived pages, but treat them as partial content references, not backups.

This guide is for Australian business owners who need to recover a website after a designer or developer stops responding. It covers .au and .com domains, hosting and WordPress. It is general information, not legal advice. Get advice before changing an account if ownership or copyright is disputed.

Start here: Write down the domain registrar, the name shown as registrant, the hosting provider, the CMS and the account you can still access. Keep invoices, contracts and messages together. Then work through the recovery route for each account. Do not guess a password or try to enter an account that is not yours.

Start With the Recovery Order

First establish what you can recover. Domain, hosting, WordPress, email and analytics may use separate providers and logins.

  1. Check the domain. Identify the registrar and the registrant details. Make a note of the renewal date and the contact email shown in the registrar or registry records.
  2. Find the host. Search business invoices and bank statements for hosting charges. If you can log in, download the latest full backup before making changes.
  3. Test the CMS. Try your own WordPress, Shopify or other platform login and the normal password reset. Record any error message without repeatedly guessing credentials.
  4. Inventory connected accounts. Check who controls DNS, business email, Google Analytics, Search Console, booking tools, online payments and other services that your site relies on.
  5. Preserve public content. While the pages still load, save the copy and images you have permission to use, and check whether the Wayback Machine has older captures.

For a broader explanation of what is and is not part of website ownership, read our guide to who owns your website. This page focuses on the incident response when the provider has stopped replying, rather than a general audit or a routine handover.

Check Who Is Listed for the Domain

A domain registrar is the company that manages a domain licence. The hosting company stores or serves the site. They may be the same business, but they do not have to be. The registrant is the person or business that holds the domain licence, as recorded in the registry or registrar. The authorisation code, also called the EPP authInfo code or domain password, is what a new registrar needs to start a transfer. Start with the auDA WHOIS lookup for an .au domain, or the relevant registry or registrar lookup for a .com domain. Record the registrar, registrant name, any registrant identifier and the contact email available in the lookup. For .au domains, auDA’s WHOIS Policy says the registry publishes a subset of the registration data. Its current schedule distinguishes fields visible through web WHOIS from those shown through other WHOIS services.

WHOIS shows registrar and registrant information, not your registrar password or who owns the site’s code, copy or hosting account. It is one piece of a complete website asset check.

If You or Your Business Is the Registrant

If the domain is already registered to you or your business, contact the registrar through its published support or account recovery channel. Explain that the account’s former administrator is unavailable, and ask what documents it needs to verify you as the registrant or authorised business representative. The registrar may not be able to give you access to another customer’s account. Its job is to verify the person entitled to control the domain, not to settle a disagreement based only on who paid an invoice.

For .au domains, check the registrant contact details in the registry and the registrar account. auDA provides a .au domain password recovery tool for the transfer authorisation code. The code is sent to the registrant contact email recorded in the registry, so it will not help if that mailbox belongs to the missing designer. Ask the current registrar how to update the contact information and verify your identity. Under the auDA Registrar Rules, a registrar must provide a requested authorisation code within two calendar days where the registry contact details are accurate. If the contact details are inaccurate, the registrar must verify the registrant’s identity before providing the code. The registry contact information must be corrected before a transfer can proceed.

Once you have the code, start the transfer with the registrar you want to use. auDA’s .au domain transfer guidance says an approved .au registrar transfer can take up to three days and has no registrar-to-registrar fee. This moves the licence between providers while keeping the registrant the same. It does not change a designer listed as registrant into your business.

If the Designer or Their Company Is the Registrant

This is not just a password reset. A move from the designer’s name to your business is a change of registrant, which is different from changing registrars. For a .com.au name, the new registrant must qualify under the .au rules, enter a new licence agreement and pay the applicable licence fee. auDA allows a developer to register a .com.au domain on a client’s behalf, but says the client’s details and ABN should be used. Its .com.au guidance says that the details provided at registration determine who holds the domain licence. Ask the registrar what evidence it requires to process a change of registrant.

Send a brief, factual written request to the designer and the registrar of record. Identify the domain, explain the business connection, attach the contract or other relevant paperwork, and request the registrar’s formal change-of-registrant or recovery process. Do not send identity documents to an email address or upload form you have not verified as belonging to the registrar.

Document requirements vary by registrar. For example, VentraIP’s published domain recovery process for an .au name asks for a signed and dated letter on company letterhead, a statutory declaration witnessed by a Justice of the Peace, and a copy of the ABN, ACN or business registration certificate. It says the documents must match the auDA WHOIS record. That is VentraIP’s process, not a universal list. Contact the actual registrar for its requirements, and ask whether it can act if the listed registrant cannot be reached.

For an .au complaint, auDA says the complaint must first go to the registrar of record. If you are not satisfied with the result, you can submit it to auDA. Its complaints process covers potential breaches of .au eligibility or allocation rules and registrar conduct under those rules. It does not decide web hosting matters or website content disputes, and an upheld complaint does not transfer the domain to the complainant. Read auDA’s complaints process before choosing that route. The transfer guidance linked above also says you cannot transfer a .au licence while it is subject to a complaint to the Licence Review Panel, under internal review or under the auDRP. It also requires the licence not to be subject to any current complaints process, dispute resolution or court proceedings. If your ABN was used without permission, auDA’s .com.au guidance says to contact auDA directly.

How .com Recovery Differs

A .com domain is not governed by auDA’s .au eligibility or complaint rules. Start with the registrar shown in the domain lookup and its account recovery process. For a transfer between registrars, the ICANN transfer policy for generic top-level domains describes the AuthInfo code process. If the registrar does not provide a self-service way to generate or manage the code, the policy says it must provide it within five calendar days of the holder’s request. The registrar’s own process, account access, verification and any transfer lock can affect timing. Do not apply .au rules such as ABN eligibility, auDA’s two-day code rule or the .au complaint process to a .com domain. Ask the current and new registrars for the applicable requirements, especially if the registered contact details were recently changed.

Recover Hosting and cPanel Access

The hosting provider controls the hosting account and its panel credentials. If you know the host, open a support request from the billing or customer account you control. Ask what they need to verify that you are the account holder or an authorised representative. A host may be able to restore access, provide an export or identify available backups for its verified customer. It may not disclose or hand over data stored in a different customer’s account.

Prepare your evidence before contacting support. Depending on your relationship with the provider, useful items may include the hosting invoice, payment record, account or service ID, business name and ABN or ACN, a current company extract, photo identification for a director or authorised contact, and a signed authority if you are acting for the business. Do not assume every provider will accept the same documents. For instance, Australian provider BinaryLane says it assists its verified account holder through the account’s normal support path, and cannot provide third-party access to another customer’s server. See its hosting recovery guidance for its own process.

If the host confirms that the hosting plan sits under the designer’s reseller account, it may be unable to make you the account owner or share another customer’s files. Ask whether the designer can be contacted through the reseller, whether a migration or site export is possible with the registrant’s written authority, and whether any backups are available. Keep the request specific: you need to know whether a full website backup can be provided, what it contains, and whether email is part of the same account.

If you regain control of cPanel or another hosting panel, preserve before you edit. Ask the host how to generate or download a full backup of the site files and database. Keep a copy in a business-controlled, secure location. If the site includes customer, health, payment or booking information, do not send that data to a new developer until you have confirmed the authority, security and transfer method.

If you can open cPanel but its password reset option is missing or points to an old email, contact the hosting provider that supplies the service.

Reset WordPress Admin Access Safely

If you can access WordPress, first use the normal Lost your password? link and send the reset to an email account the business controls. Once you are back in, create an admin user for the business, save a fresh backup, and remove old access only after checking who needs it for legitimate work.

If the admin email belongs to the former developer but you control the hosting account, WordPress documents a phpMyAdmin password reset. Only follow these steps if you are authorised to administer the website and have hosting or database access. Before changing a database, download a backup or ask the host to create one. In cPanel, open phpMyAdmin from the Databases area, select the WordPress database, and locate the user table. Its usual name is wp_users, but the prefix can differ: WordPress explains that $table_prefix in wp-config.php sets the prefix for the database tables. Use the table name configured for that site, not a guess.

  1. Open the users table and find the account by its user_login value.
  2. Edit that row and find the user_pass field.
  3. Replace the field value with a new strong password, then select MD5 in the function menu for that field.
  4. Save the row, test the login, and immediately set a strong password from the WordPress profile screen.
  5. Update the account email to a business-controlled address and create a separate admin user for the business if appropriate.

This method follows the current WordPress.org password reset instructions. WordPress warns that using phpMyAdmin carries a risk of data loss, and recommends seeking help if you are unsure. If you do not know which database or user row is correct, stop and ask the hosting provider or a qualified WordPress professional rather than editing tables by trial and error.

If you have no hosting, file or database access, you cannot use phpMyAdmin to reset the WordPress admin. The public website does not expose the database or server controls. Continue with the registrar and host recovery steps, and preserve what you can from public pages while you wait.

Save Content While the Website Is Still Online

If the pages are publicly visible but you have no login, use the Wayback Machine to see whether older copies already exist. Enter the domain or a specific URL, choose Browse History, and inspect the available capture dates. You may be able to retrieve page text and images from a snapshot even if the current site later disappears.

If a page is live now, you can capture it with the Internet Archive’s Save Page Now tool at web.archive.org. It saves a single page per submission. It does not archive an entire site, and the Archive does not guarantee a complete backup. Some pages or resources may not be captured. Save the important pages one by one, including the home page, service pages, contact details and any pages that contain unique business copy.

A Wayback capture is a view of public content, not a WordPress export. It does not give you the theme, plugins, customer records, form submissions, database, private media, email, analytics history or working checkout. It may omit images, scripts, fonts and parts of pages. Do not treat a capture as a complete backup or as proof that you own every piece of content. Use it as a reference for rebuilding text and visible page structure, and recover the actual files and database from hosting backups whenever possible.

Also save copies of business-owned materials you already control: original photos, logos, page copy, brand files, product descriptions, PDFs, menus and service information. Preserve the original files and dates. Avoid scraping or copying private customer information from the site. If a content or copyright question is disputed, get advice before reusing material.

When the Website Cannot Be Recovered

If the designer, registrar and host cannot provide the source files or a usable backup, rebuilding may be more practical than waiting indefinitely. First decide whether you still control the domain. If you do, you can build a replacement on a new hosting account and point the domain to it when it is ready. The old files may be lost while your business address remains the same.

If you cannot recover the domain, the business may need a new address. Check with the registrar about expiry and dispute status before assuming the name is lost. If it cannot be returned, register an alternative domain that fits the business, update the website and business profiles customers use, and tell existing customers where to find you. If you use business email on the old domain, plan how to keep messages and customer contact working before changing the domain.

There is no reliable flat recovery or rebuild price without knowing what can be reused. Cost depends on the number of pages, whether content and images survive, the platform, integrations, online payments, booking flows and whether the site needs new copy or design. A recovery assessment should separate a technical migration from a full redesign. For a reference point on new small-business website packages, see our Adelaide web design pricing guide. Those published build prices are not a quote for website recovery or takeover work.

Before a replacement goes live, make a list of the old URLs that matter and keep a copy of each page’s content. Where you control the old domain, ask your new provider to preserve important URLs or create appropriate redirects. If you do not control the old domain, you cannot safely assume you can redirect it. Do not publish a duplicate copy of an old site until you have checked that you have the right to use its text, images and code.

Prevent the Next Lockout

Once the urgent work is done, put every important asset under business-controlled accounts. The designer can receive a collaborator login with only the access they need. They should not be the only person who can renew the domain, reset the host password or create a CMS administrator.

AssetBusiness controlWhat to check
DomainBusiness or eligible legal entity is the registrantBusiness controls registrar login, recovery email and renewal payment
DNSBusiness has an owner or administrator loginKnow where nameservers and DNS records are managed
HostingAccount is in the business name or has business owner accessKnow the host, billing contact and backup process
CMSBusiness has its own administrator accountUse an individual login for each provider, not one shared password
BackupsCopies are stored outside the live hosting accountCheck when the last backup ran and whether it can be restored
Connected toolsBusiness has owner access to analytics and platform accountsReview users, recovery email and two-factor authentication

Put the handover duties in the contract: who controls each account, what access the client receives, when the domain or files must be transferred, how backups are provided, and what happens if the project ends early. Our web design contract guide explains the clauses to review. If you are still choosing a provider, read the web designer red flags checklist before signing. That article is about prevention; this page is for recovery after the relationship has already stalled.

Finally, test your own access before there is a crisis. Sign in to the registrar and host, confirm that recovery emails reach a business-controlled mailbox, and download a fresh copy of the backup. If a designer is the only person with an account, ask for the handover while they are still available.

Frequently Asked Questions

Can I get my website back if my web designer has disappeared?

Recovery depends on who is recorded as domain registrant and who controls hosting. Identify the providers and ask each to verify you through its recovery process. If the designer controls an account, no instant transfer is guaranteed. Preserve public pages and seek available backups while following the provider’s process.

Who owns my .com.au domain if my designer registered it?

For .com.au, registry registrant details identify the licence holder. auDA permits a developer to register for a client with explicit written permission, using the client’s details and ABN. If the designer’s details appear, ask the registrar about a change of registrant. Contact auDA if your ABN was used without permission.

How do I transfer a .com.au domain from an unresponsive designer?

Check whether you are the registrant. A registrar transfer keeps the registrant the same and requires the auDA authorisation code. A change of registrant moves the licence to someone else and has separate eligibility requirements. Start with the registrar. auDA complaints go there first, and an upheld complaint does not transfer the domain to you.

Can I reset my WordPress admin password without the designer?

Yes, if you have authorised access to the hosting account or database. WordPress documents resetting a user’s password through phpMyAdmin by editing the correct users table and the user_pass field. Back up the database first and do not guess which table or user to edit. If you have no hosting, file or database access, a public website alone does not let you reset its WordPress administrator password.

Can I rebuild my website from the Wayback Machine?

You can use archived pages as a reference for some visible copy and layout, but they are not a complete backup. Save Page Now captures individual pages and may miss images, scripts or other resources. It does not recover the WordPress database, customer data, forms, email, code, plugins or hosting. Ask the host for a full backup first, and use Wayback captures only as a fallback source for public content.

Conclusion: Recover the Accounts, Then Decide What to Rebuild

When a web designer stops responding, do not treat the website as one account. Check the domain registrant, contact the registrar through its official process, then identify the host and any CMS access you still control. For a .au domain, use the current auDA process and distinguish changing registrars from changing registrants. For WordPress, reset an admin only with authorised hosting or database access. Save public pages if the site is still live, but do not mistake an archive snapshot for a working backup.

This article was written by Ewen Zhang, Founder and Principal Engineer at DreamoonTech. You can learn more about the team on our about page. If you need a second opinion on what is recoverable, DreamoonTech can discuss the next steps for a website migration and ongoing maintenance. Read about our website maintenance and migration service, or contact us to discuss a website takeover. We can assess what exists before recommending whether to migrate, repair or rebuild.

Need help taking over a website?

We can help you work out what is recoverable, discuss a website migration and hosting, and plan the next step without assuming a rebuild is necessary.

Talk to DreamoonTech