A domain and a website are different assets. The domain's registrant and registrar access determine who can change DNS; hosting, source files, and content may sit elsewhere. Build an inventory before a vendor relationship ends.

Check the real path

  1. Look up the domain registrar and confirm the business controls the registrant account and recovery email.
  2. List hosting, CMS, analytics, design, and source accounts with their administrators.
  3. Read the signed agreement for ownership, licenses, export, and unpaid-balance terms.
  4. Request a tested backup and a written transfer plan before revoking access or changing DNS.

Decide what to change

Do not change nameservers or cancel hosting until a replacement site and mail records are ready. If access is disputed, preserve documents and seek appropriate registrar or legal support rather than assuming a technical shortcut will resolve ownership.

Put it in the project brief

Before paying for a fix, ask the provider to name the affected page or workflow, the change they will make, how they will test it, and which dependencies or exclusions could change the estimate. Keep the baseline and the completed test so both sides can see what improved.

How ARCHV can help

ARCHV can help scope a new site and handover checklist. Domain disputes and legal ownership questions require the registrar or counsel. Share the current page and the problem through ARCHV's website estimate form. If you are an agency seeking delivery support, see the partner route.

Sources and related reading