What a URL Is

When you open a website, you type something like https://example.com/about into the bar at the top of your browser. It looks like one long, slightly cryptic string — but it isn't one blob. It's several parts joined together, each saying something specific about what you're asking for.

That string has a name: a URL — short for uniform resource locator, the address of a single page or file on the web. Once you can read a URL the way you read a postal address, a lot of the web stops being mysterious, and you start noticing exactly where a link is about to send you.

What is a URL?

A URL is the full address of one thing on the web — usually a page, sometimes an image or a file. It's what your browser needs to go and fetch the exact resource you want, out of the billions sitting on computers all over the world.

Think of a postal address. "France, Paris, 12 Rue Lafayette, apartment 4" isn't one fact — it's a stack of them, each narrowing the search until only one mailbox is left. A URL works the same way: each part narrows things down, from "which computer" to "which page on it." Read left to right, it goes from broad to specific.

The parts of a URL

Take https://example.com/about apart and three pieces fall out. The first is the scheme — the https:// at the front. It tells the browser how to fetch the page, which connection rules to use. For ordinary web pages it's almost always https.

The middle part is the domain — example.com here. This is the website's name: the human-friendly label that, as the last topic showed, DNS quietly looks up and turns into the address of the computer your browser should talk to. When people say "the website," they usually mean this part.

The last part is the path — /about, everything from the slash onward. The domain gets you to the right computer; the path picks which page on it you want. Change the path and you stay on the same site but land on a different page: /about, /contact, /help all live at example.com.

https vs http: the padlock

You've probably noticed a small padlock icon near the address bar. It's tied to that scheme at the front. https — the s stands for secure — means the connection between your browser and the website is encrypted: scrambled so that anyone who intercepts it along the way sees only gibberish, not your password or card number.

Plain http, without the s, sends everything in the open, readable by anyone who can watch the traffic in between. That's why browsers now flag plain http pages as "Not secure." The padlock isn't decoration — it's the browser telling you the link to the site is encrypted. The full machinery behind that lock comes later in the security material; for now, remember that the padlock only means the connection is encrypted — it does not promise the site itself is honest or safe, since scam sites can show a padlock too.

Reading a URL before you click

Once the parts are clear, you can read a link before you follow it. The domain is the part that matters most for safety, and it's the rightmost piece of the name just before the first single slash. In https://example.com/login, the domain is example.com — so that page really is on the example.com site.

This is how people get tricked. A link like https://example.com.scam-site.net/login looks at a glance like example.com, but the real domain is scam-site.net — example.com is just a label tacked onto the front. Reading the domain correctly, right before that first slash, is a small skill that saves real trouble. One wrinkle: some real sites end in things like .co.uk, so the name can carry an extra piece — when you're not sure, don't rely on eyeballing the address alone.