A URL is not just a web address you paste into a browser. It is a structured instruction that tells software where a resource is and, in many cases, how to request or display it.
Consider:
https://example.com/learn/domains?level=beginner#renewal
The main pieces are:
https — the scheme
example.com — the host
/learn/domains — the path
?level=beginner — the query
#renewal — the fragment
The scheme
The scheme identifies the type of access being used. For normal modern websites, HTTPS is the standard secure web scheme.
HTTP and HTTPS are not merely decorations at the beginning of an address. They describe how the client communicates with the web service.
The host
The host identifies the destination by name.
example.com
A subdomain can create another host:
support.example.com
mail.example.com
news.example.com
A subdomain is still connected to the larger domain namespace, but it can point to a completely different service or server.
The path
The path identifies a location or route within the site.
Examples:
/learn/domains
/tools/dns-check
/account/settings
Paths can represent physical files, application routes, database-driven content, or other resources. What they mean depends on the website.
Query strings
A question mark begins the query portion of a URL.
Example:
/search?q=domains
More than one parameter can appear:
/search?q=domains&page=2
Query parameters are useful for searches, filters, tracking, application state and many other jobs.
They can also accidentally create large numbers of URL variations, so they should be used deliberately.
Fragments
The # portion is called a fragment.
Example:
/guide#backups
It can tell the browser to move to a particular section or represent client-side state.
The fragment is generally not sent to the web server as part of the HTTP request in the same way as the path and query.
Why extra pieces matter
These addresses may all behave differently:
example.com/page
example.com/page/
example.com/page?source=a
www.example.com/page
https://example.com/page
http://example.com/page
A website can intentionally redirect or normalize variations toward one preferred address.
URLs are infrastructure
A URL can be printed, bookmarked, indexed, emailed, linked from another website, stored in a database or shared for years.
Design important URLs as though people may still use them after the current page design is gone.
Put This Lesson to Work
Choose a real website or project you control. Identify where this lesson applies, record who is responsible for that part, and identify one change or check you can safely make.
Worked example
For a domain-email lesson, record the separate website and email providers. Look up the existing MX records without changing them, then confirm which provider receives mail.
Your finished result
A short explanation of the system, its owner, and a checked next action. Keep passwords and recovery codes out of your notes.
Check your understanding
- Can you explain the main idea without repeating a slogan?
- What evidence or example supports your explanation?
- Which decision will you make differently, and why?