📡

HTTP Status Codes

Look up and understand HTTP response status codes.

Showing 21 status codes

100

Continue

1xx

The server has received the request headers and the client should proceed to send the request body.

101

Switching Protocols

1xx

The server is switching protocols as requested by the client.

200

OK

2xx

The request has succeeded. The meaning of the success depends on the HTTP method.

201

Created

2xx

The request has been fulfilled and resulted in a new resource being created.

204

No Content

2xx

The server successfully processed the request but is not returning any content.

301

Moved Permanently

3xx

The requested resource has been permanently moved to a new URL.

302

Found

3xx

The requested resource temporarily resides under a different URL.

304

Not Modified

3xx

The resource has not been modified since the last request. Use the cached version.

400

Bad Request

4xx

The server could not understand the request due to invalid syntax.

401

Unauthorized

4xx

The client must authenticate itself to get the requested response.

403

Forbidden

4xx

The client does not have access rights to the content.

404

Not Found

4xx

The server cannot find the requested resource.

405

Method Not Allowed

4xx

The request method is known by the server but is not supported by the target resource.

408

Request Timeout

4xx

The server would like to shut down this unused connection.

409

Conflict

4xx

The request conflicts with the current state of the server.

410

Gone

4xx

The requested resource has been permanently removed and will not be available again.

429

Too Many Requests

4xx

The user has sent too many requests in a given amount of time (rate limiting).

500

Internal Server Error

5xx

The server has encountered a situation it does not know how to handle.

502

Bad Gateway

5xx

The server received an invalid response from an upstream server.

503

Service Unavailable

5xx

The server is not ready to handle the request. It may be overloaded or down for maintenance.

504

Gateway Timeout

5xx

The server is acting as a gateway and did not receive a timely response from the upstream server.

How to Use

  1. 1Enter the HTTP status code in the input field (e.g., 200, 404, 500)
  2. 2Click the "Look up" button
  3. 3View the status code meaning, description, and common causes
  4. 4Browse status code categories: 1xx, 2xx, 3xx, 4xx, 5xx

Use Cases

  • •Debug API responses and error messages
  • •Understand web server behavior during development
  • •Configure proper error handling in applications
  • •Learn HTTP protocol for web development

Tips

  • 💡2xx codes indicate success, 3xx for redirects, 4xx for client errors, 5xx for server errors
  • 💡404 Not Found is the most common error - check your URL carefully
  • 💡301 redirects are permanent, 302 redirects are temporary
  • 💡Use 429 Too Many Requests to handle rate limiting

About This Tool

This is a free online tool that helps you complete tasks quickly. All processing happens in your browser to keep your data secure.

🔒 Privacy Protected⚡ Instant Processing🌐 No Registration

Related Tools