Everyday Internet & Troubleshooting
The Anatomy of a URL
Every web address follows the same logical structure. Once you can read its parts, URLs stop being mysterious strings and become readable instructions.
A worked example
Consider https://shop.example.com:443/products/shoes?color=red#reviews. It looks busy, but each piece has a clear job.
Scheme
https is the scheme (or protocol) — how to communicate. https means encrypted web traffic; http is the unencrypted version. Other schemes include ftp and mailto.
Host (and subdomain)
shop.example.com is the host. Reading right to left: com is the top-level domain, example.com is the registered domain, and shop is a subdomain. DNS translates this whole name into an IP address so your browser knows where to connect.
Port
:443 is the port. It's usually omitted because browsers assume the standard port for the scheme (443 for HTTPS, 80 for HTTP). You only see it when a site uses a non-standard port.
Path
/products/shoes is the path — which resource on the server you want, much like a folder-and-file location.
Query and fragment
?color=redis the query string, passing parameters to the server (here, a filter).#reviewsis the fragment, pointing to a specific spot within the page. It's handled by your browser and never sent to the server.
Why it's worth knowing
Reading a URL helps you spot where a link really goes (useful against phishing), understand how sites are organized, and debug problems. The host portion in particular ties directly to everything else on this site: it's the human-friendly name that DNS turns into the IP address your device actually connects to.