Domains, DNS and SSL in plain English
Your domain is the name customers remember. DNS tells their devices where to find the services attached to that name. An SSL/TLS certificate helps their browser establish an authenticated, encrypted HTTPS connection to your website. All three need to work for a visit to succeed.
You can buy these services together or from different suppliers. What matters is that your business retains control and knows who fixes each part.
Your domain: the address you keep
A domain such as example.com is registered for a renewable period. It is separate from the website files and from the company hosting them. You can normally move your website to a new host while keeping the same domain.
Register the domain in the correct business name, keep account access available to authorised staff and make sure renewal notices reach an address someone monitors. A supplier can administer the registration for you without becoming the registrant itself.
Enable suitable account protection and keep a recovery route that does not rely entirely on the domain working. Our domain name guide covers ownership, renewal and naming decisions in more detail.
DNS: the directory connecting your services
The Domain Name System publishes records for your domain. An A or AAAA record connects a hostname to an IP address. A CNAME points one hostname to another. MX records identify incoming email servers, while TXT records can carry email policies and ownership checks.
That means your website and email can use the same domain while running at different providers. Moving the website should not require changing the mail records unless you are also moving email.
DNS answers are cached. A TTL states how long a record may remain in a cache, so changes can appear at different times for different users. Keep the previous service available during a planned transition rather than cancelling it as soon as you save a new record.
SSL and TLS: the secure connection
The term “SSL certificate” remains common, although modern secure web connections use TLS. A valid certificate covering your hostname lets the browser verify the server's identity as part of establishing HTTPS.
The connection protects information in transit. It does not prove the business is trustworthy, remove malicious plugins or secure information after it reaches the server. An encrypted connection and a well-maintained application are both necessary.
Certificates must renew successfully. If your host manages renewal, ask whether monitoring catches failures and whether every relevant hostname is covered. See SSL certificates explained for certificate choices and limitations.
What happens when a customer opens your website?
- The customer enters your web address.
- Their device obtains the DNS answer, possibly from a cache.
- The browser connects to the destination and establishes HTTPS.
- The server returns the page and the browser loads its resources.
A failure at each stage looks different. An expired registration may disrupt the domain. A wrong DNS address sends traffic to the wrong destination. A certificate mismatch triggers a connection warning. A broken application can still fail even when DNS and TLS work correctly.
Keep one record of responsibility
Write down the registrar, DNS provider, web host, certificate manager and email provider, together with their support contacts. Keep credentials in a password manager and document which people are allowed to approve changes.
If you prefer these tasks to sit with one team, ResaHost's domain service and web hosting can be discussed together. The useful outcome is a maintained website with clear ownership of the underlying services, rather than a collection of accounts nobody remembers.