33 status codes documented with examples

Complete HTTP Status Codes Reference

Look up any HTTP response code. Understand what it means, why it happens, and how to fix it.

Status Code Categories

HTTP responses are grouped into five categories. Click any category to explore its codes.

1xx

Informational

2 codes

2xx

Success

5 codes

3xx

Redirection

6 codes

4xx

Client Error

14 codes

5xx

Server Error

6 codes

Quick Reference

Click any status code for a detailed explanation, troubleshooting guide, and real HTTP examples.

101 Switching Protocols 103 Early Hints 200 OK 201 Created 202 Accepted 204 No Content 206 Partial Content 301 Moved Permanently 302 Found 303 See Other 304 Not Modified 307 Temporary Redirect 308 Permanent Redirect 400 Bad Request 401 Unauthorized 403 Forbidden 404 Not Found 405 Method Not Allowed 408 Request Timeout 409 Conflict 410 Gone 413 Payload Too Large 415 Unsupported Media Type 418 I'm a Teapot 422 Unprocessable Entity 429 Too Many Requests 451 Unavailable For Legal Reasons 500 Internal Server Error 501 Not Implemented 502 Bad Gateway 503 Service Unavailable 504 Gateway Timeout 511 Network Authentication Required

Monitor Your Website 24/7

Don't wait for users to report errors. Get instant alerts when your site returns 5xx errors, goes down, or SSL certificates expire.

Uptime monitoring Status code checks SSL monitoring Instant alerts
Start Free Monitoring

Frequently Asked Questions

Quick answers to common HTTP status code questions.

HTTP status codes are 3-digit numbers returned by a web server in response to a browser's request. They indicate whether the request was successful (2xx), redirected (3xx), caused a client error (4xx), or triggered a server error (5xx). For example, 200 means OK, 404 means Not Found, and 500 means Internal Server Error.
A 301 redirect is permanent - search engines transfer link equity to the new URL and update their index. A 302 redirect is temporary - search engines keep the original URL indexed. Use 301 for permanent URL changes like site migrations or HTTPS upgrades, and 302 for temporary situations like A/B testing or maintenance pages.
To fix a 500 error: 1) Check your server error logs for specific details. 2) Review recent code changes or deployments. 3) Verify file permissions are correct. 4) Check for syntax errors in configuration files like .htaccess. 5) Ensure your server has sufficient memory and disk space. 6) Test database connectivity.
A 502 Bad Gateway error occurs when a server acting as a gateway or proxy receives an invalid response from an upstream server. Common causes include: the upstream server crashing or being overloaded, firewall rules blocking communication, PHP-FPM process timeouts, or network issues between servers. These errors are often temporary.
Use a website monitoring service like HTTP Tiger to continuously check your site's HTTP status. Monitoring services send requests to your URLs at regular intervals and alert you when errors occur, helping you fix issues before your users notice them.