URL

A URL can contain a scheme, host, port, path, query string and fragment. Web links, stylesheets, images, API endpoints and canonical addresses are commonly represented as URLs. In practical terms, URL belongs to the browser, server or document layer. Knowing that layer is important because it tells you what the term can change, what it cannot change, and where to look when something behaves unexpectedly.

The common mistake is to use URL as if it also meant DNS. That blurs two separate decisions and usually sends troubleshooting in the wrong direction. A better test is practical: Break the address into scheme, hostname, path, query and fragment before troubleshooting redirects or routing.

In day-to-day work, URL matters when the concept needs to be identified precisely instead of being grouped with a nearby term. The practical value is not the vocabulary itself; it is being able to identify the right control, file, setting or decision when the concept becomes relevant.

https://example.com/products/?sort=price contains a scheme, host, path and query string, each identifying a different part of the resource request. That example is useful because it turns the definition into something you can recognize, test and discuss with other people working on the same project.

Use these references when you need documentation-level detail, specifications or product-specific behavior beyond the plain-English explanation above.