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.
Hosting fundamentals
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
Choose a provider only after deciding who will manage the domain, DNS, certificate, backups and future migration.
FAQ
No. A domain can be registered before hosting. You connect it later by changing DNS records or nameservers.
Sometimes, but not always. Treat registration, hosting and certificate terms as separate items and verify renewals for each.
Yes. A registrar transfer changes who manages the registration; a DNS change can point the existing domain to another host without a transfer.
Possible causes include the wrong hostname on the certificate, incomplete validation, mixed HTTP content, an expired certificate or stale DNS.
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.