ServerField Server operations and website growth
Fundamentals For beginners Updated July 29, 2026

What is a domain?
How domain names, DNS, and URLs work — with examples

A domain is a memorable name used for websites and email. It is not the same thing as a URL, DNS, an IP address, or a server. We break down example.com and explain registration, costs, SEO, and safe operation.

Written and reviewed by the Finite Field Editorial Team Published: December 5, 2024 Last updated: July 29, 2026

Domain Name System

Connect a name people use
to a service endpoint

HOST NAMEshop.example.com
DNSName resolution
IP ADDRESS192.0.2.1
URL → host name → DNS → endpoint → web server

An illustration of resolving a name through DNS and connecting to an endpoint.

This article has no advertising or affiliate links. On July 29, 2026, we checked DNS terminology against RFC 9499, URL syntax against RFC 3986, top-level domains against IANA, JP domain names against JPRS, registration, renewal, and RDAP against ICANN, and SEO against Google Search Central. Prices, eligibility, and expiration conditions vary by TLD and provider.

In short, a domain is a name used on the internet. DNS looks up information such as IP addresses or mail destinations associated with the name, while servers provide web pages or email services. URLs, DNS, IP addresses, and servers work together but have different roles.

The 30-second summary

Register a name, use DNS to identify endpoints, and provide services on those endpoints

For example, in https://shop.example.com/products , example.com is the registered domain name, shop.example.com is the host name, and /products is the path. Registration alone does not publish a site: DNS, the server, and HTTPS must also be configured.

DomainA human-readable hierarchical name such as example.com
DNSA system for looking up IP addresses and mail destinations associated with names
URLA resource identifier that includes a scheme, host, and location
In one sentenceA memorable hierarchical name used for websites, email, and other services
How it differs from a URLA domain name can form the host part of a URL; it is not the entire URL
How it differs from DNSA domain name is a name; DNS is the system used to look up associated information
Configuration after registrationAuthoritative DNS, A, AAAA or CNAME records, a web server, a TLS certificate, and MX or TXT records when needed
Costs to considerRenewal, transfer, recovery after expiration, options, exchange rates, and tax as well as the first year
Safe managementCompany-controlled registration, multifactor authentication, automatic renewal, least privilege, change procedures, and monitoring
Checked onJuly 29, 2026

A domain is a hierarchical name used on the internet

A domain name consists of hierarchically arranged labels separated by dots and is used to identify websites, email, APIs, and other resources.

Instead of remembering numeric IP addresses every time, names such as finitefield.org and example.com are easier to communicate and can support a service's brand. In everyday speech, 'domain' and 'domain name' are often used interchangeably, but in DNS a domain can mean an entire branch of the namespace below a particular node.

Read www.shop.example.com from right to left

Follow the hierarchy from the TLD on the right toward the left.

.com is the top-level domain (TLD); below it, example.com is a commonly registered name. Further to the left, shop and www are lower-level names an administrator can create after registration. A fully qualified representation including the DNS root has a trailing dot, as in www.shop.example.com. , though ordinary interfaces generally omit that dot.

Be precise with the term 'root domain'

In web development, example.com is sometimes called the root domain, but the DNS root is the top of the namespace, represented by '.'. To avoid confusion, call example.com a registered domain name or, when referring to the top of its DNS zone, the zone apex.

How domains, URLs, DNS, IP addresses, and servers differ

These concepts appear together when a web page loads, but they have different roles. Rather than relying only on analogies such as addresses and phone books, distinguish what each represents and where it is used.

https://shop.example.com/products/42?color=blue#spec
httpsScheme
shop.example.comHost
/products/42Path
?color=blueQuery
#specFragment

↔ Scroll horizontally to view the table

Comparing domain names and related concepts
TermMeaning and roleExampleCommon confusion
Domain nameA name in the hierarchical DNS namespaceexample.comIt is neither the whole URL nor the server
URLA string identifying a resource, including a scheme, host, and pathhttps://example.com/about/A domain name can appear in the host part of a URL
DNSA system for looking up IP addresses, mail destinations, and other information associated with namesA, AAAA, CNAME, MX, TXTIt does not serve the web page itself
IP addressA numeric address used to identify network interfaces or destinations192.0.2.1, 2001:db8::1One name can resolve to multiple IPs, and multiple sites can share one IP
Web serverSoftware or an environment that receives HTTP requests and returns HTML, images, API responses, and other contentNginx, Apache, Cloud Run, and othersA separate layer from registration and DNS management
Host nameA domain name used to identify a network host or serviceshop.example.comNot necessarily a registration unit

DNS does not look up the entire URL

The browser extracts the host name from the URL and requests the needed records, such as A or AAAA. It does not send the path, query, and fragment to DNS to find the page. A fragment such as #spec is normally omitted from the HTTP request and used for a location within the retrieved page.

What happens between entering a URL and displaying a website

Actual requests can involve caches, CDNs, IPv4 and IPv6, proxies, HTTP/2, and HTTP/3, but the basic responsibilities can be divided into five stages.

  1. 01

    The browser parses the URL

    It identifies the scheme, host, port, path, query, and fragment. An omitted port is determined from the scheme's default and other context.

  2. 02

    DNS looks up the host name

    The device or browser checks its cache and, if necessary, queries a recursive resolver. The resolver responds from its cache or by querying authoritative DNS.

  3. 03

    Connect to an IP address

    A records provide IPv4 candidates and AAAA records provide IPv6 candidates. Some configurations follow aliases such as CNAME records.

  4. 04

    Authenticate the endpoint and protect the connection with HTTPS

    The browser verifies that the TLS certificate matches the requested host name and establishes an encrypted connection. A mismatched certificate causes a warning even when DNS is correct.

  5. 05

    The web server returns content

    The browser sends an HTTP request including the host, path, and query; the web server or application returns HTML, images, JSON, or other content.

Separate the layers when troubleshooting

Registration → delegation → DNS response → network → TLS → HTTP → application is a useful order to check. Saying only that 'the domain has not propagated' does not identify an expired registration, name server mismatch, incorrect A or AAAA record, DNSSEC failure, certificate issue, or web configuration problem.

Major domain categories: gTLDs, ccTLDs, and JP domains

The IANA Root Zone Database lists delegation information for top-level domains. Each registry's rules determine who can register which names beneath a TLD, eligibility, length limits, renewal, and transfer conditions.

gTLD

Generic top-level domain

Examples include .com, .org, and .net, alongside many newer gTLDs. A TLD's original intended use does not necessarily match its current registration requirements.

ccTLD

Country-code top-level domain

Examples include .jp, .uk, and .de. They are associated with countries or regions, and registration eligibility and required information vary by registry.

.JP

General-use and prefecture-type JP domains

Individuals and organizations with an address in Japan are eligible. Registration numbers are unrestricted and Japanese-language names are supported.

CO.JP

Organizational and geographic JP domains

Examples include CO.JP, OR.JP, AC.JP, and GO.JP. Eligibility depends on organization type; rules generally include one domain name per organization.

↔ Scroll horizontally to view the table

Examples for different uses
CategoryExampleTypical useWhat to check
Common gTLD.com, .org, .netBrands and services used domestically or internationallyRenewal price, trademarks, transfer, and recovery conditions
Country-code TLD.jp, .de, .ukSites primarily serving a particular country or regionResidence and eligibility, public information, and usage rules
General-use JPexample.jpSites for individuals, businesses, and organizations serving JapanJapanese address, characters and format, and designated provider
Organizational JPexample.co.jpCompanies registered in Japan and other eligible organizationsOrganization type, one domain per organization, and registrant identity
Japanese-language domaincafé.exampleAdvertising, local names, or a memorable secondary URLInput environment, email support, lookalike characters, and ASCII-compatible form

Do not judge trust or SEO by TLD alone

A .com name is not automatically safe, and an unusual TLD is not automatically disadvantaged. Consider the operator, content, HTTPS, renewal practices, history of abuse, and fit for the target region together.

Custom domains, subdomains, and subdirectories

When adding a site, decide whether it belongs on a separate custom domain, a subdomain, or a subdirectory. The names sound similar but differ in their contractual, DNS, and site-structure boundaries.

Comparing custom domains, subdomains, and subdirectories
ApproachExampleCharacteristicsCommon uses
Custom domainexample.comA name registered and renewed under a contract through a registrar or providerThe main site for a company, service, or brand
Subdomainshop.example.comA name created in DNS beneath a registered domain; it can point to a different serverShops, administration, APIs, or regional and product sites
Subdirectoryexample.com/shop/A URL path under the same host, configured at the web layer rather than in DNSArticle categories, product pages, and multilingual directories

A separate subdomain is not automatically a securely isolated environment. Design cookie Domain attributes, authentication, CORS, TLS certificates, search visibility, and administrative permissions. Conversely, a subdirectory need not use the same application; a reverse proxy can route it to a different system.

How to register a domain and compare costs

A domain is not a product purchased for permanent ownership. The registrant manages a name during a registration period under a registrar contract and the TLD's rules. Compare renewal, transfer, and expiration conditions as well as the first-year price.

  1. 01

    Define the use and candidate names

    Consider the company and service names, target countries, email, ease of saying the name aloud, likely typing errors, and similar names.

  2. 02

    Check availability and others' rights

    Availability does not establish that a name is safe to use. Check registration eligibility, trademarks, existing services, and similar spellings.

  3. 03

    Choose a registrar or designated provider

    Compare first-year, renewal, transfer, and recovery fees; DNS features; two-factor authentication; support; registrant changes; and cancellation procedures.

  4. 04

    Register under an identity the company controls

    For company use, choose registrant information, email, and a payment method the company can manage over time rather than relying solely on an agency or an individual's account.

  5. 05

    Configure DNS, web, email, and HTTPS

    Set up authoritative DNS, A, AAAA or CNAME records, MX and TXT records, web endpoints, and TLS certificates as needed, then verify them from an external network.

Compare multi-year totals, not just a monthly figure

RegistrationFirst-year registration fee
Continued useRenewal fees from the second year
Exceptional eventsTransfer, expiration recovery, and optional fees

Effective three-year cost = first-year registration + two renewals + required options is a useful comparison for identifying plans that are inexpensive only in the first year. Renewal prices, tax, exchange rates, and free-offer periods can change, so check the displayed terms immediately before applying.

A domain and its server need not use the same provider

Using one provider can simplify setup, but registrant identity, transferability, responsibility during outages, and portability at cancellation matter too. Record the providers and administrators for the registrar, authoritative DNS, and hosting.

Choosing a domain name with SEO in mind

A memorable name you can keep using is usually more practical than stuffing in search keywords. Google describes words in a domain as one relevance factor while taking steps not to overvalue exact-match domains.

01

Prioritize the brand

Using a name consistent with the company or service across search, business cards, email, and social media helps build recognition.

02

Keep it short and easy to read

Choose a name that is easy to communicate aloud and type correctly. Consider whether numbers, hyphens, or similar spellings are necessary.

03

Choose a TLD appropriate to the target region

Google says differences among generic TLDs are not usually a major ranking factor, while a ccTLD can be a strong signal that a site targets a particular country.

04

Leave room for future expansion

A name tied too narrowly to today's product or region may need to change when you add services or expand internationally.

05

Choose a consistent www or non-www URL

Ensure DNS and TLS work for both, choose one canonical URL, and redirect the other with 301 or 308. Do not rely only on canonical markup.

06

Avoid changing the name casually after adoption

Changing a domain affects URLs, backlinks, email, advertising, OAuth, cookies, certificates, and more. When a change is necessary, set up permanent redirects for individual URLs and monitor them.

Effective SEO depends on the whole site, not just the domain

The foundations are content that meets search intent, crawlable internal links, clear URLs, page speed, mobile support, HTTPS, structured data, publisher information, and regular updates. It is safer not to assume that registering a keyword-rich domain will get you a top ranking.

Domain security checklist

An expired, hijacked, or incorrectly changed domain can disrupt not only your website but also email, login, APIs, advertising, and integrations with external services. Manage it as an important business asset, not just a server setting.

  • Register the domain in the name of the company or its authorized managing entity: Do not rely solely on a departing employee, an agency, or a personal email account.
  • Enable multifactor authentication for the registrar and DNS provider: Store recovery codes securely.
  • Enable automatic renewal and multiple expiry reminders: Also watch for expired payment cards and undelivered billing emails.
  • Use transfer locks, change approvals, and audit logs: Have multiple people review important changes.
  • Plan TTL, rollback, and overlap of old and new configurations before DNS changes: Inventory A/AAAA, MX, TXT, CAA, and other records.
  • Consider DNSSEC, TLS, and registry locks for their respective roles: No single measure protects against every threat.
  • Set up email authentication: Align SPF, DKIM, and DMARC with your sending services.
  • Inventory dependencies before retiring a domain: Check websites, email, APIs, OAuth, certificates, short URLs, and external SaaS services.

DNSSEC, TLS, and locks are not substitutes for one another

DNSSEC helps validate the authenticity of DNS responses, TLS authenticates the endpoint and protects communications, and registrar or registry locks control changes such as registration and transfers. Check support from the relevant TLD and providers and introduce these measures alongside operating procedures.

Common domain problems and what to check

Expiration

The website and email suddenly stop working

Check the registration status, expiration date, billing, and recovery period. DNS, TLS, and email may not all return at the same time after recovery.

DNS changes

Some people see the old site and others see the new one

Check TTL and caches, as well as differences between authoritative servers, delegation, A/AAAA records, DNSSEC, the CDN, and browser caches.

www

Different pages appear with and without www

Set up DNS and TLS for both and permanently redirect to the canonical URL. Use the same URL in internal links, canonical tags, and sitemaps.

Email

The website works, but email does not arrive

A web A record alone does not enable email. Check MX records, sending and receiving services, SPF, DKIM, DMARC, and any remaining old email environment.

Record observations and diagnose instead of simply waiting for propagation

Record the resolver queried, name, record type, response, TTL, time, IPv4 and IPv6 results, HTTP status, and certificate. Distinguishing authoritative DNS responses from those returned by public caching resolvers makes the cause easier to isolate.

Check registration data with RDAP

Registration status, registrar, name servers, and creation, update, and expiration events can be checked through a registration data lookup for the TLD. For gTLDs, RDAP (Registration Data Access Protocol) is now the standard lookup method.

According to ICANN, gTLD registries and registrars must provide RDAP, and the obligation to provide WHOIS ended on January 28, 2025, with limited exceptions. RDAP uses HTTP(S) and structured responses and supports internationalization, authentication, and discovery of authoritative services.

Examples of available informationRegistration status and registrar
Configuration cluesName servers and event dates
When information is not publicPersonal contact details may be withheld or redacted

The information made public varies by TLD, registry, registrar, and data protection rules. Missing personal information does not mean that a domain is unregistered or illegitimate. Some ccTLDs also use their own lookup methods, so check the official guidance of the relevant registry.

Frequently asked questions about domains

Are a domain and a URL the same?

No. A domain name is a name such as example.com. A URL is the complete string identifying a resource and may include a scheme such as https, a host, a path, a query, and a fragment.

Are domain names and DNS the same?

No. A domain name is a name people can use easily; DNS is the system for querying information associated with that name, such as IP addresses and email delivery destinations.

Is www required?

No. www is a conventional host name under example.com. Choose either the www or non-www URL as canonical and redirect the other using 301 or 308.

Can I publish a website as soon as I register a domain?

Registration alone is not enough. You need to configure authoritative DNS, DNS records such as A, AAAA, and CNAME, a web server or hosting service, and a TLS certificate.

Can I use a domain forever after buying it once?

It is not permanent ownership. Registration gives you use and management rights for a defined period, and you must renew to keep using it. Expiration, recovery, and deletion terms vary by TLD and provider.

Does adding a keyword to a domain improve SEO?

Adding a keyword alone does not guarantee a high ranking. Google describes domain-name words as one factor in assessing relevance, while also explaining that its systems avoid giving excessive credit to exact-match domains. Prioritize a clear, recognizable brand.

How many hours does a DNS change take to propagate?

There is no fixed time. Results vary with TTL, caches, delegation, authoritative DNS, IPv4 and IPv6, DNSSEC, and other factors. Instead of just waiting, record the resolver, record type, response, TTL, and time of each check.

Can I check owner information using WHOIS?

What is public varies with the TLD, registration provider, and data protection rules. RDAP is now the standard lookup method for gTLDs, and personal information may be withheld or redacted.

Primary and official sources

We checked the definitions and discussion of hierarchy, URL syntax, TLDs, registration and renewal, RDAP, JP domain names, and SEO against the following official sources.

Related concepts and implementation

Summary: manage domains in three layers—names, DNS, and services

A domain name is not the same thing as a URL, DNS, or a server. Register a name, publish the information needed by the web and email through DNS, and provide services at the destination: thinking in these three layers helps organize registration, migration, and troubleshooting.

When choosing a domain, consider branding, clarity, eligibility, renewal costs, and future business plans. For operations, establish company registration, multifactor authentication, automatic renewal, access control, change procedures, and DNS, TLS, and email monitoring. Rather than relying on the domain name alone for search rankings, build useful content and operate the site reliably.

Writing and fact-checking

Finite Field Editorial Team

Our editorial team, which covers website, server, DNS, and web application design and operations, checked terminology and practical considerations against primary and official materials from IETF, IANA, ICANN, JPRS, and Google.

Website Production

Ask Finite Field
to build your website

Talk to us about everything from domain registration and DNS setup to information architecture, SEO, WordPress and Go development, redesign, speed improvements, and ongoing operations.

Free consultation Support from requirements planning onward WordPress and Go SEO and speed improvements
  • From identifying challenges to design, development, and post-launch improvements
  • Support for site migration, URL changes, and redirect design
  • Launch and rollback planning for DNS, TLS, and email
Contact

Tell us about your current challenges

You are welcome to contact us even if you have an idea but are unsure how to proceed.

We can help assess your current setup, migrate domains and DNS, and organize existing URLs.