Before you publish anything online, it helps to know exactly what a web address is telling you and others. This article walks through one hypothetical URL, marks each of its parts, and shows how to record them on a simple description card you can reuse in your own planning notes.
What Domain Names and Full URLs Each Answer
Consider this hypothetical address: https://example.org/notes/first-page?view=compact#intro. It is not a real page that exists on the internet; it is a string we will use purely to practice reading the parts of a web address. Even so, it contains everything you need to understand the difference between a domain name and a full URL.
A domain name answers the question "which server am I talking to?" Domain names are a key part of the internet infrastructure because they provide a human-readable address for any web server available on the internet. Computers communicate using IP addresses, but people have a hard time remembering those numeric strings, so domain names serve as convenient aliases.12
A full URL answers a more specific question: "which exact resource on that server do I want?" A URL is the address of a unique resource on the internet, and it is one of the key mechanisms browsers use to retrieve published resources such as HTML pages, images, or documents. While the domain name gets you to the right building, the rest of the URL tells you which floor, which room, and which shelf you are looking for.3
Marking Each Part of the Example Address
Let us label every piece of our hypothetical string. The first segment, https, is called the scheme. It indicates the protocol the browser must use to request the resource. For websites the protocol is usually HTTPS or its unsecured version HTTP. In our example the scheme tells the browser to use a secure connection.3
The next segment, example.org, is the domain name or host. It identifies which web server is being requested. A domain name has a simple structure made of several parts separated by dots and read from right to left. The rightmost part is the top-level domain, which in this case is .org. The label to its left, example, is the secondary-level domain. Together they form the host portion that directs your request to a particular server.13
After the host comes the path: /notes/first-page. The path points to a resource on the web server. In the early days of the web a path like this represented a physical file location, but nowadays it is mostly an abstraction handled by web servers without any physical reality. In our example, the path suggests a page called first-page inside a section called notes, but we are only reading the string, not claiming any server actually serves this content.3
Query Strings and Fragments: What the Punctuation Marks Mean
The question mark in our example introduces the query portion: ?view=compact. Query parameters are extra key-and-value pairs provided to the web server, separated by the ampersand symbol when there are multiple pairs. The web server can use those parameters to do extra processing before returning the resource. Here the key is view and the value is compact. We are only observing the string structure; we are not inferring what any server would actually do with this parameter.3
The hash symbol introduces the fragment: #intro. An anchor represents a sort of bookmark inside the resource, giving the browser directions to show the content located at that bookmarked spot. It is worth noting that the part after the hash, also known as the fragment identifier, is never sent to the server with the request. This means the fragment only affects what the browser displays after it has already received the page.3
So the two punctuation marks serve different roles. The question mark separates the path from parameters that travel to the server as part of the request. The hash separates the fragment, which stays on the browser side and points to a location within the returned document. Keeping this distinction in mind helps you read any address without guessing how the server behind it behaves.3
Comparing Variations While the Host Stays the Same
Now imagine we keep example.org unchanged but swap the path. If the address were https://example.org/gallery/summer-photos?view=compact#intro, the host is identical but the path points to a completely different section. The query and fragment happen to be the same, yet the resource being requested would differ because the path changed. This shows that the path is the part that locates a specific resource within the same server.
Next, keep the host and path identical but change the query. Compare https://example.org/notes/first-page?view=compact with https://example.org/notes/first-page?view=full. The server, the section, and the page name are all the same string-wise; only the parameter value differs. Whether the server actually returns different content for these two queries depends entirely on how that server is configured, which we cannot determine from the address alone.
Finally, change only the fragment. Compare https://example.org/notes/first-page?view=compact#intro with https://example.org/notes/first-page?view=compact#conclusion. Because the fragment is never sent to the server, both requests reach the server identically. The difference only matters once the browser has the document and scrolls to the bookmarked position. This is a useful observation when you are deciding whether a fragment is part of your address record or just a convenience for readers.
Writing an Address Description Card for Your Project
Record a short card for any address you plan to use in your project. A useful card contains three fields: the purpose of the address in one sentence, the full URL string exactly as you intend to write it, and a line-by-line breakdown of each part with a brief label. For our hypothetical example the purpose might read "a compact view of the first note in the notes section, bookmarked to the introduction heading." The full address is the string itself, and the breakdown lists scheme, host, path, query, and fragment separately.
Writing the purpose in your own words forces you to decide what the address is actually for. If you cannot state the purpose clearly, that is a signal the address may be too complex or poorly named for your needs. The breakdown, meanwhile, gives you a reference you can compare against later if you copy the address into a document, an email, or a link inside another page.
Choose whatever format is easiest for you to maintain. Some people prefer a plain text file; others use a spreadsheet with one row per address. The important thing is that the card lives somewhere you will actually look at it again, not buried in a draft folder you never reopen.
Verifying Your Card by Manual Copy and Marking
After you have written your card, verify it by hand. The process is simple: copy the full URL from your card, paste it into a blank line, and then go through each segment one by one, writing the label above or below it. This catches typos, missing slashes, or misplaced question marks that are easy to overlook when you are reading quickly.
Check each segment against the rules you now know. The scheme should be a recognized protocol name followed by a colon and two slashes. The host should be a valid domain name with labels separated by dots. The path should begin with a forward slash. The query, if present, should begin with a question mark. The fragment, if present, should begin with a hash. If any segment violates these patterns, go back and correct the card before you use the address anywhere.
Repeat this check each time you modify the address. Even small edits, like adding a trailing slash or changing a parameter value, can introduce subtle errors. A thirty-second manual pass is far cheaper than discovering a broken link after you have shared it with readers or embedded it in published content.
Step 1
Copy the full URL from your description card and paste it into a fresh, empty line in your text editor or notes application.
Step 2
Mark the boundary between the scheme and the host by placing a small gap or comment after the two slashes that follow the colon.
Step 3
Mark the start of the path at the first forward slash after the host, the start of the query at the question mark, and the start of the fragment at the hash symbol.
Step 4
Read each labeled segment aloud and confirm it matches the field you wrote on your card. If anything differs, update the card to match the corrected string.
Frequently asked questions
Does the fragment part of a URL ever reach the server?
No. The fragment identifier, which is the part after the hash symbol, is never sent to the server with the request. It only tells the browser where to scroll or focus after the page has loaded.3
Can I tell what a server will do just by reading its URL?
You can identify the structural parts of the address, but you cannot determine how the server handles them. Each web server has its own rules regarding parameters, and the only reliable way to know whether a specific server is handling parameters is by asking the server owner.3
Is a domain name the same thing as a URL?
No. A domain name identifies a web server and is one component inside a URL. A full URL adds a scheme, and may also include a path, query parameters, and a fragment to pinpoint a specific resource on that server.13