Web hosting provides the infrastructure and services that make a website available online. Depending on the arrangement, it may include serving files, running applications and managing supporting systems.
Hosting is different from owning a domain name or maintaining the website's content. Those responsibilities can be bundled commercially while remaining distinct technically.
What does the hosting provider do?
The scope depends on the service. Some arrangements supply infrastructure with substantial customer responsibility, while managed platforms handle more of the operating environment.
Ask which tasks are included: backups, updates, monitoring, support and recovery. “Managed” is useful only when the actual responsibilities are clear.
Hosting versus domain registration
A domain name is an address registered through a registrar. Hosting is where the website is delivered from.
DNS connects the address with relevant services. A domain can remain with one provider while the website uses another hosting arrangement.
What affects reliability?
Delivery infrastructure, application behaviour and operational processes all matter. A service commitment should be read alongside its scope and exclusions.
A website can also fail because of a configuration change or expired dependency. Hosting quality does not remove every other maintenance responsibility.
What should backups provide?
Establish what is backed up, how frequently and how restoration works. A backup that cannot be restored within a useful process offers limited reassurance.
Include content, files and relevant application data in the discussion. Different platforms preserve different parts of the system.
What matters during a migration?
Identify the current services and their dependencies before changing them. Websites, email and other domain-linked services may use separate records.
Plan the move, verification and recovery approach. Avoid assuming that changing the website host also requires moving every account or service.
How should a business choose?
Begin with the website's functions, likely traffic, support needs and technical ownership. Compare services on those requirements rather than storage alone.
Also establish portability and exit arrangements. The business should understand how content, domains and operational access can be handed over.
What should be documented?
Record providers, responsible owners and recovery procedures without exposing credentials in ordinary project documents.
A clear operating model helps the business know who to contact and what to expect when something needs attention.
Further reading
For reference, see the supporting documentation. Explore related explanations of Domain name, DNS, Content delivery network, SSL certificate.
A practical example
Illustrative example: a company moves its website to a managed platform while keeping its domain registrar and email provider. The team changes only the required DNS records, checks the site and email separately and documents who owns each service.
Why it matters
Hosting underpins availability, but its value depends on a clear division of responsibilities. Understanding the arrangement makes maintenance and future changes more manageable.
