If a web developer stops responding, protect the domain and the working website before redesigning anything. Preserve account access, record the current DNS and hosting state, make independent backups, test customer contact paths, and collect the information a replacement needs.

Do not change nameservers, cancel hosting, or reset every password at once. A rushed change can take down the site, email, forms, certificates, or other services that share the domain.

Immediate priorities: confirm the website and forms work, identify the domain registrar and registrant, preserve hosting and code, back up content and data, inventory DNS and email dependencies, secure business-controlled access, document missing work, and buy a bounded takeover assessment. Use qualified counsel for contract, payment, or ownership disputes.

Confirm the current customer path

From a device and network not already signed in, test:

  • The main domain with and without www.
  • Important service, product, location, and contact pages.
  • Contact, estimate, booking, application, and checkout forms.
  • Confirmation messages and internal delivery.
  • Phone links, email links, maps, payments, and scheduling.
  • Certificates and visible browser security warnings.
  • Mobile navigation and the primary call to action.

Record the date, results, screenshots, and any lost inquiries. If a form fails, publish a controlled alternative contact method without deleting the existing site.

Send a formal, concise contact request

Use the channels and notice method in the agreement. Identify the site, urgent operational issue, specific access or file needed, and a reasonable response deadline.

Try known company, project, billing, and support contacts. Preserve the correspondence. Avoid inflammatory public messages while facts remain incomplete.

Technical preservation can continue while you wait. Do not allow one missing response to become a lost domain or expired hosting account.

Find the domain registrar and registrant

Search company email, invoices, credit-card statements, password managers, and prior proposals for domain renewal notices. An ICANN lookup can help identify the registrar even when public registration details are private.

Confirm:

  • The registrar and account email.
  • The registrant or beneficial owner.
  • The expiration and automatic-renewal status.
  • The payment method.
  • Multifactor authentication and recovery access.
  • Transfer lock and nameservers.
  • Who can change DNS.

ICANN describes the registrant's management and transfer role in its domain registrant guidance. If the former provider appears as registrant, use the contract and qualified legal guidance rather than attempting an unauthorized takeover.

Record DNS before changing anything

DNS may control the website, business email, verification records, customer portals, subdomains, call tracking, and vendor services. Save the current record set and nameservers.

Do not point the domain to replacement hosting until the new provider has mapped email and other records. A website migration that silently stops employee email is not successful.

Identify and preserve hosting

Find the current host, plan, account owner, billing method, renewal date, server or project identifier, and administrator access. Keep the service paid while recovery is underway unless qualified security response requires a different action.

Download a backup where the platform permits, including files, database, configuration exports, redirects, and media. Keep an untouched copy under business control.

For hosted builders, export the content and data formats the platform supports. A builder export may not reproduce the original design elsewhere, but it can preserve copy, products, orders, customers, media, or blog entries.

Locate the source and editing system

The visible website might come from:

  • A Git repository and automated deployment.
  • A WordPress installation and database.
  • A hosted builder account.
  • An ecommerce platform and theme.
  • Files uploaded directly to a server.
  • A custom application with separate frontend and backend.

Ask whether the available source matches production and includes build instructions, packages, content, configuration, redirects, server functions, and integrations.

The article on website domain, code, and hosting ownership explains why each asset needs separate control.

Preserve forms, orders, and customer data

Export form submissions, orders, customer records, booking data, product data, blog content, and other business information according to approved privacy and security procedures.

Confirm where new inquiries are delivered. A website can display a success message while the notification goes to a former developer's address or a disconnected inbox.

Record export dates, counts, filters, and the platform used. Protect confidential data and do not send raw customer exports to an unevaluated replacement provider.

Recover analytics and search access

Identify Google Analytics, Tag Manager, Search Console, business profiles, advertising pixels, call tracking, consent tools, and any reporting dashboard.

Preserve historical access under the business's organizational account. Do not create a new analytics property merely because the old administrator is unavailable; that divides measurement history.

Export recent traffic, landing-page, query, conversion, and error data before a migration. A replacement needs evidence of what should not be lost.

Inventory licenses and recurring services

List themes, plugins, fonts, stock images, forms, scheduling, email, security, backups, CDN, translation, search, ecommerce, and other tools.

Determine whether each license belongs to the business, the former provider, or an agency plan. A working website may stop updating or lose premium behavior when an agency license ends.

Secure access in a controlled sequence

After the inventory is reliable, move administrative recovery and billing into company control. Invite replacement providers with named user accounts and minimum necessary permissions.

Rotate credentials that the former provider no longer needs, but preserve logs and update dependent systems. Avoid shared passwords where the platform supports individual access.

If the site may be compromised, use a qualified security response process. Do not let a new developer clean the only copy in place without backups and evidence preservation.

Separate unfinished scope from new requests

Prepare four lists:

  • Pages and functions that work and must be preserved.
  • Current defects or security problems.
  • Written deliverables the former developer did not complete.
  • New content, pages, or redesign ideas.

A replacement can estimate the current site more accurately when incomplete contract work is not mixed with a fresh wish list.

Ask for a takeover assessment

The first replacement engagement should confirm:

  • Domain, DNS, hosting, source, and platform access.
  • Independent backups and restoration path.
  • Technology, dependencies, licenses, and account ownership.
  • Current pages, forms, integrations, and search signals.
  • Security, update, performance, and accessibility risks.
  • Deployment or editing process.
  • Repair, migrate, rebuild, or maintain options.
  • Estimated hours and recurring costs for the next phase.

At Vertinus's $49.99 hourly rate, a simple accessible website review may take 4-12 hours, about $200-$600. A complicated WordPress, ecommerce, migration, or custom site may require 12-60 hours, about $600-$3,000, before repairs.

The companion website takeover cost guide explains the ranges by platform and condition.

Do not let urgency create a second lock-in

Warning signs include:

  • A replacement demands that the domain be transferred into its name.
  • It wants to cancel the old host before a verified backup exists.
  • It quotes a full rebuild without inspecting the site or evidence.
  • It creates new analytics and search accounts instead of recovering business access.
  • It cannot explain code, content, data, and license portability.
  • It makes DNS changes without mapping business email.
  • It requires a large open-ended payment because the situation is urgent.

Recover control before redesigning

The best immediate outcome may be boring: the site stays live, forms work, renewals are protected, the business controls its assets, backups are usable, and a new developer can deploy safely.

Once that foundation exists, decide whether to finish, repair, migrate, redesign, or rebuild based on business value.

Send Vertinus the current URL and the accounts you can access. We can scope a bounded website takeover at $49.99 per hour and identify the safest next step without taking ownership away from your business.