What happens when someone opens your website?
A visitor enters a domain name, DNS helps locate the service responsible for that domain, and the browser requests the website over HTTP or HTTPS. The hosting platform processes that request and returns the page, assets or application response.
A domain name and web hosting are separate services. You can keep the same domain while changing hosting providers by updating the relevant DNS records. See our Domain Name Guide for domain ownership and DNS basics.
Client, server, IP address and DNS basics
This original Plus2Net video explains the basic client-server model, IP addressing, DNS and front-end/back-end concepts. The hosting market has changed considerably since it was recorded, but these networking fundamentals remain useful.
Shared, managed, VPS, cloud and dedicated hosting solve different needs
| Hosting type | Typical fit | Main trade-off |
|---|---|---|
| Shared hosting | Small websites, basic CMS sites and low-complexity projects | Low cost, but fewer resources and less control |
| Managed hosting | Teams that want the provider to handle more updates, backups or platform maintenance | Convenience at a higher price and with platform-specific limits |
| VPS | Applications needing more control and dedicated resource allocation | More administration responsibility |
| Cloud hosting | Applications that need flexible scaling, managed services or distributed infrastructure | Pricing and architecture can become more complex |
| Dedicated server | Specialized workloads requiring full control of a physical server | Higher cost and greater management responsibility |
Choose hosting for your software stack, not only for the operating-system label
Older hosting guides often reduced the choice to “Linux hosting vs Windows hosting.” That distinction still matters for some applications, but modern hosting can include containers, managed runtimes, serverless platforms and services where the underlying operating system is largely hidden from the site owner.
Before buying a plan, confirm support for what your site actually uses:
- PHP, Python, Node.js, .NET or another runtime.
- MySQL, PostgreSQL, SQL Server or another database.
- Required PHP extensions, libraries or server modules.
- Scheduled jobs / cron tasks.
- SSH or deployment access if your workflow needs it.
- CMS-specific requirements such as WordPress version and plugin compatibility.
.php does not prove the server runs Linux, and many modern sites hide file extensions completely.
Disk space and bandwidth are only part of the resource picture
The original Plus2Net article correctly separated storage from bandwidth. A site can use little disk space but still serve a large amount of traffic, or store many files that are rarely downloaded.
Also check:
- CPU or compute limits.
- Memory limits.
- Concurrent-process limits.
- Database size and connection limits.
- File/inode limits.
- Monthly data transfer or fair-use rules.
- Upgrade options when the site grows.
Optimize images and other media so users download only what the page needs. For practical performance work, see Fast Loading Pages and Core Web Vitals.
Website hosting and email hosting do not have to be on the same server
A domain such as example.com can use addresses like support@example.com
while the email itself is hosted by a separate mail provider.
DNS MX records direct mail to the chosen provider. Modern business email setups should also consider SPF, DKIM and DMARC according to the provider's instructions.
Do not choose a web host only because it advertises “unlimited email accounts.” Reliability, spam protection, storage, deliverability and account security are usually more important.
Ask how the site is protected and how it will be recovered
- HTTPS: TLS certificates should be easy to provision and renew.
- Backups: know how often backups run, how long they are kept and whether you can restore them yourself.
- Isolation: understand how shared accounts or workloads are separated.
- Updates: know which software the provider maintains and which updates are your responsibility.
- Access control: use strong passwords, MFA where available and limited administrative accounts.
- Recovery: document what happens after accidental deletion, compromise or server failure.
Good support is more valuable when something is already broken
Before committing, check:
- Support hours and channels.
- Whether technical support is included in your plan.
- Response expectations for urgent issues.
- Status-page and outage communication.
- Migration assistance.
- Whether you can export your site, database and backups if you leave.
Keep control of the domain, website files and data
Your domain should remain under an account controlled by you or your organization, not only by the hosting company or developer. You should also know how to obtain a current copy of your website files, database and configuration if you need to migrate.
For the broader setup process, see How to Set Up a Website for a Small Business.
Questions to answer before choosing a host
- Does the plan support my application stack and database?
- What CPU, memory, storage, file and traffic limits apply?
- How are backups created and restored?
- Is HTTPS easy to configure?
- What security controls and MFA options exist?
- What support is included?
- Can I upgrade without rebuilding the site?
- Can I export my website and database easily?
- Does the provider have a clear status/outage process?
- Will the business retain control of its domain and DNS?
Buy enough hosting for the application you have, with a path to grow
Avoid choosing a plan only by advertised storage or an “unlimited” label. Application compatibility, reliability, backups, support, security and portability usually matter more over the life of a website.
