# Domain, hosting and SSL explained A domain is the address, hosting serves the files and HTTPS protects data in transit. These are related services with different ownership and renewal arrangements. Moving a website to another host may require changing web DNS records while leaving the company’s email records intact. A padlock does not certify that a company is trustworthy or that its application is secure in every respect. When reviewing account access, distinguish ownership from a temporary permission grant. A developer may need access to configure a project without becoming the only person who can renew its domain. Record the intended long-term owner and confirm that recovery information is controlled appropriately. Do not publish those private details in the website’s repository or public documentation. During a domain or hosting move, test more than the root address. Open an actual service URL, follow an alternate-host link and inspect a missing path. Confirm that secure access and redirects preserve the destination a visitor intended to reach. Check the form separately because its processing route may have different configuration from static pages. A successful homepage load is a useful first observation, but it is not evidence that every connected service, mailbox or dynamic endpoint survived the change. ## Understand the three separate jobs A domain name is the memorable address people use to reach a service. Registering it gives the registrant rights to use that name under the registrar’s terms for a registration period. The domain does not, by itself, contain a website or a mailbox. Those functions need services connected to the address. Hosting provides the files or application that visitors receive. A static host can serve prepared HTML, images and other assets. A more dynamic application may run code and communicate with storage while processing a request. Both can use the same kind of public domain name; the address does not tell you how the underlying site is implemented. HTTPS protects the connection used to exchange data with a website. People often use SSL as a familiar label for certificate-based web security, although modern secure web connections use TLS. The practical owner-level question is whether the real public URLs load securely and whether certificate management is correctly configured. A secure connection does not establish that all application logic is safe or that every claim made by a business is true. ## Know what DNS changes affect DNS connects a domain with the services that handle its traffic. A website move may require updating the records used for web traffic. Email may use other records pointing to a separate mail provider. Treating all DNS entries as obsolete during a web migration can disrupt unrelated services that the business still needs. Before a change, record the relevant existing configuration and identify the purpose of each item. If you do not know what a record does, investigate it before deleting it. Keep the scope of a migration limited to the services actually moving. A new web host does not automatically require moving the business mailbox. Check the desired public address as well. Decide how the main domain and its www variant should behave, and preserve paths when a host-level redirect is needed. A visitor following a link to a service page should not lose that context merely because they used the alternate hostname. Configuration should be verified on the actual deployed site rather than inferred from a dashboard checkbox. ## Establish ownership and renewal responsibility The business should know which account controls the domain, which account controls hosting and who is responsible for renewals. Use accounts that can remain under the owner’s control after the delivery relationship ends. Administrative access can be granted appropriately without leaving the business dependent on an undocumented personal account. Create a small register with domain name, registrar, renewal date, hosting project and responsible person. Store recovery information securely and keep private account details out of public source files. The ordinary project documentation can identify needed accounts without exposing passwords or secret tokens. Consider an illustrative consultancy moving its introductory website to a static hosting service. The developer prepares the new site and updates the web-related configuration. The consultancy retains its domain registration and existing mail provider. The deployment should check public pages, HTTPS and enquiry handling while confirming that email-related records were preserved. Three connected services remain three separate responsibilities. Ask about costs using the same distinction. Domain registration and renewal can be recurring items; hosting depends on the selected service and usage; business email may have its own subscription. Free static hosting does not make the domain or mailbox free. Nor does it imply unlimited dynamic processing for an application added later. At handover, verify that the owner can locate each account and explain what it controls. This understanding is more useful than memorizing technical acronyms. It helps the business renew the right service, authorize a safe migration and ask a future provider precise questions without accidentally treating the website, domain and email as one inseparable product. ## Practical checklist - Keep registrar access - Document DNS settings - Check HTTPS on real URLs **A concrete example:** Moving a website to another host may require changing web DNS records while leaving the company’s email records intact. **A boundary to keep clear:** A padlock does not certify that a company is trustworthy or that its application is secure in every respect. ## Your next step [Tell Orvunweb about your project](/en/start-a-project/) ## Related reading - [One-time website fees and ongoing expenses](/en/blog/one-time-website-fees-and-ongoing-expenses/) - [What it means to host a website on Cloudflare](/en/blog/what-it-means-to-host-a-website-on-cloudflare/) - [Is business email part of website hosting?](/en/blog/is-business-email-part-of-website-hosting/) - [Business website service](/en/services/business-website/) - [Compare packages](/en/pricing/) ## Related services - [Business website](/en/services/business-website/) --- Locale: en Canonical: https://orvunweb.com/en/blog/domain-hosting-and-ssl-explained/ Updated: 2026-09-16 - [MDN — Domain names](https://developer.mozilla.org/en-US/docs/Learn_web_development/Howto/Web_mechanics/What_is_a_domain_name)