Domain Names and URLs: Understanding Website Addresses Before Launch

When you prepare a personal website or a small project site for the first time, you will encounter two related but distinct concepts: the domain name and the full URL. Confusing them or treating them as interchangeable can lead to miscommunication when you describe your site to collaborators or troubleshoot a link. This article uses one hypothetical address to show how each part of a website address serves a different role.

What a Domain Name Tells You Versus What a Full URL Tells You

Imagine you are setting up a small site to publish project notes for a design course. A colleague asks where to find your work. You might say the site lives at example.org, but when they type that into a browser they arrive at the top-level page. To reach a specific note, you need to share a longer address. This simple situation illustrates the core distinction: a domain name identifies a server on the Internet, while a full URL identifies a particular resource on that server.¹²

Domain names exist because computers communicate using IP addresses such as 192.0.2.172, which are difficult for people to remember and can change over time. A domain name provides a human-readable alias for that numeric address. The name itself is structured in parts separated by dots and read from right to left, with the top-level domain on the right and one or more labels to its left.¹

A URL, by contrast, is the address of a unique resource on the Internet. It includes the domain name but adds further information about the protocol to use, the specific path on the server, and optional parameters or anchors. In theory each valid URL points to one unique resource, though in practice a URL may point to something that no longer exists or has moved.³

Reading the Example Address Part by Part

To see how these pieces fit together, consider the following hypothetical address used purely for illustration: https://example.org/notes/first-page?view=compact#intro. This page does not need to exist or be live anywhere; the address is a constructed string we will dissect to understand its structure. The scheme at the beginning is https, which tells the browser which protocol to use when requesting the resource. For websites, the protocol is typically HTTPS or its unsecured version HTTP.³

The authority section follows the pattern :// and in this example is example.org. This is the domain name, identifying which web server should handle the request. After the authority comes the path, which here is /notes/first-page. The path points to a location on the server, though today it is mostly an abstraction handled by web servers rather than a literal file location on disk.³

Two more parts appear after the path. The question mark introduces the query string; in this example the query is view=compact, a key-value pair that a web server can use to modify what it returns. The hash symbol introduces the fragment identifier; here the fragment is intro, which acts as a bookmark inside the resource itself, directing the browser to scroll to a particular spot. Notably, the fragment portion after the hash is never sent to the server with the request.³

Same Host, Different Paths and Queries

Now keep the host part of the address fixed at example.org and imagine two other URLs for the same hypothetical site. The first is https://example.org/notes/second-page?view=compact#summary. The second is https://example.org/notes/first-page?view=full#intro. In both cases the domain name remains example.org, meaning the request still targets the same server. What changes is the path and, in one case, the query parameter value.

Comparing these strings side by side reveals that the path determines which resource on the server is being requested. Changing /notes/first-page to /notes/second-page points to a different location in the site structure, even though the host is identical. Changing the query from view=compact to view=full keeps the same path but asks the server for a different presentation of that resource. The fragment changes where the browser scrolls within the page once the resource is loaded.

It is worth noting here that we are only observing what the strings communicate structurally. Whether a particular server actually honors the view parameter or how it renders different paths depends entirely on how that server is configured. The URL standard defines what each part means syntactically, but the behavior behind those parts is up to the server owner.

Building an Address Description Card for Your Project

When you are about to share your site address with collaborators or write it into documentation, a short description card can prevent confusion. Record three things: the purpose of the address, the complete URL string, and a brief note on what each part represents. For our hypothetical example, the card might read: Purpose is to link to the first design note in compact view, scrolled to the introduction section. The full address is https://example.org/notes/first-page?view=compact#intro.

Write down the breakdown alongside the address. Scheme: https. Host: example.org. Path: /notes/first-page. Query: view=compact. Fragment: intro. Keeping this breakdown next to the full string means anyone reading the card can immediately see which part does what, without having to parse the string themselves.

If your project has multiple pages you plan to share, consider making one card per address rather than a single combined note. A card for a gallery page will differ from a card for a settings page, and separating them makes each easier to verify independently. The format can be as simple as a plain text file or a table in a document; the key is that the full string and its labeled parts sit together.

Verifying Your Description Card by Hand

Check each labeled part against the full string by copying the URL into a plain text editor and manually placing a space or line break before each delimiter. Place a break after :// to separate the scheme from the authority. Place a break at the first / after the host to mark where the path begins. Place a break at the ? to isolate the query, and at the # to isolate the fragment. This manual exercise catches typos or missing delimiters that are easy to overlook when reading the string at a glance.

Record any discrepancy you find between the card and the actual string. If the card says the fragment is intro but the string actually reads #introduction, update one or the other so they match. Small mismatches like this are a common source of broken links when someone copies the card description rather than the live URL.

Use this verification step before you paste the address into any public document, email, or link list. It takes only a moment, but it ensures that what you have written down is exactly what a reader will type or click. Over time this habit reduces the back-and-forth of correcting shared links after publication.

Keeping Your Address Notes for Future Use

Once you have verified a description card, store it somewhere you will naturally look when writing content or communicating about the site. Some people keep a dedicated notes file alongside their project files; others add a comment block at the top of their site configuration. The specific location matters less than consistency: pick one place and always check there first.

If your project grows and you add more pages, extend the collection of cards rather than rewriting them. Each card is a snapshot of one address at one point in time. If a path or parameter changes later, update the relevant card and note the change date so you can distinguish current addresses from older ones.

This practice is particularly useful when multiple people contribute to a site. A shared card file gives everyone the same reference, reducing the chance that two contributors use slightly different versions of the same URL. It also helps when you return to a project after a break and need to remind yourself which addresses point where.

Frequently asked questions

Is a domain name the same thing as a URL?

No. A domain name identifies a server on the Internet, while a URL is a complete address that includes the domain name plus additional parts such as a scheme, path, optional query, and optional fragment. Every URL contains a domain name, but a domain name alone does not specify a particular resource on that server.¹³

What does the question mark do in a URL?

The question mark separates the path from the query string. Everything after the question mark and before any hash symbol is the query, which consists of key-value pairs that a web server can use to modify the response it returns.³

Does the fragment part of a URL get sent to the server?

No. The fragment identifier, which is the portion after the hash symbol, is never sent to the server with the request. It is used only by the browser to navigate to a specific spot within the loaded resource.³