HTTP Status Code Reference

Quick reference guide for all HTTP status codes with detailed explanations

Search Status Codes

Filter by Category

1xx - Informational

Request received, continuing process

100

Continue

The client should continue with its request

101

Switching Protocols

The server is switching protocols as requested by the client

102

Processing

The server is processing the request but no response is available yet

103

Early Hints

Used to return some response headers before final HTTP message

2xx - Success

The action was successfully received, understood, and accepted

200

OK

The request was successful

201

Created

The request was successful and a new resource was created

202

Accepted

The request has been accepted for processing, but processing is not complete

203

Non-Authoritative Information

The returned meta-information is not definitive

204

No Content

The request was successful but there is no content to return

205

Reset Content

The client should reset the form that caused this request to be sent

206

Partial Content

The server is delivering only part of the resource due to a range header

207

Multi-Status

The message body contains multiple status codes for different operations

208

Already Reported

The members of a DAV binding have already been enumerated

226

IM Used

The server has fulfilled a request using an instance manipulation

3xx - Redirection

Further action must be taken in order to complete the request

300

Multiple Choices

There are multiple options for the resource from which the client may choose

301

Moved Permanently

The resource has been permanently moved to a new URL

302

Found

The resource temporarily resides under a different URL

303

See Other

The response can be found under a different URL using GET method

304

Not Modified

The resource has not been modified since the last request

305

Use Proxy

The requested resource must be accessed through the proxy given by the Location field

307

Temporary Redirect

The request should be repeated with another URL but future requests should still use the original URL

308

Permanent Redirect

The request and all future requests should be repeated using another URL

4xx - Client Error

The request contains bad syntax or cannot be fulfilled

400

Bad Request

The server cannot process the request due to a client error

401

Unauthorized

Authentication is required and has failed or has not yet been provided

402

Payment Required

Reserved for future use

403

Forbidden

The request was valid, but the server is refusing action

404

Not Found

The requested resource could not be found

405

Method Not Allowed

The request method is not supported for the requested resource

406

Not Acceptable

The requested resource is capable of generating only content not acceptable according to the Accept headers

407

Proxy Authentication Required

The client must first authenticate itself with the proxy

408

Request Timeout

The server timed out waiting for the request

409

Conflict

The request could not be processed because of conflict in the request

410

Gone

The resource requested is no longer available and will not be available again

411

Length Required

The request did not specify the length of its content

412

Precondition Failed

The server does not meet one of the preconditions that the requester put on the request

413

Payload Too Large

The request is larger than the server is willing or able to process

414

URI Too Long

The URI provided was too long for the server to process

415

Unsupported Media Type

The request entity has a media type which the server or resource does not support

416

Range Not Satisfiable

The client has asked for a portion of the file, but the server cannot supply that portion

417

Expectation Failed

The server cannot meet the requirements of the Expect request-header field

418

I'm a teapot

This code was defined as an April Fools' joke and is not expected to be implemented by actual HTTP servers

421

Misdirected Request

The request was directed at a server that is not able to produce a response

422

Unprocessable Entity

The request was well-formed but was unable to be followed due to semantic errors

423

Locked

The resource that is being accessed is locked

424

Failed Dependency

The request failed because it depended on another request and that request failed

425

Too Early

The server is unwilling to risk processing a request that might be replayed

426

Upgrade Required

The client should switch to a different protocol

428

Precondition Required

The origin server requires the request to be conditional

429

Too Many Requests

The user has sent too many requests in a given amount of time

431

Request Header Fields Too Large

The server is unwilling to process the request because either an individual header field, or all the header fields collectively, are too large

451

Unavailable For Legal Reasons

The server is denying access to the resource as a consequence of a legal demand

5xx - Server Error

The server failed to fulfill an apparently valid request

500

Internal Server Error

A generic error message when an unexpected condition was encountered

501

Not Implemented

The server either does not recognize the request method, or it lacks the ability to fulfill the request

502

Bad Gateway

The server was acting as a gateway or proxy and received an invalid response from the upstream server

503

Service Unavailable

The server is currently unavailable (because it is overloaded or down for maintenance)

504

Gateway Timeout

The server was acting as a gateway or proxy and did not receive a timely response from the upstream server

505

HTTP Version Not Supported

The server does not support the HTTP protocol version used in the request

506

Variant Also Negotiates

Transparent content negotiation for the request results in a circular reference

507

Insufficient Storage

The server is unable to store the representation needed to complete the request

508

Loop Detected

The server detected an infinite loop while processing the request

510

Not Extended

Further extensions to the request are required for the server to fulfill it

511

Network Authentication Required

The client needs to authenticate to gain network access

Related Tools

Ping Tool

Domain Information Tool

URL Encoder/Decoder

JSON Formatter

Base64 Encoder/Decoder

About This Tool

How It Works

Browse HTTP status codes organized by category (1xx-5xx)
Search for specific codes by number, name, or description
Filter by status code categories for focused browsing
Get detailed explanations for each status code

Common Use Cases

Web developers debugging HTTP responses
System administrators troubleshooting server issues
Students learning about HTTP protocol
Quick reference during API development

Frequently Asked Questions

What are HTTP status codes?

HTTP status codes are three-digit numbers returned by web servers to indicate the result of a client's request. They are grouped into five categories: 1xx (Informational), 2xx (Success), 3xx (Redirection), 4xx (Client Error), and 5xx (Server Error).

What does a 404 error mean?

404 Not Found means the server could not find the requested resource. This is one of the most common client error codes and usually indicates that the URL is incorrect or the resource has been moved or deleted.

What's the difference between 301 and 302 redirects?

301 Moved Permanently indicates the resource has been permanently moved to a new URL, while 302 Found indicates a temporary redirect. Search engines treat these differently for SEO purposes.

What does a 500 Internal Server Error mean?

500 Internal Server Error is a generic server-side error indicating that something went wrong on the server, but the server can't specify what the exact problem is. It's often caused by server misconfigurations or application errors.

When would I see a 401 vs 403 error?

401 Unauthorized means authentication is required or has failed - you need to log in. 403 Forbidden means you're authenticated but don't have permission to access the resource - you're logged in but not allowed.

What are 1xx status codes used for?

1xx Informational status codes indicate that the request was received and the process is continuing. They're rarely seen by end users and are mainly used for protocol-level communication between clients and servers.

Is the 418 "I'm a teapot" status code real?

Yes, HTTP 418 "I'm a teapot" is a real status code defined in RFC 2324 as an April Fools' joke. It's part of the Hyper Text Coffee Pot Control Protocol and is not expected to be implemented by actual HTTP servers.

What does 429 Too Many Requests indicate?

429 Too Many Requests means the user has sent too many requests in a given amount of time. This is commonly used for rate limiting to prevent abuse of web services and APIs.

How can I use this tool for debugging web applications?

Use the search function to quickly find specific error codes you encounter, filter by category to understand different types of responses, and reference the detailed descriptions to understand what each code means and how to resolve issues.

Are there status codes outside the 100-599 range?

No, standard HTTP status codes are three-digit numbers ranging from 100 to 599. Codes outside this range are not part of the HTTP specification and should not be used in standard web applications.

What should I do if I encounter an unfamiliar status code?

Use this reference tool to search for the code by number. If it's not listed, it might be a custom code specific to the application or service you're working with - check the application's documentation for custom status codes.

Why are status codes important for SEO?

Search engines use HTTP status codes to understand how to treat web pages. Proper use of codes like 301 redirects, 404 errors, and 200 success responses helps search engines crawl and index websites correctly, affecting search rankings.