A foundational reference on web hosting. Defines hosting as the service that stores a website's files on an always-on server and makes them reachable over the internet. Walks through the request flow: a visitor types a domain, DNS resolves it to the server's IP address, the browser requests the page, and the server returns the files that render as a web page. Distinguishes the roles of the server, the domain name, and DNS as the internet's address book. Describes what a hosting plan typically bundles — storage, bandwidth, an operating environment with a web server and database, email, SSL, and a control panel — and frames hosting as the foundation every other performance, security, and SEO concern rests on.
Every website lives on a computer somewhere. Web hosting is the service that provides that computer — a server — keeps it running around the clock, and connects it to the internet so anyone can reach the site. Without hosting, a website’s files have nowhere to live and no way to be found.
The server
A server is a computer optimized to store website files and respond to requests for them at any hour, from anywhere. Unlike a personal machine that switches off, a hosting server is built for continuous uptime, fast network connectivity, and handling many simultaneous visitors. A hosting provider owns and maintains these machines in secure, climate-controlled facilities called data centers, so a site owner does not have to run hardware themselves.
Domain, DNS, and how a page arrives
Three pieces cooperate to deliver a page, and it helps to separate them:
- The domain name (e.g.
example.com) is the human-friendly address people type. A domain is rented separately from hosting — it is the address, not the house. - DNS (the Domain Name System) is the internet’s address book. Servers are actually reached by numeric IP addresses; DNS translates the memorable domain into the IP where the site is hosted.
- The hosting server holds the files and returns them when asked.
The request-response flow ties them together:
- A visitor types the domain into a browser.
- The browser asks DNS which IP address that domain points to.
- DNS answers with the hosting server’s IP.
- The browser sends a request to that server for the page.
- The server processes the request and returns the files — HTML, CSS, images, scripts.
- The browser assembles those files into the page the visitor sees.
This entire exchange usually completes in a fraction of a second, and it repeats for every page and asset a visitor loads.
What a hosting plan includes
Hosting is sold as a plan bundling the resources a site needs to run. Common components:
- Storage — disk space for the site’s files, database, and media.
- Bandwidth — the volume of data the server may transfer to visitors over a period; busier sites need more.
- An operating environment — typically a web server (such as Apache or Nginx), a scripting runtime (such as PHP), and a database (such as MySQL) for content-driven sites and CMS platforms.
- Email hosting — mailboxes at the domain, on many plans.
- An SSL certificate — to serve the site securely over HTTPS.
- A control panel — a dashboard for managing files, databases, email, and domains without command-line access.
Plans differ mainly in how much of the underlying server is dedicated to one site and how much is managed on the owner’s behalf — the subject of Types of Hosting.
Why it is foundational
Hosting is the layer everything else depends on. Its speed shapes how quickly pages respond, its reliability determines whether the site is reachable at all, and its security posture is a site’s first line of defense. Those outcomes ripple outward into user experience and search visibility — see Uptime and Website Performance. Choosing hosting well is choosing the ground the rest of a site is built on.
- Web hosting
- Server
- Domain name and DNS
- Request-response flow
- Bandwidth and storage
- Hosting plan
More Guides
Run disciplined SEO A/B tests in seven steps — one metric, two variations, randomized segments, run to significance, track, analyze the winner, and iterate.
Build a topic cluster in seven steps — select and score a pillar, validate it, map subtopics, align to intent, architect internal links, publish, and measure.
Prepare your site for AI search in five steps — content architecture, entity consistency, E-E-A-T, structured data, and machine-readable structure.
Get your content cited by AI in seven steps — answer capsules, link-free extraction, original data, digital PR, community presence, consistent messaging, and tracking.
A seven-step walkthrough for setting up Google Search Console on a new site — property type, DNS verification, sitemap, GA4 link, users, URL checks, and a monitoring routine.