HTTP Status Codes Reference
Learn about HTTP status codes the fun way. Explore all 1xx, 2xx, 3xx, 4xx, and 5xx error codes with playful explanations, technical details, and real HTTP response examples.
404Not Found
The internet's version of 'I looked everywhere and it's just not here!' Like searching for your keys in an empty pocket.
HTTP/1.1 404 Not Found
Content-Type: application/json
{"error": "Resource not found"}Most Common Status Codes
These HTTP status codes are encountered most frequently by developers. Understanding them is essential for web development and debugging.
- 200OKEverything is awesome! Your request was perfect and here's exactly what you asked for.
- 301Moved PermanentlyWe've moved! Like forwarding your mail after moving to a new house. Update your bookmarks!
- 302FoundDetour ahead! The page is temporarily hanging out somewhere else. We'll point you there!
- 400Bad RequestHuh? The server is scratching its head because your request doesn't make sense. Like ordering a pizza with negative toppings.
- 401UnauthorizedWho are you?! The bouncer needs to see some ID before letting you in. Time to log in!
- 403ForbiddenVIP only! You might know who you are, but you're not on the guest list for this party.
- 404Not FoundThe internet's version of 'I looked everywhere and it's just not here!' Like searching for your keys in an empty pocket.
- 500Internal Server ErrorOops, we broke it! The server had a little meltdown. It's not you, it's definitely us.
- 502Bad GatewayLost in translation! The middleman server got gibberish from the backend. Like a game of telephone gone wrong.
- 503Service UnavailableBRB! The server is taking a coffee break or being pampered with maintenance. Please hold!
Popular Comparisons
Confused about which status code to use? These side-by-side comparisons help you understand the subtle but important differences.
- 401 vs 403๐ ๐ซAuthentication vs Authorization - When to use each
HTTP/1.1 401 UnauthorizedWWW-Authenticate: BearerHTTP/1.1 403 ForbiddenContent-Type: application/json{"error": "Access denied"} - 301 vs 302๐ฆ ๐Permanent vs Temporary redirects for SEO
HTTP/1.1 301 Moved PermanentlyLocation: https://new-site.com/pageHTTP/1.1 302 FoundLocation: /temporary-page - 404 vs 410๐ ๐ปNot Found vs Gone - Resource availability
HTTP/1.1 404 Not FoundContent-Type: application/json{"error": "Resource not found"}HTTP/1.1 410 GoneContent-Type: application/json{"error": "Resource permanently deleted"} - 500 vs 502๐ฅ ๐Internal Server Error vs Bad Gateway
HTTP/1.1 500 Internal Server ErrorContent-Type: application/json{"error": "Something went wrong"}HTTP/1.1 502 Bad GatewayContent-Type: text/html<h1>Bad Gateway</h1> - 301 vs 308๐ฆ ๐ Permanent redirects with method preservation
HTTP/1.1 301 Moved PermanentlyLocation: https://new-site.com/pageHTTP/1.1 308 Permanent RedirectLocation: /new-permanent-endpoint - 302 vs 307๐ โช๏ธTemporary redirects with method preservation
HTTP/1.1 302 FoundLocation: /temporary-pageHTTP/1.1 307 Temporary RedirectLocation: /alternative-endpoint
Latest from the Blog
Articles, guides, and deep dives into HTTP status codes, web development, and debugging common server issues.
View All Posts- 14 min read
Understanding HTTP 406 Not Acceptable: Accept Headers, Default Representations, and the WAF Red Herring
What 406 Not Acceptable really means, how Accept headers and q-values drive content negotiation, why a default representation usually beats a 406, why a WAF block can show up as a 406, and how to return it correctly in Express and Next.js with Vary: Accept.
4xxClient Error - 14 min read
Understanding HTTP 501 Not Implemented: Unknown Methods, 501 vs 405, and Why It Isn't a Coming-Soon Page
What 501 Not Implemented really means (a method the server doesn't support anywhere), how it differs from 405, why it's a bad stub for unfinished endpoints, why it's heuristically cacheable, and what Node, Express, Next.js and NGINX actually do with unknown methods.
5xxServer Error - 14 min read
Understanding HTTP 431 Request Header Fields Too Large: Cookie Bloat, Header Limits, and Why You Often Get a 400 Instead
What 431 Request Header Fields Too Large means, the real causes (cookie bloat, oversized tokens, shared parent-domain cookies, localhost cookies from other projects), the actual header limits in NGINX, Apache, Node.js, AWS ALB and Cloudflare, and how it differs from 413, 414 and 400.
4xxClient Error
Explore All Status Codes
Browse our complete collection of 80 HTTP status codes, including standard codes and vendor-specific responses from NGINX, Cloudflare, AWS, and Microsoft IIS.
View All Status Codes