Find the real response code a server returns and what it means — 200, 301, 403, 404, 5xx, and more.
| Code | Meaning | Likely Cause |
|---|---|---|
| 200 | OK | Page is reachable and loading normally |
| 301 | Moved Permanently | URL has a permanent redirect to another address |
| 302 | Temporary Redirect | Temporary forward; original URL still canonical |
| 403 | Forbidden | WAF, geo-block, IP ban, or wrong file permissions |
| 404 | Not Found | Page/path doesn't exist; check spelling and routes |
| 500 | Server Error | App crash or misconfiguration on the server side |
| 502 | Bad Gateway | Upstream server (origin) returned an invalid response |
| 503 | Service Unavailable | Server overloaded or in maintenance mode |
| 504 | Gateway Timeout | Origin server took too long to respond to the proxy |
Usually a WAF, geo-IP rule, bot filter, or server permission issue. Try from a different network or use the Browser vs Bot comparison in Autopsy.
The origin server is down, overloaded, or a CDN/reverse proxy can't reach it. Check server logs or contact your host.
A 301/302 is normal — but too many hops (3+) slow down load and can confuse crawlers. Run Autopsy to trace the full chain.