HTTP status codes explained: what 403, 404, 429, 500, 502, 503 and 504 mean
Every time a browser asks a website for a page, the server replies with a three-digit status code before anything else. You normally never see it, but when something goes wrong it's the single most useful clue about where the problem is. IsSiteUpOrDown shows this code on every status page under "HTTP response".
The five families
| Range | Meaning | Is the site up? |
|---|---|---|
| 1xx | Informational, rarely seen | Yes |
| 2xx | Success | Yes |
| 3xx | Redirect: "look over there instead" | Yes |
| 4xx | Problem with the request | Yes, the server answered |
| 5xx | Problem on the server | Not properly |
That last column is why IsSiteUpOrDown counts any response under 500 as UP: the server is alive and talking, even if it refused this particular request.
200 OK
Everything worked. If you see 200 here but the site won't load for you, the problem is on your side. Start with this checklist.
301 and 302: redirects
The site is sending visitors somewhere else, for example from example.com to www.example.com, or from HTTP to HTTPS.
We follow up to five redirects automatically. Endless redirect loops usually come from bad cookies. Clearing them for that site often fixes it.
403 Forbidden
The server understood the request but won't allow it. Common reasons: the content is region-locked, your IP address was blocked, or a security service decided the request looked automated. For you, try turning off a VPN or switching networks. A 403 doesn't mean the site is down.
404 Not Found
The server is fine, but that specific page doesn't exist. Check the address for typos, or go to the site's homepage and navigate from there.
429 Too Many Requests
You (or everyone sharing your IP address, such as an office or university network) sent too many requests too quickly. Wait a few minutes. It clears by itself.
500 Internal Server Error
A generic "something crashed" from the website's own software. It's the site's problem. Reloading occasionally works if the fault was temporary, but usually you just have to wait for them to fix it.
502 Bad Gateway
Most large sites sit behind a front door (a load balancer or CDN such as Cloudflare). A 502 means the front door is working but the server behind it sent back nonsense or nothing. It's a classic sign of an outage in progress, often during deployments or traffic spikes.
503 Service Unavailable
The server is deliberately turning people away, because it's overloaded or down for planned maintenance. Sites often show a friendly maintenance page with this code. Check back later.
504 Gateway Timeout
Like a 502, but the server behind the front door didn't answer in time. Common when a site's database is struggling under load.
No code at all
Sometimes there's no status code because no server answered. IsSiteUpOrDown shows these as:
- Timeout: nothing replied within 5 seconds.
- DNS lookup failed: the domain name doesn't point anywhere (expired domain or DNS outage).
- Connection refused: the machine exists but isn't accepting web traffic.
- TLS/SSL error: the site's security certificate is broken or expired.