Domain Name System
Connect a name people use
to a service endpoint
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.
Domain Name System
Connect a name people use
to a service endpoint
An illustration of resolving a name through DNS and connecting to an endpoint.
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.
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.
| In one sentence | A memorable hierarchical name used for websites, email, and other services |
|---|---|
| How it differs from a URL | A domain name can form the host part of a URL; it is not the entire URL |
| How it differs from DNS | A domain name is a name; DNS is the system used to look up associated information |
| Configuration after registration | Authoritative DNS, A, AAAA or CNAME records, a web server, a TLS certificate, and MX or TXT records when needed |
| Costs to consider | Renewal, transfer, recovery after expiration, options, exchange rates, and tax as well as the first year |
| Safe management | Company-controlled registration, multifactor authentication, automatic renewal, least privilege, change procedures, and monitoring |
| Checked on | July 29, 2026 |
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.
wwwA label identifying a hostshopA label distinguishing a useexampleA name registered under .comcomTop-level domainFollow 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.
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.
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.
↔ Scroll horizontally to view the table
| Term | Meaning and role | Example | Common confusion |
|---|---|---|---|
| Domain name | A name in the hierarchical DNS namespace | example.com | It is neither the whole URL nor the server |
| URL | A string identifying a resource, including a scheme, host, and path | https://example.com/about/ | A domain name can appear in the host part of a URL |
| DNS | A system for looking up IP addresses, mail destinations, and other information associated with names | A, AAAA, CNAME, MX, TXT | It does not serve the web page itself |
| IP address | A numeric address used to identify network interfaces or destinations | 192.0.2.1, 2001:db8::1 | One name can resolve to multiple IPs, and multiple sites can share one IP |
| Web server | Software or an environment that receives HTTP requests and returns HTML, images, API responses, and other content | Nginx, Apache, Cloud Run, and others | A separate layer from registration and DNS management |
| Host name | A domain name used to identify a network host or service | shop.example.com | Not necessarily a registration unit |
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.
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.
It identifies the scheme, host, port, path, query, and fragment. An omitted port is determined from the scheme's default and other context.
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.
A records provide IPv4 candidates and AAAA records provide IPv6 candidates. Some configurations follow aliases such as CNAME records.
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.
The browser sends an HTTP request including the host, path, and query; the web server or application returns HTML, images, JSON, or other content.
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.
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.
Examples include .com, .org, and .net, alongside many newer gTLDs. A TLD's original intended use does not necessarily match its current registration requirements.
Examples include .jp, .uk, and .de. They are associated with countries or regions, and registration eligibility and required information vary by registry.
Individuals and organizations with an address in Japan are eligible. Registration numbers are unrestricted and Japanese-language names are supported.
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
| Category | Example | Typical use | What to check |
|---|---|---|---|
| Common gTLD | .com, .org, .net | Brands and services used domestically or internationally | Renewal price, trademarks, transfer, and recovery conditions |
| Country-code TLD | .jp, .de, .uk | Sites primarily serving a particular country or region | Residence and eligibility, public information, and usage rules |
| General-use JP | example.jp | Sites for individuals, businesses, and organizations serving Japan | Japanese address, characters and format, and designated provider |
| Organizational JP | example.co.jp | Companies registered in Japan and other eligible organizations | Organization type, one domain per organization, and registrant identity |
| Japanese-language domain | café.example | Advertising, local names, or a memorable secondary URL | Input environment, email support, lookalike characters, and ASCII-compatible form |
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.
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.
| Approach | Example | Characteristics | Common uses |
|---|---|---|---|
| Custom domain | example.com | A name registered and renewed under a contract through a registrar or provider | The main site for a company, service, or brand |
| Subdomain | shop.example.com | A name created in DNS beneath a registered domain; it can point to a different server | Shops, administration, APIs, or regional and product sites |
| Subdirectory | example.com/shop/ | A URL path under the same host, configured at the web layer rather than in DNS | Article 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.
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.
Consider the company and service names, target countries, email, ease of saying the name aloud, likely typing errors, and similar names.
Availability does not establish that a name is safe to use. Check registration eligibility, trademarks, existing services, and similar spellings.
Compare first-year, renewal, transfer, and recovery fees; DNS features; two-factor authentication; support; registrant changes; and cancellation procedures.
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.
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.
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.
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.
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.
Using a name consistent with the company or service across search, business cards, email, and social media helps build recognition.
Choose a name that is easy to communicate aloud and type correctly. Consider whether numbers, hyphens, or similar spellings are necessary.
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.
A name tied too narrowly to today's product or region may need to change when you add services or expand internationally.
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.
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.
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.
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.
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.
Check the registration status, expiration date, billing, and recovery period. DNS, TLS, and email may not all return at the same time after recovery.
Check TTL and caches, as well as differences between authoritative servers, delegation, A/AAAA records, DNSSEC, the CDN, and browser caches.
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.
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 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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.
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.