How the web works under the address bar
The three pieces of plumbing worth understanding: what a web address is made of, what the padlock proves, and what happens in the moment between typing a name and seeing a page.
Three pieces of plumbing sit behind every page you open: the address you typed, the lookup that turns that name into a machine somewhere in the world, and the padlock claiming your connection is private. You can use the web for years without thinking about any of them, right up to the moment a message asks you to click a link and you have no reliable way of telling whether it goes where it says it does.
Start with how a web address is put together, because reading the real domain out of a long link is the most useful defensive habit here. Then take what the padlock proves and what it does not, which is considerably less than most people assume. DNS decides where you actually land when you type a name, and it explains a surprising number of odd errors and blocked sites.
Put together, these three turn an abstract warning into something you can check yourself, which is exactly what you need when a message arrives with a link and a deadline.
Articles in this hub
- Anatomy of a URL: reading a web address like a proEvery part of a web address explained, and the single rule for spotting a fake domain that defeats most phishing links.
- HTTPS and the padlock: what it proves and what it does notWhat the padlock in the address bar actually guarantees, why scam sites have it too, and the certificate warnings you should never click past.
- DNS explained: the phone book that decides where you landWhat DNS does every time you open a page, why changing your DNS can speed things up or filter content, and what your resolver can see about you.
- What your IP address reveals, and what it does notWhat an IP address is, what somebody can actually learn from one, why yours changes, and the difference between the address on your device and the one the world sees.