The website is working, but the owner cannot say who controls the domain, where DNS is managed, or which supplier receives the hosting bill. Those gaps often stay invisible until a renewal, provider change, or unexpected outage turns a routine question into a search through years of email.

A website account inventory should make the operating arrangement understandable without collecting passwords into a spreadsheet. Its purpose is to connect each essential service with business ownership, authority, renewal, recovery, and technical dependencies. It is a map for decisions and handoffs, not a secret store or proof that every account is secure.

Separate the name, the directions, and the destination

A domain registration, DNS service, and website hosting perform different jobs. They may be supplied by one company, but that does not make them the same service. Changing one can affect the others, and a single invoice can conceal several distinct responsibilities that somebody needs to understand.

Think of the registered domain as the name the business uses under its registration arrangement. The registrar handles that registration relationship. DNS publishes information used to locate relevant services. Hosting operates the environment serving the website. Email may be hosted elsewhere again, even when its addresses use the same domain name.

NIST’s September 2013 Secure DNS Deployment Guide explains DNS roles, name servers, and records including mail-related records. Those architectural distinctions help explain why a website move deserves dependency review. The guide is not a recommendation to copy its historical product settings into a current hosting account.

Ask the responsible providers to explain the arrangement in ordinary language. Who manages registration? Who controls authoritative DNS? Where does the website run? Who operates email? A useful record answers each separately, even when the provider name happens to repeat. Do not assume that the developer who edits pages automatically controls every layer.

Start with a service map, not a folder of screenshots

List the public website addresses and the services that support them. Include the principal domain, relevant additional domains, DNS, hosting, email dependencies, backups, and essential integrations. Distinguish the production service from testing or retired arrangements so an old account does not look like the live environment merely because it has a familiar name.

For each service, identify its purpose and the business activity affected if it stops. A secondary domain may redirect customers from older materials. A backup subscription may protect an important recovery route. An integration may deliver enquiries to staff. These relationships explain why a seemingly unused renewal can matter, or why an old service may genuinely be ready for review.

Use a stable reference for the service and record where authorized people can find the provider’s account information. Do not copy passwords, authentication codes, secret keys, or full payment details into the map. The inventory can point to an approved credential-management process without reproducing its contents.

Discuss the website environment through Motta Industries’ web hosting service where relevant. The discussion should identify what a hosting arrangement includes and excludes. A hosting provider may not own the domain relationship, manage email, or retain every item needed for a complete business handoff.

Hands clip a cream sheet of geometric lines into an open blue binder beside orange folders and a laptop.

Record who has authority, not just who knows the supplier

A technical contact, billing recipient, administrator, and authorized contract holder can be different people. Record the relevant roles instead of writing one person’s name under owner and leaving the meaning unclear. The business needs to know who can approve a change, resolve a billing question, and use the provider’s legitimate recovery process.

For the domain registration, confirm the business’s relationship with the registrant and the registrar through authorized records. A name appearing in a public lookup is not a substitute for the actual account and registration arrangement, and privacy services can limit what public information reveals. Avoid turning an operational inventory into a legal conclusion about ownership rights.

If a supplier holds an account under a managed agreement, document the arrangement and handoff obligations. Do not assume the business can simply take over the supplier’s entire account, which may contain other customers. Equally, do not leave essential rights and exit responsibilities dependent on an undocumented personal understanding.

When authority is unclear, mark it unresolved and assign an appropriate business owner to investigate with the provider or adviser. Guessing that whoever receives the invoice must control the service can create a misleading record. A documented question is more useful than a confident answer that nobody has verified.

Capture renewal facts that someone can act on

Record the renewal date or billing cycle, the responsible budget owner, and the approved route for checking current status. Distinguish a recorded date from evidence that payment will succeed. Automatic renewal depends on an operating account and valid arrangements; the presence of a setting does not eliminate the need for ownership and review.

Identify where notices go and who monitors that destination. An important renewal warning sent to a former employee’s mailbox is not a dependable process. Establish an authorized current recipient and a backup responsibility, while keeping any change within the provider’s supported procedure and the business’s approval process.

Use the record to prevent duplicate or accidental services, not to cancel unfamiliar items impulsively. Before retiring a subscription, establish what depends on it and who can authorize the decision. A label such as old hosting may conceal an email dependency or a domain redirect the company still needs.

Keep contractual scope and recurring costs connected to the service description. A renewal for infrastructure is not necessarily a maintenance agreement for application code. A support plan may have limits that matter during an outage. The inventory should help an owner ask the right questions before urgency narrows the available options.

Make DNS dependencies visible without inviting experiments

DNS records can support different functions under the same domain. Website and email arrangements should therefore be reviewed together before a change to authoritative DNS. A provider migration that preserves the visible homepage can still interrupt another service if the transition ignores records outside the web destination.

The November 1987 Domain Names concepts standard, RFC 1034, describes zones, authoritative information, delegation, and caching. These concepts explain why control is distributed and why an observed response alone may not describe every relevant part of the arrangement. It is foundational architecture, not a current provider-specific migration recipe.

Record who maintains the authoritative configuration and where an authorized current configuration record is kept. Have qualified administrators explain any planned change and its dependencies. This article does not recommend editing records, replacing name servers, or deleting unfamiliar entries as a way to tidy the inventory.

Include a note about other teams that must be consulted. Email, verification services, and connected applications may require coordination with different owners. The inventory is valuable because it exposes those relationships before a rushed migration, not because it lets an unprepared owner bypass the people responsible for technical changes.

A woman in rust points to a geometric sheet in a blue binder as a man in blue listens beside a laptop.

Plan how the record remains available during trouble

If the only service map is inside the same workspace that becomes unavailable, it may not help when needed. Choose an approved, appropriately protected location and a practical fallback for authorized people. Limit access because even an inventory without secrets can reveal sensitive details about the business’s operating arrangements.

NIST’s May 2010 contingency planning guide discusses business impacts, recovery planning, contacts, and exercises. It addresses federal information systems, so use relevant planning principles proportionately rather than assuming its procedures are mandatory for every small business. The useful question is whether your record supports the recovery decisions your business actually needs.

Imagine a fictional upholstery workshop whose website and usual enquiry mailbox are unavailable. Can an authorized person identify the responsible providers and contact routes without relying on that mailbox? Can they explain which services are affected? A short discussion can reveal missing references without making real account changes or simulating an attack.

Record what the discussion establishes and what remains uncertain. Finding a provider’s support address is not proof that the business could complete account recovery or restore service. Where verification is necessary, agree a safe, authorized process with the relevant parties instead of testing by locking someone out.

Keep operational records and content records connected

The website also depends on information about what has been built and published. Record where the business keeps approved assets, important custom-work documentation, and relevant subscription or license references. Clarify which materials belong to the business and which remain subject to provider terms rather than assuming every file has identical rights.

Connect that record to the person responsible for content updates. They may know which pages and enquiry routes matter most, but they should not need infrastructure credentials merely to explain those priorities. Good documentation lets different roles contribute useful knowledge without giving everyone administrative control.

For a future provider change, identify what a handoff must include: scope, authority, current service references, relevant configuration documentation, business dependencies, and approved materials. A folder of design files is not a complete operating handoff, while a complete handoff does not require exposing secret values in an ordinary project document.

Distinguish a fact from an assumption

Give important entries a simple evidence status. Confirmed from an authorized provider record is different from mentioned in an old email or believed by the former manager. This prevents a plausible story from becoming the basis for a consequential migration. Keep the reference useful without copying sensitive account material into a widely shared file.

When two records conflict, investigate the service actually in use. An old invoice can remain genuine while describing an arrangement that has been replaced. A supplier’s current explanation may still leave a contractual question unanswered. Record the disagreement and assign the appropriate owner to resolve it, rather than choosing whichever document is easiest to find. The inventory becomes more dependable when its limits are explicit and the next verification step is clear to another authorized person.

Give the inventory a maintenance owner

Assign someone to keep the record current when a provider, domain, billing contact, or important integration changes. Add a periodic review appropriate to the business. A beautifully formatted document from two years ago can be less useful than a modest table whose entries have been checked and whose uncertainties are visible.

For every material entry, note the verification source and review date. Separate confirmed facts from supplier statements awaiting clarification. Do not update the reviewed date merely because the file was opened. The next authorized person should be able to understand why the business believes an entry is correct.

Include this responsibility in a website maintenance discussion rather than assuming it belongs to whichever supplier answered the last email. The useful result is an understandable operating map, clear authority, and fewer surprises during change. Start with the domain registration, DNS service, hosting, and the people authorized to explain each. Reliable records should support decisions, not merely fill a binder.