concept Domains & DNS
Domain name
A domain names a place in DNS. It is neither the complete URL nor the site files or hosting account.
What it means
A domain name is a name in the hierarchical Domain Name System (DNS), such as example.com. It can be used to find information needed to reach a website or other service. Registering a name gives the registrant rights to that registration under a contract; it does not buy the hosting machine or the website's files. Registrant responsibilities
The name itself is not a complete URL. https://www.example.com/help is a URL: it includes a scheme, a hostname and a path. example.com is a domain name, and www.example.com is a subdomain used as a hostname in the example. DNS and web requests
Try it
Example — follow a name through its hierarchy. Switch between the three fixed names, inspect a boundary, and change the separately configured services. The result distinguishes the name itself from DNS data and a prepared website; no registration or availability lookup occurs.
Name hierarchy explorer
Change a child label without confusing a name with a working website.
Changing www changes a child name, not the supplied registration boundary example.com.
- DNS root (.)
- com
- example.com
- www.example.com
| Item | State / result | Why it matters |
|---|---|---|
| Full name | www.example.com | A name, not a URL with scheme/path/query. |
| Registration boundary | example.com | Supplied by the fixture, never inferred from the last two labels. |
| DNS | Not configured in fixture | Registration does not create every useful DNS record. |
| Website | Not established | An address record alone does not establish content or HTTPS. |
Fixed local examples only. No availability, registration, DNS or website check.
About this model
Read labels from the root toward the left. The registration boundary is explicitly supplied for each example: example.com or example.co.uk. It is not calculated by taking the last two labels. Internationalized names and registry eligibility are outside this scene.
Read the article’s primary sources for protocol rules and implementation-specific limits. This scene has no network access.
Compare www.example.com with shop.example.com. Only the child label changes; the supplied registration boundary remains example.com. Now select shop.example.co.uk: this fixture explicitly supplies example.co.uk as its registration boundary. Taking the last two labels would produce co.uk, which is not the intended result here. Real boundaries must come from the relevant registry's rules or an appropriate maintained data set, not a universal dot-counting rule.
| Selection | What the scene reveals | What it does not establish |
|---|---|---|
| Child label | A name below the supplied registration boundary | A separately registered domain |
| Registration boundary | The boundary explicitly supplied for this example | Availability, ownership or the rules of every suffix |
| DNS root | The root represented by the final dot | A website or an HTTP request |
| Address record configured | A separate mapping has been supplied | Content, a working server or valid HTTPS |
The website-ready option adds DNS, hosting and TLS readiness as stated fixture conditions. It does not discover those conditions from the name. Reset returns to www.example.com, the child label and name-only context. Internationalized names, public-suffix discovery and registration eligibility are outside this example. DNS hierarchy Registration roles
What registration controls
A registrant usually manages renewal, contact information and the delegation to authoritative DNS through a registrar. The registrar and registry operate different layers of registration. DNS records live in the relevant zone run by a DNS operator, which may be the registrar, host or another provider. Registration process
| Thing | Example | Job |
|---|---|---|
| Domain registration | example.com | Keeps the name registered under an agreement |
| DNS record | www address or alias | Directs a lookup toward a service |
| Web hosting | Static host or application server | Responds to web requests |
| URL | https://www.example.com/help | Identifies a web resource and access scheme |
Different organizations can provide each part. Moving hosting can leave the registration untouched; moving a registrar does not, by itself, move a running site. Editing a DNS record can change where browsers connect without transferring ownership of the domain. Routing with DNS
Why DNS is not the website
DNS returns records such as addresses or aliases. It does not contain your complete HTML, images or site application. The browser contacts a web endpoint after obtaining routing information. Website contents and HTTPS configuration must still be present at the destination.
A domain can also identify mail services and other resources. Changing the website's address record is a different operation from changing mail exchange records. A DNS configuration is not automatically safe to replace wholesale when changing hosts.
In practice
Keep registrar credentials, renewal notices and recovery contacts under your control. Record which DNS provider is authoritative before you edit anything. For a new site, confirm whether you need both example.com and www.example.com; they can be configured separately. For any move, preserve email records and validate the actual content and TLS certificate at the destination. DNS traffic routing
Common misunderstanding: a domain that resolves successfully is not proof that the server will display the intended site. Resolution, HTTPS and application routing are separate steps.
Key takeaways
A domain name is part of a naming hierarchy. Registration, authoritative DNS and a website are separate responsibilities, even when one company sells them together. Read the boundary for the particular name, and verify the service behind it rather than treating a familiar-looking hostname as evidence of a working site.
Frequently asked questions
Editorial questions, answered from the sources listed for this article.
Does registering a domain automatically create a website?
No. Registration establishes rights and responsibilities for the name under the applicable agreement. DNS records and a serving environment still need to be arranged; a provider may bundle these services but they remain distinct.
Is the registrable domain always the last two labels?
No. The registration boundary depends on the suffix and its rules. The local examples supply their boundaries explicitly; this article does not implement a general public-suffix or internationalized-name validator.
Sources & model boundaries
Primary references used for this explanation. The interactive example is an educational model, not a live check.
- ICANN — Information for domain name registrants
Registrant contracts and management. Registrant–registrar relationship and domain maintenance obligations.
Checked .
- ICANN — Domain name registration process
Registrant, registrar and registry roles. Registration gives rights to a name under a contract, distinct from website content and hosting.
Checked .
- Amazon Route 53 — Routing traffic to resources
Public hosted zones and records. Records in the authoritative hosted zone associate hostnames with hosting resources.
Checked .
- RFC 1034 — Domain Names: Concepts and Facilities
Sections 3 and 4. DNS name hierarchy, labels, root and zone boundaries; not a universal registration-boundary algorithm.
Checked .