HTTP Status Code Reference

Web & Dev Client-Side Privacy

A searchable reference of all HTTP status codes with meanings.

100Continue
1xx Informational
The server has received the request headers and the client should proceed to send the request body.
101Switching Protocols
1xx Informational
The requester has asked the server to switch protocols and the server has agreed.
102Processing
1xx Informational
The server has received and is processing the request, but no response is available yet.
103Early Hints
1xx Informational
Used to return some response headers before the final response.
200OK
2xx Success
Standard response for successful HTTP requests.
201Created
2xx Success
The request has been fulfilled and a new resource has been created.
202Accepted
2xx Success
The request has been accepted for processing, but processing is not complete.
204No Content
2xx Success
The server successfully processed the request and is not returning any content.
206Partial Content
2xx Success
The server is delivering only part of the resource due to a range header.
301Moved Permanently
3xx Redirection
This and all future requests should be directed to the given URI.
302Found
3xx Redirection
The resource was found but at a different URI. Tells the client to use the new URI for this request only.
304Not Modified
3xx Redirection
The resource has not been modified since the last request. Use cached version.
307Temporary Redirect
3xx Redirection
Same as 302 but preserves the HTTP method.
308Permanent Redirect
3xx Redirection
Same as 301 but preserves the HTTP method.
400Bad Request
4xx Client Error
The server cannot process the request due to a client error (malformed syntax).
401Unauthorized
4xx Client Error
Authentication is required and has failed or has not been provided.
403Forbidden
4xx Client Error
The request was valid but the server is refusing to respond. The user may not have permissions.
404Not Found
4xx Client Error
The requested resource could not be found.
405Method Not Allowed
4xx Client Error
The request method is not supported for the requested resource.
408Request Timeout
4xx Client Error
The server timed out waiting for the request.
409Conflict
4xx Client Error
The request could not be processed because of conflict with the current state of the target resource.
410Gone
4xx Client Error
The resource is no longer available and will not be available again.
418I'm a Teapot
4xx Client Error
The server cannot brew coffee because it is a teapot. (RFC 2324 joke status)
422Unprocessable Entity
4xx Client Error
The request was well-formed but unable to be followed due to semantic errors.
429Too Many Requests
4xx Client Error
The user has sent too many requests in a given amount of time.
500Internal Server Error
5xx Server Error
A generic error message for server failures.
501Not Implemented
5xx Server Error
The server does not recognize the request method or lacks the ability to fulfill it.
502Bad Gateway
5xx Server Error
The server received an invalid response from an upstream server.
503Service Unavailable
5xx Server Error
The server is currently unavailable (overloaded or down for maintenance).
504Gateway Timeout
5xx Server Error
The upstream server failed to respond in time.
511Network Authentication Required
5xx Server Error
The client needs to authenticate to gain network access.

How to Use HTTP Status Code Reference

Follow this simple step-by-step guide to get the most out of our free online HTTP Status Code Reference:

  1. 1
    Type a number, name, or phrase into the search field to filter the reference list.
  2. 2
    Narrow the results further with the All, 1xx, 2xx, 3xx, 4xx, and 5xx category buttons.
  3. 3
    Read each card for the code, its official name, its class, and a plain description.

Key Features & Capabilities

Zero Uploads

Execution occurs 100% locally in your browser memory for maximum privacy.

Instant Latency

Zero network lag or server queues — get results instantaneously as you type.

Quick Export

One-click copy to clipboard or instant file download options built right in.

Technical Specifications & Privacy Guarantee

At utilitiestools.net, privacy and data security are core design principles. When using HTTP Status Code Reference, your inputs are parsed and processed locally via client-side JavaScript execution engine. No plain text, uploaded media, or API tokens are transmitted over the internet or logged into remote server infrastructure.

Common Practical Use Cases

  • API design: decide between 401 and 403 when a token is valid but lacks the required scope.
  • Debugging a proxy: confirm what a 502 from an upstream service actually indicates before paging the team.
  • Writing client code: check whether 307 or 302 preserves the original HTTP method on redirect.
  • Onboarding: give a new backend developer a quick reference while reviewing their first endpoint.

Frequently Asked Questions

The numeric code, the reason phrase, and the description text, all case-insensitively. Typing gateway finds 502 and 504, and typing 42 matches 422 and 429.