HTTP Status Codes Searchable Reference Guide

minimalist, searchable reference for web response codes. get technical meanings for 1xx-5xx status.

1001xx
Continue
The server has received the request headers and the client should proceed to send the request body.
1011xx
Switching Protocols
The requester has asked the server to switch protocols.
2002xx
OK
Standard response for successful HTTP requests.
2012xx
Created
The request has been fulfilled, resulting in the creation of a new resource.
2022xx
Accepted
The request has been accepted for processing, but the processing has not been completed.
2042xx
No Content
The server successfully processed the request and is not returning any content.
3013xx
Moved Permanently
This and all future requests should be directed to the given URI.
3023xx
Found
The resource was found, but at a different URI.
3043xx
Not Modified
Indicates that the resource has not been modified since the version specified by the request headers.
4004xx
Bad Request
The server cannot or will not process the request due to an apparent client error.
4014xx
Unauthorized
Similar to 403 Forbidden, but specifically for use when authentication is required and has failed or has not yet been provided.
4034xx
Forbidden
The request was valid, but the server is refusing action.
4044xx
Not Found
The requested resource could not be found but may be available in the future.
4054xx
Method Not Allowed
A request method is not supported for the requested resource.
4094xx
Conflict
Indicates that the request could not be processed because of conflict in the current state of the resource.
4224xx
Unprocessable Entity
The request was well-formed but was unable to be followed due to semantic errors.
4294xx
Too Many Requests
The user has sent too many requests in a given amount of time.
5005xx
Internal Server Error
A generic error message, given when an unexpected condition was encountered and no more specific message is suitable.
5015xx
Not Implemented
The server either does not recognize the request method, or it lacks the ability to fulfil the request.
5025xx
Bad Gateway
The server was acting as a gateway or proxy and received an invalid response from the upstream server.
5035xx
Service Unavailable
The server cannot handle the request (because it is overloaded or down for maintenance).
5045xx
Gateway Timeout
The server was acting as a gateway or proxy and did not receive a timely response from the upstream server.

Understanding HTTP Response Status Codes

HTTP status codes are standard response codes given by web server servers on the internet. These three-digit integers indicate the result of an HTTP request and help developers diagnose issues between clients and servers. Our searchable HTTP reference provides clear, technical definitions for every major status code defined by the IETF, from successful 200 OK responses to critical 500 Internal Server Errors.

Category Guide

  • 1xx (Informational): Request received, continuing process.
  • 2xx (Success): The action was successfully received and accepted.
  • 3xx (Redirection): Further action must be taken to complete the request.
  • 4xx (Client Error): The request contains bad syntax or cannot be fulfilled.
  • 5xx (Server Error): The server failed to fulfill an apparently valid request.

API Developer Tool

Whether you are building a REST API, debugging a frontend fetch request, or managing server logs, having a quick reference for status codes like 422 Unprocessable Entity or 429 Too Many Requests is essential for modern web engineering.

Frequently Asked Questions

What is the most common HTTP error?

The 404 Not Found is the most recognized error, indicating that the server could not find the requested resource. For backend developers, the 500 Internal Server Error is also common, signifying an unhandled exception on the server.

What is a 418 status code?

HTTP 418 I'm a teapot is an Easter egg status code defined in RFC 2324 as part of the Hyper Text Coffee Pot Control Protocol (HTCPCP), intended as an April Fools' Joke.