HTTP Status Code Lookup

Search and browse HTTP status codes and their meanings

HTTP Status Code Lookup
Search and browse HTTP status codes and their meanings
HTTP Status Code Lookup
Search and browse HTTP status codes and their meanings
50
CodeNameCategoryDescription
100

Continue

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

Switching Protocols

InformationalThe requester has asked the server to switch protocols and the server has agreed.
102

Processing

InformationalThe server has received and is processing the request, but no response is available yet.
103

Early Hints

InformationalUsed to return some response headers before final HTTP message.
200

OK

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

Created

Common
SuccessThe request has been fulfilled and resulted in a new resource being created.
202

Accepted

SuccessThe request has been accepted for processing, but the processing has not been completed.
204

No Content

Common
SuccessThe server successfully processed the request and is not returning any content.
206

Partial Content

SuccessThe server is delivering only part of the resource due to a range header sent by the client.
300

Multiple Choices

RedirectionThe request has more than one possible response. The user agent should choose one of them.
301

Moved Permanently

Common
RedirectionThe URL of the requested resource has been changed permanently.
302

Found

Common
RedirectionThe URL of the requested resource has been changed temporarily.
304

Not Modified

Common
RedirectionIndicates that the resource has not been modified since the version specified by the request headers.
307

Temporary Redirect

RedirectionThe server is redirecting the user agent to a different resource, as indicated by a Location header.
308

Permanent Redirect

RedirectionThe resource is now permanently located at another URL, specified by the Location header.
400

Bad Request

Common
Client ErrorThe server cannot or will not process the request due to an apparent client error.
401

Unauthorized

Common
Client ErrorAuthentication is required and has failed or has not yet been provided.
403

Forbidden

Common
Client ErrorThe request was valid, but the server is refusing action.
404

Not Found

Common
Client ErrorThe requested resource could not be found but may be available in the future.
405

Method Not Allowed

Common
Client ErrorA request method is not supported for the requested resource.
406

Not Acceptable

Client ErrorThe requested resource is capable of generating only content not acceptable according to the Accept headers sent in the request.
408

Request Timeout

Client ErrorThe server timed out waiting for the request.
409

Conflict

Client ErrorThe request could not be processed because of conflict in the request.
410

Gone

Client ErrorThe resource requested is no longer available and will not be available again.
411

Length Required

Client ErrorThe request did not specify the length of its content, which is required by the requested resource.
412

Precondition Failed

Client ErrorThe server does not meet one of the preconditions that the requester put on the request.
413

Payload Too Large

Client ErrorThe request is larger than the server is willing or able to process.
414

URI Too Long

Client ErrorThe URI provided was too long for the server to process.
415

Unsupported Media Type

Client ErrorThe request entity has a media type which the server or resource does not support.
416

Range Not Satisfiable

Client ErrorThe client has asked for a portion of the file, but the server cannot supply that portion.
417

Expectation Failed

Client ErrorThe server cannot meet the requirements of the Expect request-header field.
418

I'm a teapot

Client ErrorThis code was defined in 1998 as one of the traditional IETF April Fools jokes.
422

Unprocessable Entity

Client ErrorThe request was well-formed but was unable to be followed due to semantic errors.
425

Too Early

Client ErrorIndicates that the server is unwilling to risk processing a request that might be replayed.
426

Upgrade Required

Client ErrorThe client should switch to a different protocol such as TLS/1.0.
428

Precondition Required

Client ErrorThe origin server requires the request to be conditional.
429

Too Many Requests

Common
Client ErrorThe user has sent too many requests in a given amount of time.
431

Request Header Fields Too Large

Client ErrorThe server is unwilling to process the request because its header fields are too large.
451

Unavailable For Legal Reasons

Client ErrorThe server is denying access to the resource as a consequence of a legal demand.
500

Internal Server Error

Common
Server ErrorA generic error message, given when an unexpected condition was encountered.
501

Not Implemented

Server ErrorThe server either does not recognize the request method, or it lacks the ability to fulfill the request.
502

Bad Gateway

Common
Server ErrorThe server was acting as a gateway or proxy and received an invalid response from the upstream server.
503

Service Unavailable

Common
Server ErrorThe server is currently unavailable (because it is overloaded or down for maintenance).
504

Gateway Timeout

Common
Server ErrorThe server was acting as a gateway or proxy and did not receive a timely response from the upstream server.
505

HTTP Version Not Supported

Server ErrorThe server does not support the HTTP protocol version used in the request.
506

Variant Also Negotiates

Server ErrorTransparent content negotiation for the request results in a circular reference.
507

Insufficient Storage

Server ErrorThe server is unable to store the representation needed to complete the request.
508

Loop Detected

Server ErrorThe server detected an infinite loop while processing the request.
510

Not Extended

Server ErrorFurther extensions to the request are required for the server to fulfill it.
511

Network Authentication Required

Server ErrorThe client needs to authenticate to gain network access.

What is an HTTP Status Code?

HTTP status codes are three-digit response codes returned by a server to show what happened to a request. You will see them in browser developer tools, API responses, server logs, uptime checks, and reverse proxy dashboards.

How to Read the Main Status Code Families

  • 1xx Informational: The server received the request and the exchange is still in progress.
  • 2xx Success: The request completed successfully.
  • 3xx Redirection: The client needs to follow another location or reuse a cached result.
  • 4xx Client Error: The request itself has a problem, such as a missing resource, invalid input, or failed authentication.
  • 5xx Server Error: The server or an upstream dependency failed while handling a valid request.

When This Lookup is Useful

Use this lookup when you need to confirm what a status code means, compare similar codes such as 401 vs 403 or 502 vs 504, or search by a phrase from an error message. The tool supports searching by code, status name, and localized description.

Why Correct Interpretation Matters

A status code is often the fastest clue during debugging. A 4xx response usually points to the request, credentials, or target resource, while a 5xx response usually points to the application, gateway, or upstream service. Reading the category first helps you choose the right next step.