imbahub
Menu +
US
Talk to us
IMBAHUB / Knowledge & guides

Who controls your domain and website accounts?

Separate domain registration, DNS and hosting first. They may involve three different suppliers. Record the account holders, responsibilities and recovery routes before planning a move. A CMS login does not automatically provide control of the domain.

Keep four responsibilities distinct

  1. Identify

    List registration, DNS, hosting and CMS separately.

  2. Verify

    Test access and secure recovery.

  3. Change carefully

    Move web traffic with explicit checks and a recovery plan.

Map four different functions

Domain registration associates the name with a registrant under the registration terms. DNS holds records directing services such as web traffic and email. Hosting serves the website. The CMS provides content editing. One login may sometimes cover several functions, but verify that arrangement rather than assuming it.

Consider a fictional business whose registrar, DNS provider and office email supplier are separate. Only the website is moving to new hosting. Changing nameservers without accounting for email records could affect more than the site. This is why an account inventory should precede the technical move, even when the visual redesign seems straightforward.

Build an inventory without exposing secrets

For each service, record the account holder, responsible person, billing contact and access recovery route. Store passwords and recovery codes separately in a secure system with appropriate access. The shared project document should indicate where the responsible person can retrieve them, rather than contain the secrets themselves.

Verify access in practice. Ask the responsible person to sign in and confirm the correct account without sending you their password. Check whether recovery depends entirely on a former employee’s private email. Invitation, delegation and permission options vary by provider, so use the actual account features available.

SystemQuestionEvidence
DomainIs the intended organization the registrant?Registrar account details
DNSWho can change the records?Confirmed permission
HostingWho operates and pays for it?Agreement and named contact
CMSWho can publish and correct changes?A tested user role

Keep email within the change plan

Inventory the current DNS records and identify the services using them. Have the technical owner describe exactly which records should change and which must remain. Moving a website does not always require changing registrar. Separate those operations when they do not need to happen together.

Assign checks for the website, forms and email after the change. Opening a page in your own browser does not prove that every connected service works. Avoid scheduling a sensitive change when nobody with the required permissions will be available to resolve an unexpected issue.

  • Confirm access before agreeing a move date.
  • Document affected records and a recovery plan.
  • Assign a contact for email as well as the website.
  • Avoid a single external individual being the only recovery route.

When account information is missing

Start with invoices, existing agreements and your organization’s IT contact. Registering a different name does not restore control over the name customers already use. Ask the relevant provider about its identification and recovery process. Resume migration planning once access is secure. This is an operational checklist, not a legal interpretation of every registration agreement or the rules for national domain extensions.

Questions, answered

Must we transfer the domain when replacing the website?

Not necessarily. Changing the appropriate DNS records may be enough. Decide after mapping the existing registration, DNS and hosting arrangements.

Should the agency receive our main password?

First check whether a separate user or delegated access is available. Grant the access the task requires and agree how it will be removed afterwards.

IMBAHUB

Let’s plan your website

Separate domain registration, DNS and hosting first. They may involve three different suppliers. Record the account holders, responsibilities and recovery routes before planning a move. A CMS login does not automatically provide control of the domain.

Talk to us
Existing English product interface with fictional demonstration content; reused for the US website.

Existing English product interface with fictional demonstration content; reused for the US website.