Every website needs two things before anything else works: an address people can type, and a server that answers when they do. This hub explains domains, hosting, DNS, SSL and CDNs in plain language, then points you to the detailed guide for each topic.
Learn. Build. Improve.
Simple guides that work.
Tools, resources & checklists.
SEO, AI, WordPress & more.
HOSTING & DOMAINS
Every website depends on infrastructure you rarely see: a domain name people type, DNS that points it to the right place, a hosting server that stores and serves the site, a security layer that encrypts connections and, often, a content delivery network that helps deliver files efficiently.
This guide explains each component in plain language — how they connect, what they do and what to consider when choosing or managing them.
THE BASICS
A website is a collection of files (HTML, CSS, JavaScript, images), usually a database holding content and settings, and software such as a CMS that ties them together. All of that has to live somewhere that is connected to the internet and switched on around the clock.
A web hosting service provides that infrastructure: servers, storage, network connectivity and the software needed to run a site. When someone visits your website, their browser sends a request to the server; the server processes it, runs any application code, fetches data and sends back the files needed to display the page.
Hosting providers also typically handle hardware, power, networking and varying levels of server management, so you can focus on the website itself. Learn more in our web hosting guide.
REQUEST FLOW
Loading a page takes a fraction of a second, but several systems work together to make it happen.
The visitor types an address or clicks a link.
DNS returns the IP address or destination for that name.
The browser opens a connection, usually secured with TLS.
The server runs code and gathers the requested content.
HTML, CSS, JavaScript and images are sent back.
The browser assembles and displays the page.
INFRASTRUCTURE GUIDES
Website infrastructure is made of connected components: where a site lives, how people find it, how connections are secured and how content is delivered. Explore each topic in depth.
Learn how web hosting stores and serves website files, databases and other resources, and understand the main factors involved in choosing hosting for a website.
Understand how virtual private servers provide dedicated virtualized resources and greater server-level control compared with typical shared hosting environments.
Learn how cloud infrastructure can distribute workloads across connected computing resources and provide flexible infrastructure for different website requirements.
Explore hosting environments designed around WordPress websites, including performance, security, caching, backups and WordPress-specific management.
Learn how domain names provide human-readable addresses for websites and how registration, DNS, nameservers and domain settings connect a domain to online services.
Understand SSL/TLS certificates, HTTPS, encrypted connections and why secure communication matters when visitors interact with websites.
Learn how Content Delivery Networks distribute cached website resources through geographically distributed edge locations to help deliver content efficiently.
Explore Cloudflare's role in DNS, CDN, security, caching and network services and understand how these technologies can sit between visitors and website infrastructure.
HOSTING TYPES
No hosting type is universally fastest or best; each suits different requirements, budgets and technical skills.
Many websites share one server's CPU, memory and storage. It is simple to start with and the provider manages the server, but resource isolation is lower, so busy neighbours can affect others. Often used for small business sites, blogs and portfolios.
A physical server is divided into virtual machines, each with allocated resources and its own operating system. You get more isolation and server-level control, with more configuration responsibility unless the plan is managed.
Websites run on virtualised resources drawn from a pool of connected servers. Many cloud setups allow resources to be adjusted as needs change, with billing models that vary by provider.
An entire physical server is reserved for one customer or organisation. It offers full hardware resources and control, and typically requires more technical management.
COMPARISON
A neutral overview of how the main hosting models differ. Actual features vary widely between providers and plans.
| Aspect | Shared | VPS | Cloud | Dedicated |
|---|---|---|---|---|
| Resource Model | Shared pool on one server | Allocated virtual resources | Virtual resources from a pool | Entire physical server |
| Isolation | Lower | Virtualised isolation | Virtualised isolation | Physical isolation |
| Control | Limited, provider-managed | Root/server-level access common | Varies by service | Full hardware and OS control |
| Scalability | Within plan limits | Upgrade allocated resources | Often adjustable on demand | Limited by hardware; upgrade or add servers |
| Typical Complexity | Low | Moderate | Moderate to high | High |
| Management Requirements | Mostly handled by provider | You or a managed plan | You, a managed service or platform | You or a managed service |
| Common Use Cases | Small sites, blogs, portfolios | Growing sites, custom stacks | Variable workloads, applications | Resource-intensive or specialised needs |
| Infrastructure Model | Multi-tenant server | Virtual machine | Distributed virtual infrastructure | Single-tenant hardware |
BEGINNER ESSENTIALS
A domain is like a street address; hosting is the building. They are different services that work together: DNS settings on the domain tell browsers where the hosting is. You can move hosting without changing your domain, or transfer a domain without moving your hosting.
The address people use to reach a website, such as example.com or example.in. You register it through a registrar, usually for a year or more at a time, and renew it to keep it.
The infrastructure where website files and databases are stored and served. It is a separate service, often from a different company, billed on its own terms.
DNS
The Domain Name System (DNS) translates human-readable domain names into the information computers need, such as IP addresses. DNS doesn’t host your website; it directs traffic and services to the right destinations.
A domain’s nameservers tell the internet which DNS provider holds its records. Those DNS records then define where each service lives:
Changes can take time to appear everywhere because resolvers cache records for the period set by each record’s TTL. See our domain names guide for more.
IMAGE PLACEHOLDER
DNS record management / domain architecture
Recommended ratio: 4:3 — replace this container with an Image widget.
ARCHITECTURE
A typical request passes through several layers. Not every website uses a CDN or security proxy, but many do.
Opens the site in a browser.
The address identifies the site.
The domain resolves to a destination.
Optional edge network may serve cached files or filter traffic.
Receives requests not served at the edge.
Application reads content and data.
The server returns the page and assets.
Renders the page for the visitor.
SECURITY
SSL (Secure Sockets Layer) was the original protocol for encrypting web connections. It has been replaced by TLS (Transport Layer Security), and SSL versions are now deprecated — but “SSL certificate” remains the common name for the certificates TLS uses.
A certificate, issued by a certificate authority, proves that a server is authorised for a domain and enables encryption. HTTPS is HTTP running over TLS: data exchanged between browser and server is encrypted and protected from tampering in transit.
Browsers show the connection state in the address bar and warn visitors when a certificate is missing, expired or invalid. HTTPS protects the connection; it doesn’t by itself make a website’s code secure.
IMAGE PLACEHOLDER
HTTPS / SSL certificate browser security illustration
Recommended ratio: 4:3 — replace this container with an Image widget.
CONTENT DELIVERY
A Content Delivery Network (CDN) is a group of servers in many locations, called edge nodes. It stores cached copies of cacheable resources — images, stylesheets, scripts and sometimes whole pages — and serves them from a location closer to each visitor, while your hosting remains the origin server.
Benefits can include faster delivery of cached resources, reduced distance to users, less load on the origin and additional network features such as DDoS mitigation. The impact depends on how much content is cacheable, where visitors are, and how the CDN is configured, so results vary. Read our CDN guide.
IMAGE PLACEHOLDER
Global CDN network diagram
Recommended ratio: 16:9 — replace this container with an Image widget.
CLOUDFLARE
Cloudflare is a company that runs a large global network offering web services including authoritative DNS, CDN caching and security features such as DDoS mitigation and a web application firewall. When configured as a proxy, it sits between visitors and your origin server.
It isn’t required for every website, and how it should be set up depends on your hosting, caching needs and application. Settings like SSL mode and cache rules need to match your origin to avoid issues. See our Cloudflare guide.
IMAGE PLACEHOLDER
Cloudflare DNS / CDN / security dashboard
Recommended ratio: 16:10 — replace this container with an Image widget.
Manage DNS records on Cloudflare's authoritative nameservers.
Cache static resources at edge locations near visitors.
Traffic filtering, DDoS mitigation and firewall rules.
WORDPRESS HOSTING
WordPress runs on PHP and a MySQL or MariaDB database, so hosting needs a supported PHP environment, a reliable database and enough resources for your traffic and plugins. Many providers offer WordPress-focused hosting with server-level caching, automatic backups, core updates and security tooling.
Performance also depends on your theme, plugins, images and whether you use a CDN. Check resource limits such as PHP workers, memory and storage before choosing a plan. Explore our WordPress hosting guide and WordPress guides.
IMAGE PLACEHOLDER
WordPress hosting infrastructure
Recommended ratio: 4:3 — replace this container with an Image widget.
PERFORMANCE
Hosting affects server response time through CPU, memory, storage speed, database performance and server configuration. Network latency depends partly on the distance between visitors and the server, which caching and a CDN can reduce.
But hosting is only one part of the picture. Heavy code, large images, unnecessary plugins and third-party scripts can slow a site on even well-resourced hosting. Measure before upgrading, and see our website speed guides for the full picture.
IMAGE PLACEHOLDER
Website speed / server performance report
Recommended ratio: 16:10 — replace this container with an Image widget.
HOSTING & SEO
Hosting doesn’t determine rankings on its own, but infrastructure supports several things search engines and users care about. A site that is frequently unavailable can’t be crawled or visited; slow server responses affect page experience and how efficiently crawlers can fetch pages; and HTTPS is expected on modern websites.
Reliable hosting, good mobile performance, sensible server configuration and correct status codes all help keep pages accessible. Server location matters mainly for latency to your audience, which a CDN can offset. No hosting company can guarantee better rankings — content and overall site quality still matter most. Learn more in our website SEO guides.
SECURITY BASICS
Security is shared between your hosting provider and you. Providers usually secure the physical and network layers; the website and accounts are often your responsibility.
BACKUPS
Backups are how you recover from mistakes, failed updates, hacked sites or hosting problems. A full backup includes both files (code, themes, uploads) and the database (content and settings); some tools back these up separately.
Choose a frequency that matches how often the site changes, keep copies in off-site storage away from the hosting account, retain several versions, and test restoration occasionally — a backup you’ve never restored is an assumption, not a plan.
IMAGE PLACEHOLDER
Website backup and recovery workflow
Recommended ratio: 4:3 — replace this container with an Image widget.
CHOOSING HOSTING
Start with requirements, not hosting types. Consider these factors, then pick the model and provider that meets them:
01 Website Type
02 Expected Traffic
03 Resource Requirements
04 WordPress or Other CMS
05 Ecommerce
06 Server Control
07 Scalability
08 Backup Requirements
09 Security
10 Server Location
11 Support
12 Budget
13 Migration Requirements
14 Technical Expertise
DOMAIN NAMES
You register a domain through a registrar, which records it with the registry for that extension (.com, .in and so on). Registration lasts for a set period and must be renewed; if it lapses, the domain enters grace and redemption periods before it may become available to others, and websites and email tied to it stop working.
Your registrar lets you set nameservers and, if they host DNS, manage DNS records. Many offer domain privacy to limit public contact details where rules allow. Domains can be transferred between registrars, usually with an authorisation code. After DNS changes, allow time for propagation as caches refresh.
IMAGE PLACEHOLDER
Domain registration and DNS management interface
Recommended ratio: 16:10 — replace this container with an Image widget.
MIGRATION
Moving to a new host is manageable with a checklist. Test on the new server before changing DNS, and keep the old hosting active until everything is confirmed. Lowering DNS TTL in advance can shorten the switchover.
IMAGE PLACEHOLDER
Website hosting migration workflow
Recommended ratio: 16:10 — replace this container with an Image widget.
CHECKLIST
Review this list at launch and periodically afterwards.
AVOID THESE
Plan limits on CPU, memory or PHP workers can cause slowdowns as a site grows.
Relying only on a host's backups, or never testing them, leaves recovery uncertain.
Websites and email stop working. Enable auto-renew and keep contact details current.
A wrong record can take a site or email offline. Double-check changes.
Browsers flag insecure pages, and expired certificates cause warnings.
Slow response times often go unnoticed without monitoring.
Each plugin adds code, maintenance and potential conflicts.
Test on the new host before switching DNS.
Moving nameservers without copying MX and TXT records can break email.
Uptime monitoring alerts you to outages quickly.
FAQ
Concise answers to the most common infrastructure questions.
ALL GUIDES
KEEP LEARNING
Design sites that perform well on any hosting.
Servers, APIs and application architecture.
How infrastructure supports search visibility.
Caching, CDNs and performance tuning.
Content management platforms and their hosting needs.
AI tools for managing and improving websites.
Continue exploring hosting, domains, DNS, SSL, CDN and infrastructure guides to understand how websites are connected, secured, delivered and maintained online.