Hosting fundamentals

Domain, hosting and SSL explained

A domain gives people an address, DNS tells browsers where to go, hosting serves the files and an SSL certificate protects the connection. They cooperate, but they are separate services with separate failure points.

The four layers of a working website

1. Domain registration

The registration reserves a name such as example.com and records who controls it. The registrar provides renewal and nameserver settings; it does not automatically store the website.

2. DNS

DNS records translate the domain into destinations. An A or AAAA record can point to a server address, a CNAME can alias one hostname to another, and MX records route email.

3. Web hosting

The host stores or runs the site and answers requests for the configured domain. It may provide files, databases, PHP, caching, backups, email and a control panel.

4. SSL/TLS

The certificate proves that the server is authorized for the hostname and enables an encrypted HTTPS connection. It must cover every public hostname visitors use.

What happens when a visitor opens the site?

  1. The browser asks DNS for the address of the requested hostname.
  2. DNS returns the host or proxy destination currently published.
  3. The browser connects and requests a secure TLS session.
  4. The server presents a certificate valid for that hostname.
  5. After validation, the host returns the page and its assets over HTTPS.

A failure at any layer can make the whole site appear unavailable. That is why changing several layers at once makes migrations harder to diagnose.

Recommended setup order

  1. Register the domain in an account the site owner controls and enable account security.
  2. Create the hosting account and add the exact production hostname.
  3. Upload or deploy the site and test it using a temporary address when available.
  4. Lower DNS TTL before a planned migration, then publish the host's required records.
  5. Issue and validate SSL only after the hostname resolves to the correct endpoint.
  6. Redirect HTTP to HTTPS after the secure version works without certificate errors.
  7. Test the root domain, www hostname, forms, email routing and a real restore path.

Nameservers versus individual DNS records

Changing nameservers delegates the entire DNS zone to another provider. Changing an A, AAAA or CNAME record edits only a destination inside the current zone. A nameserver change can unintentionally affect email verification, MX records and subdomains if those records are not recreated first.

For a simple hosting move, editing website records is often easier to control than moving the whole DNS zone. Use the method documented by the host and keep an export or screenshot of the working records.

Domain transfer versus hosting migration

A registrar transfer moves management of the domain registration. A hosting migration moves the website files, database and application configuration. Neither operation requires the other. Keeping them separate reduces risk: point DNS to the tested new host first, monitor the site, and transfer the registration later only if there is a clear administrative reason.

SSL choices and renewal

Domain-validated certificates, including free automated certificates, can provide the same transport encryption as paid domain-validated products. Paid options may differ in validation type, support, warranty language or management tools. The practical questions are whether the certificate covers the required hostnames, renews reliably and can be replaced quickly.

Troubleshooting checklist

Ownership and recovery checklist

Keep the registrar, DNS, hosting and certificate accounts documented separately. Record renewal dates, recovery email addresses, two-factor authentication ownership and the people allowed to change production settings. Store an independent backup outside the hosting account. A technically correct configuration is still fragile when nobody knows who controls it.

Related guides

Compare after mapping the setup

Choose a provider only after deciding who will manage the domain, DNS, certificate, backups and future migration.

Compare hosting options

FAQ

Common questions

Do I need hosting before buying a domain?

No. A domain can be registered before hosting. You connect it later by changing DNS records or nameservers.

Does web hosting include a domain and SSL?

Sometimes, but not always. Treat registration, hosting and certificate terms as separate items and verify renewals for each.

Can a domain point to a new host without being transferred?

Yes. A registrar transfer changes who manages the registration; a DNS change can point the existing domain to another host without a transfer.

Why does HTTPS still show a warning after SSL installation?

Possible causes include the wrong hostname on the certificate, incomplete validation, mixed HTTP content, an expired certificate or stale DNS.

How long do DNS changes take?

Some resolvers update within minutes, but cached records can remain until their TTL expires. Plan changes before a migration and verify from more than one network.