When you prepare a website for the first time, understanding the address string is one of the earliest practical steps. This article uses a single hypothetical address to show what each part of a website address means and how to keep a clear, reusable record of it.
What a Domain Name and a Full URL Each Tell You
Suppose you are planning a small personal project and you write down the address https://example.org/notes/first-page?view=compact#intro as a placeholder for discussion. This address is purely hypothetical and is used here only to practice reading the structure of a website address. It does not point to a real page, and no server is expected to respond to it. The goal is simply to look at the string and understand what each segment communicates.
A domain name provides a human-readable address for a web server available on the Internet. Computers reach each other through numeric IP addresses, but people find those numbers hard to remember and they may change over time. Domain names solve that problem by giving each server a name that is easier to recognize and type.1
A full URL goes further than a domain name alone. A URL is the address of a unique resource on the internet and is one of the key mechanisms browsers use to retrieve published resources such as HTML pages, images, or stylesheets. Where the domain name tells you which server to contact, the rest of the URL tells that server which specific resource you want.2
Reading the Example Address Part by Part
Look at the beginning of the example address. The segment https is the scheme, which indicates the protocol the browser must use to request the resource. The separator :// follows the scheme and signals that the next part is the authority. The segment example.org is the domain name within that authority, identifying which web server is being requested. For standard HTTPS connections the port is usually omitted because the browser assumes the default.2
After the domain comes the path. In this example the path is /notes/first-page. The path represents the location of a resource on the web server. In the early days of the web a path like this corresponded to a physical file location, but nowadays it is mostly an abstraction handled by web servers without any physical reality. You can still read it as a route that narrows down which resource you are asking for.2
The question mark introduces the query portion of the address. In the example, view=compact is a key-value pair that provides extra parameters to the web server. The hash symbol introduces the fragment, which in this case is intro. A fragment acts as a bookmark inside the resource itself, giving the browser directions to show content at a specific spot. It is worth noting that the fragment is never sent to the server with the request.2
Same Host, Different Paths and Queries
Now keep the host portion example.org fixed and change only the path. If you replace /notes/first-page with /notes/second-page, the domain and scheme stay identical but the string after the authority points to a different location on the same server. At the string level these are two distinct addresses even though they share the same domain name. This observation is about how the text differs, not about what any particular server would do with each request.
Next, change the query while keeping everything else the same. Replacing view=compact with view=full produces a different query string attached to the same path. The two addresses share the same scheme, domain, and path, but they carry different parameters after the question mark. Again, this is a structural observation about the text. Each web server has its own rules regarding parameters, and the only reliable way to know whether a specific server handles a given parameter is by asking the server owner.
You can also remove the fragment entirely. Without the hash and the word intro, the address still points to the same resource on the server because fragments are not sent with the request. The fragment only affects what the browser displays after the resource loads. Comparing these variations side by side helps you see which parts of the string influence the server and which parts influence only the browser display.
Building an Address Description Card
Write a short description card for your hypothetical project address. The card does not need any special format; a few lines in a plain text file or a notebook entry will do. Start by recording the purpose of the address in one sentence, for example: a reading exercise for understanding URL structure. Then write the full address exactly as it appears, character for character.
Below the full address, list each part on its own line with a label. For the example address you would write: scheme is https, domain is example.org, path is /notes/first-page, query is view=compact, and fragment is intro. Labeling each part separately makes it easier to spot mistakes later and gives you a reference you can share with a collaborator or include in project documentation.
Record any notes about choices you made while building the card. For instance, you might note that you chose the compact view parameter because it represents a hypothetical display preference, or that the fragment intro is arbitrary and serves only as a demonstration. These notes remind you later which parts carry real meaning for your project and which are placeholders for the exercise.
Checking Your Description Card by Hand
A quick manual check catches typos and mismatched labels before they cause confusion. Because the example address is short, you can verify every character without any special tools. The steps below are author suggestions for building a reliable habit, not requirements from any external standard.
After completing the check, compare your labeled parts against the original string one more time from left to right. If every segment matches and every label is in the correct position, your description card is consistent. If you find a mismatch, correct the card and repeat the check from the beginning of the address.
Check the punctuation marks as well. Confirm that the colon and two slashes appear between the scheme and the domain, that the question mark appears before the query, and that the hash appears before the fragment. These delimiter characters are easy to overlook but they define where one part ends and the next begins.
Step 1
Copy the full address https://example.org/notes/first-page?view=compact#intro into a plain text editor or a blank line in your notes. Do not rely on memory; paste or type it fresh so you are comparing against the exact string.
Step 2
Label each part directly below the copied string. Write scheme, domain, path, query, and fragment on separate lines, and under each label write the exact characters that belong to that part. For example, under path write /notes/first-page including the leading slash.
Step 3
Compare your labels against the original string character by character from left to right. Verify that the scheme ends before the colon-slash-slash sequence, that the domain ends before the first slash of the path, that the query starts after the question mark, and that the fragment starts after the hash.
Keeping Your Address Notes for Later
Save your description card in a location you will revisit when you write content, share links, or discuss the project with others. A simple text file inside your project folder works well because it travels with the rest of your materials. The card gives you a single place to confirm the exact spelling of each part before you paste an address into a document or a message.
Decide which details are worth keeping on the card and which you can leave out. For a first project, recording the full address, the purpose, and the labeled parts is usually sufficient. You do not need to document every possible variation of the path or query unless those variations represent real pages you plan to create. Keeping the card focused on what you actually use prevents it from becoming cluttered and hard to scan.
When your project grows and you add real pages, you can extend the same card format to each new address. The habit of writing down the purpose, the full string, and the labeled parts scales naturally from a single exercise address to a list of production URLs. The key is consistency: use the same structure each time so that any card you open tells you the same kinds of information at a glance.
Frequently asked questions
What is the difference between a domain name and a full URL?
A domain name identifies which web server to contact and provides a human-readable alternative to numeric IP addresses. A full URL includes the domain name plus additional parts such as the scheme, path, query, and fragment, and it points to a specific resource on that server.12
What does the question mark do in a URL?
The question mark separates the path from the query portion of a URL. Everything after the question mark consists of key-value pairs that provide extra parameters to the web server. Each server has its own rules for handling these parameters.2
Is the fragment part of a URL sent to the server?
No. The fragment, which appears after the hash symbol, is never sent to the server with the request. It acts as a bookmark inside the resource and only affects what the browser displays after the resource has loaded.2