Domain Registration vs Website Hosting: What's the Difference?

A registered name is not a hosted website

Registering a domain gives the named registrant the contractual right to use a particular name for a defined registration term, subject to registry and registrar rules. It does not buy a physical server, a website design, a database or a permanent ownership interest in the word itself. A visitor may type the domain into a browser, but the name must still resolve through DNS to a service that can answer the request. If no website has been configured, the result may be an error or a registrar's parking page rather than the business's content.

This distinction matters when a quotation says “domain included.” Ask whether the quoted line covers the initial registration only, who appears as registrant, what renewal costs after any promotional period, and whether DNS management is included. A domain can remain registered even while its website is offline. Conversely, website files can remain on a paid hosting account after the domain has expired, yet customers may be unable to reach them by the familiar name.

Who handles the registry, registrar and reseller

For a generic extension such as .com, a registry operates the extension and accredited registrars arrange registrations under the applicable agreements. A reseller may provide the customer-facing storefront while the accredited registrar remains responsible for registrar services. ICANN's registration-process guidance distinguishes these roles and says the agreement with the registrar governs fees, renewals and transfers. For a Malaysian .my name, MYNIC operates the country-code namespace and publishes its own registrant and category rules. These are different governance arrangements, not competing types of hosting.

The practical question is which organisation can actually change the registration, recover an account, update contact information or authorise a transfer. A hosting company may sell a domain as a bundle but still rely on a different registrar. Keep the registrar name, registrant record, customer account identifier and recovery channel in a company-controlled inventory. An invoice issued by a web developer is not, by itself, evidence that the business is listed as the domain registrant.

DNS connects the name to services

The Domain Name System provides the routing information that helps clients locate services for a domain. A registrar can register the name while an independent DNS provider hosts its authoritative zone. The nameserver delegation identifies which servers answer for that zone. Inside it, different records serve different purposes: A and AAAA records associate names with IP addresses; CNAME points one name toward another name; MX identifies mail exchangers; and TXT can carry verification or email-authentication policy data. The records do not themselves store the website.

A small company could register its name through one firm, use Cloudflare for DNS and use a third provider for its website. That arrangement is technically normal, provided the parties know their boundaries. Before changing nameservers, export or record every relevant DNS entry, especially MX, SPF, DKIM, DMARC, subdomains and verification records. Replacing the entire DNS zone with only a website A record can unintentionally break working mail or third-party services even though the homepage appears to load.

Hosting is the service that answers web requests

Web hosting supplies computing resources and software that deliver site content when a browser requests it. On a traditional cPanel-hosted website, the web server reads files from a document-root directory; a dynamic application may also execute code or query a database. cPanel's documentation explains that the document root is the location from which the server serves the domain's public files. Changing that directory does not automatically move the files. Other platforms may publish from a managed build or application service rather than a conventional folder.

Hosting capacity is not defined by the domain extension. The same .my or .com name can point to shared hosting, a managed website platform, a virtual private server or a static hosting service. Compare actual resource limits, software support, backups, restore procedures, uptime terms and support responsibility. A domain purchase cannot answer whether the website needs PHP, a database, staging, image optimisation or regular maintenance; those questions belong to the hosting and website scope.

A domain can be used without a public website

Some organisations register a domain first to protect a chosen identity or to prepare business email. They may create addresses at that domain before publishing any public pages, or reserve the name while legal and brand checks are completed. That is different from assuming a blank website is operational. A parked or placeholder page is not a completed customer-facing website, and a DNS record alone does not establish an email mailbox. Decide which services should exist now and which are intentionally deferred.

There is also no technical rule that a website must be hosted by the registrar. The registrar's control panel may offer forwarding to an existing website, but forwarding is not the same as storing the site under that domain. If a company uses a social profile while preparing a website, document the temporary contact route and avoid telling customers that a full site exists before it has been tested and published.

Business email is a separate decision

An email address uses the same domain name after the @ sign, but email delivery is governed by its own provider, mailbox accounts and DNS records. MX records direct incoming mail toward the configured mail service. The provider may also require SPF, DKIM or DMARC records and client settings. Cloudflare's official email-DNS guidance illustrates the separation between a mail-host A record and MX routing, and notes that mail-only hostnames should not be sent through an ordinary HTTP proxy. A functioning website is not proof that incoming email works.

Consider a business that moves its website from one host to another while keeping Microsoft 365 or another mailbox provider. The correct website cutover may involve only web-related DNS records, leaving MX and authentication records untouched. Before any change, send and receive controlled test messages, confirm the expected sending identity and keep a copy of the existing DNS zone. Never delete an old mailbox because the website now displays correctly; message storage and site files have separate retention and migration requirements.

Registration does not include HTTPS automatically

HTTPS requires a web service configured with a certificate valid for the requested hostname, along with suitable server and redirect behaviour. Buying the domain establishes neither the certificate nor its installation. Some hosts automatically issue and renew certificates, while others require configuration or offer different coverage for subdomains. The domain's DNS must also point toward the intended service so that validation and public requests reach the right place. Check both the bare domain and the www hostname if both are meant to work.

A browser padlock indicates an encrypted connection to the hostname under the browser's trust checks; it does not certify that a company is reputable or that the information on the page is accurate. Test real HTTPS responses and certificate renewal behaviour separately from the domain invoice. If a site moves hosts, verify certificate issuance on the destination before directing customer traffic there, and keep a rollback plan for an unexpected certificate or redirect problem.

Bundled purchase versus separate suppliers

Buying registration and hosting together can simplify billing and initial support. A single provider may set up nameservers and website hosting automatically, which can be convenient for a small team. The trade-off is that the same customer account may control several critical services, and the bundle may have different promotional and renewal conditions for each component. A package described as “free domain” can still have a later renewal charge or eligibility restrictions. Read the actual order summary rather than inferring the long-term price from the banner.

Separate suppliers may give a business more choice about hosting features and future migration. That flexibility requires an accurate inventory and a named administrator who understands which support team owns each problem. Neither structure is automatically safer or cheaper. Evaluate account recovery, two-factor authentication, backup access, export rights, service-specific renewal dates and the effort of changing providers. Hostinger and InMotion's educational explanations are useful secondary examples, not evidence that OnHypp offers identical bundle features.

Understand the renewal clocks

A domain registration has an expiry date and renewal rules; a hosting subscription has its own billing period, suspension conditions and cancellation process. These dates can differ even when the initial purchase was made on one invoice. MYNIC advises .my registrants to renew before expiry and explains that, after expiry, a registrar-dependent auto-renew grace period may be followed by redemption and pending deletion. A domain may be suspended during the grace period, and restoration charges can apply later. Do not treat the maximum grace period as guaranteed uninterrupted service.

Hosting expiry is a different event. A host may suspend website access or eventually remove data under its terms, even while the domain remains registered. Record the renewal owner, approved payment method, reminder destination and escalation contact for each service. Review these details before staff leave or a card expires. For continuity, confirm how to export site files and databases and how long backups are retained, instead of assuming that a registrar's domain renewal also preserves website data.

Control and access are more important than the invoice

A business should be able to identify the legal registrant, the registrar login owner, the DNS administrator, the hosting account owner and the person authorised to approve changes. These may be five distinct roles. An outside developer can have limited delegated access without becoming the sole custodian of registration recovery credentials. Use organisation-controlled recovery addresses, multi-factor authentication where supported and an access register that survives employee turnover. If a provider only supports one administrator, agree on an emergency access procedure and document it securely.

Check the actual account and registration record, not only a screenshot of the domain in a control panel. When a project ends, require a handover of credentials through an approved secure method, DNS export, hosting backups, certificate renewal information and renewal dates. Domain transfer rights and registrant changes follow applicable registrar or registry policy; a developer cannot promise an immediate transfer in every circumstance. This operational control is a key difference between paying for a domain and retaining reliable use of it.

A hypothetical Malaysian small-business example

Imagine a Penang repair business called Kedai Contoh, a fictional name used only for illustration. It registers a suitable domain through an eligible registrar and wants a five-page bilingual website plus three staff mailboxes. Its website designer builds the pages, a web host stores the files, a DNS provider publishes the records and an email provider manages the mailboxes. The business appoints one internal person to own renewal reminders and another as a backup contact. None of those decisions follows automatically from the domain purchase.

The team first checks that the domain is registered to the intended business entity and that the selected extension's eligibility rules are met. It then confirms the host supports the planned pages and forms, asks who operates the mail service and writes down the exact DNS records each supplier needs. Before launch it tests the English and Bahasa Melayu pages, HTTPS, contact path, mobile display and both inbound and outbound mail. The example shows how several services combine; it is not a claim about a real OnHypp customer or an available package.

A safe order for setting up a new site

Start with the intended name and a basic trademark and identity review, then verify availability and category eligibility with the relevant registry or registrar. Record the registrant accurately, choose secure account recovery and enable renewal reminders. Separately define the website requirements: pages, languages, contact method, accessibility, content ownership, software and backups. Choose hosting based on these needs, not merely because a domain was included. Ask the host for the exact destination records or nameservers before editing DNS.

Build and test the website in a non-public or controlled environment where possible. Only after content and forms are ready should the team configure the necessary DNS records, verify HTTPS and check the public pages from outside the hosting control panel. Keep the old DNS values for rollback. If email is already in use, explicitly preserve its routing and authentication entries. Document what was actually tested, who accepted the results and what remains pending; purchasing a domain is a milestone, not launch acceptance.

Moving hosting while keeping the same domain

A website can change hosting providers without changing its public domain name. The work typically involves copying site files and databases where relevant, configuring the destination, validating its application and adjusting the web-facing DNS destination. The domain registration may stay with the original registrar. Before the switch, test the destination using a safe preview method that does not interfere with the live site, confirm database compatibility, redirects, image paths, forms and HTTPS, and make a recoverable backup.

DNS changes can take time to be observed because resolvers cache answers according to their time-to-live and other behaviours. Do not promise an exact universal cutover minute. Monitor both the old and new hosting services during the transition, and avoid deleting the original account until important requests and data are confirmed at the destination. If the email provider is independent, do not change its MX records simply because the website moves. A host migration is not automatically a registrar transfer or a change of business ownership.

Changing the domain is a different project

Replacing the public name itself, for example from an old brand to a new brand, affects links, customer bookmarks, printed materials, email addresses and search-engine discovery. This is broader than moving the same name to a different host. Plan URL-by-URL redirects where appropriate, update internal links and canonical signals, revise verified business listings and preserve access to the old domain during the transition. Google Search documentation treats URL changes as a site-move concern rather than a mere server replacement.

Email deserves its own migration plan because addresses using the old domain may continue to receive customer messages. Confirm which old aliases or mailboxes must remain, how long they should be monitored and which external contacts need an updated address. Do not promise that search visibility or mail deliverability will transfer instantly. A business can keep the old domain registered as a redirect or for mail continuity, subject to budget and policy, even after the new website is working.

Diagnose which layer failed

When a site does not open, identify the symptom before paying for a new domain or changing all DNS records. If the registrar shows the domain expired or on hold, resolve registration status first. If authoritative DNS lacks the required web record, correct the zone at its actual DNS provider. If DNS points to the intended server but the browser shows a server error, inspect hosting, application logs and the configured document root. If only HTTPS fails, investigate certificate coverage, redirects and the host's TLS configuration.

A website outage and an email outage do not necessarily have the same cause. Test the domain's DNS delegation, the web hostname and the MX destination separately. Keep timestamps, exact error messages and a record of the last change so the right supplier can investigate. Avoid deleting working records while troubleshooting; a change made under pressure can turn a single broken page into a wider mail or service interruption. Where no access exists, ask the authorised account owner rather than attempting uncontrolled modifications.

Compare quotations by responsibility, not labels

For a fair comparison, ask each supplier to separate domain registration, DNS management, hosting resources, website creation, email hosting, certificate management, backups and ongoing support. For each line, note whether it is included, optional, billed separately or supplied by a third party. Compare the first term with the renewal term and confirm taxes, transfer charges, cancellation notice and restore costs only from the current written offer. Do not infer that “unlimited” marketing language removes fair-use, storage or inode restrictions.

Ask what the supplier will hand over at completion: registrar access, site source files, database export if applicable, content rights, DNS records and recovery documentation. Clarify whether maintenance includes updates, malware response, backup restoration or only server availability. The cheapest first-year bundle can be costly to operate if the business cannot recover access or move its content. Conversely, a modest site may not need a complex server. Select the smallest service combination that demonstrably meets the actual requirements.

A decision checklist for a first purchase

Before paying, be able to answer seven separate questions: What exact domain and extension are eligible and available? Who will be named registrant? Which registrar handles the registration? Who controls authoritative DNS? Which provider will serve the website? Who will operate business email? What are the renewal, backup and recovery arrangements for each? If any answer is unknown, mark it as an open item in the purchase brief rather than treating a bundle name as proof.

After purchase, verify the domain record and account recovery, then verify DNS, hosting and email individually against the agreed scope. Save a dated acceptance note with working URLs and the responsible people. Do not publish placeholder claims or assume Google will index a site because the domain exists. The useful outcome is a controlled, reachable service that the business can maintain and transfer when necessary—not simply a receipt showing that a memorable name was purchased.

When the domain is included in a hosting package

Some hosting quotations list a domain as a separate line while others include one eligible domain within the annual total. Neither structure changes the technical distinction between domain registration, DNS and hosting. The customer should check the exact domain extension, registered holder, included renewal period and what happens when the web hosting is cancelled. A combined price does not give the hosting company ownership of a customer's domain.

The allowance does not cover every premium or restricted extension; such names need their eligibility and additional cost confirmed before a quotation is accepted. Email hosting remains a separate requirement on the managed application plans.

Sources & further reading

Ready to explore a related service?

See the related OnHypp service and decide whether it fits your business needs.

Domains Email & hosting