How to Document Your Website, Domain and Hosting Access

If your website was set up by a developer, former employee or third-party provider, could someone else still access your domain, hosting or business email? If the answer is unclear, your business may be exposed to avoidable disruption.

Businesses often focus on launching a website but forget to document how the website works and who controls it. Months or years later, a password is missing, a renewal notice goes to an old email address, or nobody knows where the domain was registered. Recovering access can then become stressful and time-consuming.

A clear access record gives your business a reliable reference point. It helps you renew services, work with support teams, change providers, recover from staff turnover and keep important digital assets under the business’s control.

What should be documented?

Your record should cover every service needed to keep your online presence operating. This normally includes the following:

  • Domain: the domain name, registrar, account email, renewal date and ownership details.
  • Hosting: the hosting provider, account email, plan details and access method.
  • Website: the content management system, administrator accounts, important plugins and the person responsible for maintenance.
  • Business email: the email provider, administrator account, mailboxes and recovery details.
  • SSL certificate: who manages HTTPS security and whether renewal is automatic or manual.
  • DNS: where the domain’s DNS records are managed and which services depend on them.
  • Backups: where website and database backups are stored, how often they are created and who can restore them.
  • Renewals and billing: renewal dates, billing contacts and the approved payment method or responsible person.

You do not need to document every technical setting in detail. The goal is to record enough information for an authorised person to understand what exists, who controls it and what to do next.

Separate ownership from day-to-day management

One of the most important distinctions is the difference between owning an account and managing it.

A web developer may build and update a website, but the business should normally retain control of its domain registration and essential accounts. A hosting provider may manage the server environment, but the business still needs to know which account contains the website and how authorised access is handled.

For a Nigerian small business or organisation, this distinction matters when a developer becomes unavailable, a staff member leaves, or the business wants to move its website to another provider. If all services were created under someone else’s personal email address, the business may have difficulty proving ownership or recovering access.

Use business-controlled contact details wherever practical. Keep the registrant or account-owner information accurate, including the organisation’s name and a monitored business email address. Do not use an employee’s personal email as the only recovery option for a critical service.

Create a simple digital asset register

A spreadsheet or secure document can work well for smaller organisations. Create one row for each important service and include fields such as:

Field What to record
Service Domain, hosting, WordPress, email, DNS or another service
Provider The company or platform responsible for the service
Account identifier Username, customer ID or account email, without exposing sensitive information unnecessarily
Purpose What the service supports, such as the main website or staff email
Renewal date When the service must be renewed
Responsible person The authorised person who monitors or manages it
Recovery method The business-controlled email, phone or authentication method used for recovery
Notes Important dependencies, support instructions or recent changes

Do not treat the spreadsheet itself as a password vault. It should point to the relevant accounts and explain how they fit together. Store passwords and recovery codes in a reputable password manager or another secure system designed for sensitive information.

Record how the services connect

Many access problems happen because a business has recorded individual services but not their relationships.

For example, a domain may be registered with one company, while its DNS is managed through the hosting account. The website may be hosted in one location, but business email may depend on separate DNS records. Changing one setting without understanding these connections can interrupt the website or email.

Write a short plain-language description of the setup. It might explain that:

  • the domain is registered with a particular provider;
  • the domain points to the hosting service through its DNS settings;
  • the website runs on WordPress;
  • business email uses the domain and must not be disrupted when website settings change; and
  • backups are stored separately from the live website.

You do not need to use complex network diagrams. A basic service map, supported by a few notes, can help a new administrator or support team understand the arrangement quickly.

Document WordPress and website administration

If your website uses WordPress, record the website address, the administrator login location and the people who are authorised to manage it. Also note which themes, plugins or integrations are important to the site’s operation.

Do not share one administrator password with everyone. Create individual accounts where possible, give each person only the access they need and remove accounts that are no longer required. This makes it easier to review activity and change access when responsibilities change.

Document routine responsibilities as well. For example, note who reviews updates, checks backups, handles contact-form messages and responds when the website is unavailable. If managed WordPress support is used, record what the provider manages and what remains the business’s responsibility.

Protect the record itself

A document containing access information is valuable and must be protected. Avoid keeping passwords in an unprotected spreadsheet, sending them through ordinary email or storing the only copy on one person’s laptop.

Use these safeguards:

  • Store passwords in a reputable password manager or another controlled system.
  • Enable multi-factor authentication for domain, hosting, email and other critical accounts where available.
  • Keep recovery codes in a secure location that authorised backup personnel can access.
  • Limit access to people who genuinely need it.
  • Keep an offline or separately protected emergency copy of essential recovery information.
  • Review sharing permissions whenever an employee, contractor or agency stops working with the business.

Security is not only about strong passwords. It is also about making sure the right people can recover an account without giving uncontrolled access to everyone.

Track renewals before they become emergencies

Expired domains, hosting plans, SSL certificates and email services can affect customer trust and business operations. A renewal calendar reduces the chance that an important service will be overlooked.

Set reminders well before each renewal date. Use at least two authorised people for critical reminders, and make sure notifications go to a monitored business email address. Review billing details when staff or providers change, and confirm that the payment method is still approved.

Do not assume that a website provider automatically monitors every service. Confirm who is responsible for each renewal and record that responsibility in the asset register.

Review access after every major change

Update the documentation when you register a new domain, move hosting, change email providers, add an agency or transfer responsibility to another employee. Schedule a broader review periodically so the record does not become outdated.

A useful review asks:

  • Can the business identify the owner of every essential account?
  • Are the account email addresses and ownership details accurate?
  • Can an authorised person access the domain, hosting and email accounts?
  • Are former staff and contractors removed?
  • Are backups available and is the restoration process understood?
  • Are renewal dates and billing contacts current?

A practical starting point

If your records are incomplete, do not wait until everything can be organised perfectly. Start with the domain, hosting account, business email and WordPress administrator access. Confirm who owns each account, update the recovery details and record the renewal dates. Then document DNS, SSL, backups and supporting services.

For a business using Sonhosting for hosting, domain registration, business email or managed WordPress support, the same principle applies: understand which responsibilities are handled by the provider and retain clear, authorised access to the business’s essential digital assets.

The most useful access document is not the longest one. It is the one that is accurate, securely stored, understandable to an authorised colleague and reviewed whenever the business changes its people, providers or online services.