Skip to content

Home / Blog

Checklist

Digital Assets Register: Domain, Hosting and Email Logins

Digital Assets Register: Domain, Hosting and Email Logins

A digital assets register is one document that lists every online asset your business depends on: the domain, DNS, hosting, email, website admin accounts and connected services. For each one it records who owns it, where it renews and where the login is kept, though not the password itself. It takes an afternoon to build, and it stops a departing developer or employee from taking your website or email with them.

Lost access is one of the most common and most avoidable problems small businesses face. The domain was registered by a freelancer who no longer answers, the hosting renews on a former employee’s card, or nobody knows which company manages the DNS. This checklist shows what to record, who should own access, and how to keep the register safe and current.

Why does a business need a digital assets register?

A business needs a digital assets register because its website and email depend on several separate accounts, often opened by different people at different times. When one of those people leaves, the knowledge leaves with them unless it is written down.

Typical situations a register prevents:

  • A domain registered in someone else’s name. The person listed as registrant is the legal holder of the domain. If that is your former developer, recovering the domain can take weeks. Our guide on recovering a domain registered by a former developer covers that case.
  • A renewal that fails silently. The card on file has expired, the reminder emails go to an inbox nobody reads, and the site and email stop on the same day.
  • Nobody knows where the DNS lives. The domain is at one company, the DNS at another and the hosting at a third, so a simple email change becomes a hunt.
  • Admin accounts nobody remembers. Old users with full access remain on the website long after the project ended.

What should a digital assets register record?

A useful register records, for every asset, what it is, which provider holds it, which account controls it, who in the business owns that account, and when it renews. Use the table below as your column list.

Asset What to record Where to find it
Domain Registrar, account login email, registrant name, expiry date, auto-renew on or off, card on file Your registrar’s client area; ICANN lookup tool
DNS Where the nameservers point, who can edit the zone, key records (website, MX, SPF, DKIM, DMARC) Nameservers in the domain settings; the DNS provider’s panel
Hosting Provider, plan, renewal date, client area and control panel logins, where backups are kept and for how long Hosting welcome email and client area
Email Provider (hosting mailboxes or a separate suite), admin account, list of mailboxes and who uses each Email admin panel or cPanel
Website Platform, every admin user and their role, paid plugin and theme licences and the account each one is under Website dashboard; licence emails
SSL Who issues the certificate and whether it renews automatically Hosting panel
Connected accounts Google Search Console, analytics, business profile, social pages, payment gateway, newsletter service, ad accounts Each service’s users or permissions page

Check the domain from the outside

Do not rely only on what someone tells you about the domain. ICANN’s registration data lookup tool shows the current registration data for a domain. In the results, look for the registrar name and the expiry date, and compare them with your register. Personal contact details are often hidden for privacy, so log in to the registrar account itself to confirm the registrant is your business.

Record the DNS separately

The DNS provider is the company whose nameservers answer for your domain, and it is not always the registrar. Write down where the nameservers point and list the important records. If the record names are new to you, our explainer on DNS records covers A, CNAME, MX and TXT in plain language.

Who should own access to each account?

The business should own every account, and at least two trusted people inside it should be able to get in. Contractors should get their own limited access, never your master login.

  1. Register in the company’s name. Set the domain registrant to your business and keep the details accurate. ICANN’s page on registrants’ benefits and responsibilities says registrants must keep their contact information current and respond to registrar inquiries within 15 days.
  2. Use a company role address, with a backup. Open accounts with an address such as admin@ or it@ on your domain, not a personal mailbox. Because that address stops working if the domain lapses, add a recovery email on a different domain as well.
  3. Two owners, not one. Give owner-level access to at least two people, such as the owner and a manager, so one absence never locks the business out.
  4. Separate users for outsiders. Developers and agencies should get their own user accounts with only the permissions they need. In Google Search Console, for example, a removed owner can re-verify ownership unless you also delete their verification tokens, so removing the user alone is not enough.
  5. Pay with a company card. Renewals on personal cards fail when the person leaves.

How do you store the register safely?

Store the register as a normal company document, and keep the passwords in a password manager. The two are separate on purpose: the register can be read by more people than the passwords.

  • Passwords in a password manager. Use a shared business vault, so access can be given and removed per person.
  • Two-factor authentication everywhere. Turn it on for the registrar, hosting, email admin and website admins, and store the recovery codes in the vault.
  • No passwords in chats or email. WhatsApp messages and old emails are where leaked logins are usually found.
  • Limit who can edit. Keep the file in a company account, not someone’s personal drive.
  • Keep an offline summary. A printed page with providers, account emails and support contacts, without passwords, helps when the email itself is down.

When should you review and update the register?

Review the register fully once a year, check renewal dates every quarter, and update it on the day anything changes. The start of the year is a natural moment for the full review.

Update it immediately when:

  • someone who had access joins or leaves (change shared passwords, remove their users, move ownership)
  • you change registrar, hosting or email provider
  • you add a new site, domain or paid plugin
  • a card used for renewals is replaced

For your website budget, the register doubles as a list of renewal dates. Our guide to yearly website running costs shows how to turn it into a budget.

How does Start Bigger make the register easier to keep?

Keeping domain, hosting and email with one provider means fewer rows in the register and one place to check them. When you register a domain with Start Bigger, it is registered in your own name as the registrant, and all your services and invoices sit in one client area. As our domains policy explains, auto-renew is on by default, the renewal invoice is sent 30 days before expiry, and you can get the transfer (EPP) code from the client area when you want to move the domain to another registrar.

On hosting plans, you can download a full backup of your account from cPanel at any time, which is worth noting in the register as your own copy. You can search for a name or check renewal details on our domains page.

In short

  • A digital assets register lists every online asset, its provider, the controlling account, the owner and the renewal date.
  • Record the domain, DNS, hosting, email, website admins, SSL and connected accounts.
  • The business owns every account, at least two people have owner access, and contractors get limited users.
  • Keep passwords in a password manager with two-factor authentication, never in the register itself.
  • Review yearly, check renewals quarterly, and update the day anyone joins or leaves.

Frequently asked questions

Should the register contain passwords?

No. The register records what each asset is, who owns it and where the login is kept. The passwords themselves belong in a password manager with a shared business vault, protected by two-factor authentication. That way the register can be shared more widely than the passwords.

Who should hold owner-level access?

At least two trusted people inside the business, such as the owner and a manager. Developers, agencies and freelancers should get their own user accounts with only the permissions they need, which you can remove when the work ends.

What if our domain is registered in a developer's name?

Then the developer, not your business, is the legal registrant. Ask them to change the registrant to your company or to transfer the domain to an account you control, and do it while the relationship is still good. If that is no longer possible, follow the recovery steps in our dedicated guide.

How often should we update the register?

Review it once a year in full, check renewal dates every quarter, and update it the same day someone joins or leaves, or whenever you change a provider. A register that is a year out of date is almost as risky as having none.

Is a spreadsheet good enough?

Yes, for most small businesses. What matters is that the columns are consistent, the file is stored in a company account rather than a personal one, and access is limited to the people who need it.

Read next

Jordan & Gulf

Does Server Location Matter? Germany, the Gulf and Speed

An honest look at what a server in Germany means for visitors in Jordan and the Gulf: what distance really adds, when it matters, how caching and a CDN reduce it, and how to measure it yourself.

Ready to start, or have a question first?

We answer on WhatsApp Saturday to Thursday, 9:00 am – 9:00 pm Amman time (GMT+3)

WhatsApp