Every time your browser asks a website for a page, the reply starts with a three-digit number. Usually you never see it. 404 is the famous exception.
At a hotel front desk, you get short replies. “Here’s your key.” “That room has moved, it’s down the hall.” “There’s no such room.” “Sorry, the system is down.”
Websites do the same with numbers. Every reply from a website starts with a three-digit status code saying how the request went.
The families
- 200s: all fine (200 means “here you go”)
- 300s: it's moved, go here instead (a redirect)
- 400s: something's wrong with the request (404: not found, 403: not allowed)
- 500s: something's wrong on the website's side (500: server error, 503: too busy or down)
Why 404 is famous
It’s the one people actually see: the page you asked for isn’t there. Usually the link is old or there’s a typo in the address. Many websites make their 404 page friendly or funny.
What it isn’t
A 404 doesn’t mean the whole site is down. Only that one page wasn’t found.
Where the comparison breaks down
A front desk explains in words. Status codes are just numbers, so the website usually adds a friendlier page on top.
How the words fit together
A URL asks for a page. The server answers with a status code. A 500 is the website’s version of an error message.
If a page shows 404, check the address for typos. If it shows a 500 error, the problem is on their side: try again in a few minutes.

When you'll hear it
“It's throwing a 404.” The page doesn't exist at that address.
“We're getting 500s.” The website's own server is failing.
“Set up a redirect.” Send people from the old address to the new one automatically, so they don't hit a 404.
“When we change a page's address, do we send people from the old one to the new one?”

Try it yourselfReady to use it? The exact commands are on my other site, devcmds: Check a website's status code ↗


