HTTP Status Codes Cheat Sheet

Comprehensive HTTP status code reference with meanings, examples, and debugging guidance.

View
StandardDetailedCompact
Export
Copy the compact sheet, download it, or print it.
Download
`D` dense toggle · `C` copy all
## Status Code Classes
HTTP status code classes
1xx Informational
2xx Success
3xx Redirection
4xx Client Error
5xx Server Error

# Understand the five categories of HTTP responses.

Debug status codes in the right order
1) Check request method, URL, headers, and body
2) Inspect auth and permissions
3) Follow redirects if needed
4) Check upstream/app logs for 5xx
5) Confirm caching/proxy/CDN behavior

# A quick flow for deciding where a problem lives.

Check headers and status with curl
curl -I https://example.com

# Inspect the response line and headers only.

See the full request/response exchange
curl -v https://example.com

# Use verbose mode to diagnose redirects, TLS, and headers.

Follow redirects
curl -L https://example.com

# Useful for 301, 302, 307, and 308 responses.

## Common API Response Patterns
GET success codes
200 OK
206 Partial Content
304 Not Modified

# Typical success responses for reads.

Create success codes
201 Created
202 Accepted
204 No Content

# Typical responses when creating resources.

Authentication and authorization codes
401 Unauthorized
403 Forbidden
407 Proxy Authentication Required

# The most common auth-related status codes.

Rate limiting and overload codes
408 Request Timeout
425 Too Early
429 Too Many Requests
503 Service Unavailable

# Responses commonly used when a client must back off.

Recommended next

No recommendations yet.