Skip to main content

HTTP Status Code FinderDeveloper

Quickly look up any HTTP status code to understand its meaning and common causes.
200

OK

Success

The request succeeded. The result depends on the HTTP method.

201

Created

Success

The request succeeded, and a new resource was created as a result.

204

No Content

Success

There is no content to send for this request, but the headers may be useful.

301

Moved Permanently

Redirection

The URL of the requested resource has been changed permanently.

302

Found

Redirection

The URI of requested resource has been changed temporarily.

400

Bad Request

Client Error

The server cannot or will not process the request due to an apparent client error.

401

Unauthorized

Client Error

The client must authenticate itself to get the requested response.

403

Forbidden

Client Error

The client does not have access rights to the content.

404

Not Found

Client Error

The server cannot find the requested resource.

500

Internal Server Error

Server Error

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

502

Bad Gateway

Server Error

The server, while working as a gateway to get a response needed to handle the request, got an invalid response.

503

Service Unavailable

Server Error

The server is not ready to handle the request. Common causes are maintenance or overloading.

Capabilities & How-To Guide

Instructions, supported options, and client-side privacy guarantee.

HTTP Status Codes are three-digit responses from a server to a client's request. They are divided into five classes based on the first digit (1xx through 5xx).

Standard Classes:

  • 2xx: Success
  • 3xx: Redirection
  • 4xx: Client Error
  • 5xx: Server Error
Need an extra feature or found an edge case?Send Feedback