How A URL Is Built
The address bar holds six engineered pieces glued together by punctuation. Each one means something specific — and one mistake breaks the whole thing.
A URL looks like one string, but it's six nested parts, each with a job. Take this example:
https://example.com:443/articles/2026/popcorn?sort=new#top
The scheme — https://
What protocol to use. https means a secure HTTP request. Others: http, ftp, mailto, file. The :// separator tells the browser "what follows is a network location."
The host — example.com
The domain name. The browser will look this up in DNS to get an IP address — the actual machine on the internet where the website lives.
The port — :443
Which "door" on that machine to knock on. https defaults to 443, http to 80. Usually omitted because the default applies. Custom ports (:8080, :3000) are used for dev servers or private services.
The path — /articles/2026/popcorn
The location on that machine. The server decides what this means — often it maps to a folder and file, but increasingly it's just a route handled by code. The path is case-sensitive on most servers.
The query string — ?sort=new
Key-value pairs after the ?, joined by &. These are parameters passed to the server: ?sort=new&page=2&lang=en. They're visible in the address bar, bookmarkable, and not secret.
The fragment — #top
A specific spot within the page. The fragment is never sent to the server — the browser handles it locally, scrolling to an element with id="top". That's why clicking a footnote jumps without reloading.
Why one typo breaks everything
Each piece has strict syntax:
- Scheme and host are case-insensitive.
- Path and query are usually case-sensitive.
- Spaces must be encoded as
%20, special chars as%xx. - A misplaced
?,#, or/changes meaning entirely.
The URL is one of the most successful mini-languages ever built. Six pieces, a handful of punctuation rules, and the entire web is addressable by typing a single line.
Written with 💖 by Waela · Back to The Side Quest
Built with 💖 by Waela
Keep going down the rabbit hole
Why GIFs Never Died
A 1987 image format that everyone mocked as obsolete became the internet's native language for reaction, comedy, and the half-second feeling.
Why CAPTCHAs Ask You About Traffic Lights
Pick every square with a traffic light. You're doing a tiny job for a self-driving car company — and the system isn't really checking if you're human.
How Memes Evolve Like Genes
Memes mutate, compete, reproduce, and die — following the same rules as living things. Richard Dawkins predicted it in 1976.
Why Wi-Fi Has Those Weird Names
802.11ac, 802.11n, 802.11ax — your router is named after a 1997 IEEE committee's numbering scheme. Here's why it stuck.