Thirty Days of Hosting Research: What We Learned

If you are choosing hosting for a new or existing site, verify five things before paying: who controls the domain and related services, whether the platform fits, whether HTTPS is handled, whether backups can be restored, and what renewal and transfer involve. This hosting research roundup found that server space alone does not answer those questions. If your current service passes them and its terms are clear, keeping it—or postponing a purchase—is a reasonable outcome.

Map the services you are paying for#

ICANN explains that a domain name is not the same as a website. Hosting and email are separate services connected to the domain (About Domain Names). Record the company and account that manage each one:

• domain registration and renewal;
• website hosting; and
• email, if it is connected to the domain.

Keep the login details, account contact information, and renewal dates in one secure record. Do not assume that moving or cancelling hosting also moves the domain or email service.

Check platform compatibility before comparing plans#

Write down what the site needs to run, such as its content-management system, site builder, or other required platform. Then check the host’s current documentation or ask support whether the service supports those requirements. A storage allowance or a low introductory charge does not demonstrate compatibility.

Avoid treating any software requirement as permanent without checking the current documentation. The relevant test is whether the selected service supports the platform your site uses under the plan and conditions you intend to buy.

Treat HTTPS as a baseline#

Let’s Encrypt explains that unencrypted HTTP traffic can be viewed or modified while it is in transit (Why All Websites Should Use HTTPS). Confirm that HTTPS is supported and ask who handles certificate setup and renewal.

Record what happens if a certificate needs attention or renewal fails. HTTPS should be part of the launch and maintenance plan, not an optional extra to investigate after the site is live.

Ask how backups become a working recovery#

The UK National Cyber Security Centre recommends backing up website and business data, keeping more than one copy where practical, and checking that restoration works (Backing up your data). Before signing up, ask:

• What exactly is included in a backup?
• How long are backups retained?
• Can you download a copy?
• What are the steps to restore the site?
• Can restoration be checked before there is an emergency?

A statement that backups exist is not the same as a successful restore. Keep more than one copy where practical, document the recovery steps, and verify that the process works.

Read renewal and exit terms#

ICANN advises registrants to understand registrar terms, renew before expiration, and keep contact details current (Renewing Domain Names). Before paying, record the first-term and renewal charges for each service, cancellation conditions, domain-transfer rules, and how site data can be exported or downloaded.

Save the relevant terms and calendar the renewal dates. If the provider does not clearly explain how you would recover your data or transfer the domain, pause before committing. If you later move, retain access to the domain account and a usable backup until the replacement service is operating.

A practical decision rule#

For a new site, proceed only after platform compatibility, HTTPS responsibility, backup recovery, service ownership, and renewal terms are clear. For an existing site, do not switch solely because another plan lists more storage or features. First identify the specific gap and confirm that a move would improve it.

The research supports a checklist and a recovery plan. It does not provide current prices, speed measurements, uptime testing, or a performance verdict for any provider. Treat provider statements as claims to verify in documentation or by testing the relevant process, especially restoration and data retrieval.