Web & Network

HTTP Status Code Lookup

Look up HTTP status codes with examples

Look up any HTTP status code to understand what it means and when it's used, from 200 OK and 301 Moved Permanently to 404 Not Found and 503 Service Unavailable. A quick reference for debugging API responses, configuring redirects, and explaining errors.

Runs 100% in your browser · no upload, no tracking, no ads

HTTP Status Codes

100

Continue

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

Informational

101

Switching Protocols

The requester has asked the server to switch protocols and the server has agreed to do so.

Informational

102

Processing

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

Informational

103

Early Hints

Preliminary headers, mainly Link, sent before the final response so the client can start preloading resources.

Informational

200

The request has succeeded.

Success

201

Created

The request has been fulfilled and resulted in a new resource being created.

Success

202

Accepted

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

Success

203

Non-Authoritative Information

The request succeeded, but the returned metadata was modified by a transforming proxy.

Success

204

No Content

The server successfully processed the request and is not returning any content.

Success

205

Reset Content

The request succeeded and the client should reset the document view, such as clearing a form.

Success

206

Partial Content

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

Success

207

Multi-Status

The response body carries separate status codes for multiple independent operations (WebDAV).

Success

208

Already Reported

The members of a WebDAV binding were already listed earlier in the same response and are not repeated.

Success

226

IM Used

The response is a representation of the result of one or more instance manipulations applied to the current instance.

Success

300

Multiple Choices

The request has more than one possible representation and the client should pick one.

Redirection

301

Moved Permanently

This and all future requests should be directed to the given URI.

Redirection

302

Found

The resource was found but is temporarily located at a different URI.

Redirection

303

See Other

The response to the request can be found under another URI using a GET method.

Redirection

304

Not Modified

The resource has not been modified since the last request.

Redirection

305

Use Proxy

Deprecated: the requested resource must be accessed through the proxy given in the Location header.

Redirection

307

Temporary Redirect

The request should be repeated with another URI, but future requests should still use the original URI.

Redirection

308

Permanent Redirect

The request and all future requests should be repeated using another URI.

Redirection

400

Bad Request

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

Client Error

401

Unauthorized

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

Client Error

402

Payment Required

Reserved for future use; some APIs use it for quota or billing problems.

Client Error

403

Forbidden

The server understood the request but refuses to authorize it.

Client Error

404

Not Found

The requested resource could not be found but may be available in the future.

Client Error

405

Method Not Allowed

The request method is not supported for the requested resource.

Client Error

406

Not Acceptable

The resource cannot produce a representation matching the request's Accept headers.

Client Error

407

Proxy Authentication Required

The client must first authenticate itself with the proxy.

Client Error

408

Request Timeout

The server timed out waiting for the request.

Client Error

409

Conflict

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

Client Error

410

Gone

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

Client Error

411

Length Required

The server refuses to accept the request without a defined Content-Length header.

Client Error

412

Precondition Failed

One or more conditions in the request headers (If-Match, If-Unmodified-Since) evaluated to false.

Client Error

413

Payload Too Large

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

Client Error

414

URI Too Long

The URI provided was too long for the server to process.

Client Error

415

Unsupported Media Type

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

Client Error

416

Range Not Satisfiable

The range specified by the Range header cannot be fulfilled for the target resource.

Client Error

417

Expectation Failed

The expectation given in the Expect request header could not be met by the server.

Client Error

418

I'm a teapot

The server refuses to brew coffee because it is, permanently, a teapot (RFC 2324, an April Fools RFC that stuck).

Client Error

421

Misdirected Request

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

Client Error

422

Unprocessable Entity

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

Client Error

423

Locked

The source or destination resource of a method is locked (WebDAV).

Client Error

424

Failed Dependency

The request failed because it depended on another request that failed (WebDAV).

Client Error

425

Too Early

The server is unwilling to risk processing a request that might be replayed (TLS early data).

Client Error

426

Upgrade Required

The server refuses to perform the request using the current protocol; the client should upgrade.

Client Error

428

Precondition Required

The origin server requires the request to be conditional to prevent lost updates.

Client Error

429

Too Many Requests

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

Client Error

431

Request Header Fields Too Large

The server refuses to process the request because its header fields are too large.

Client Error

451

Unavailable For Legal Reasons

The resource is unavailable due to a legal demand, such as censorship or court order.

Client Error

500

Internal Server Error

A generic error message when an unexpected condition was encountered.

Server Error

501

Not Implemented

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

Server Error

502

Bad Gateway

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

Server Error

503

Service Unavailable

The server is currently unavailable due to temporary overload or maintenance.

Server Error

504

Gateway Timeout

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

Server Error

505

HTTP Version Not Supported

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

Server Error

506

Variant Also Negotiates

The server has a configuration error: the chosen variant is itself configured to negotiate content.

Server Error

507

Insufficient Storage

The server is unable to store the representation needed to complete the request (WebDAV).

Server Error

508

Loop Detected

The server terminated an operation because it encountered an infinite loop (WebDAV).

Server Error

510

Not Extended

Further extensions to the request are required for the server to fulfil it.

Server Error

511

Network Authentication Required

The client needs to authenticate to gain network access, typically shown by captive portals.

Server Error

Code Details

Select a status code to view detailed information

HTTP Status Codes

• 1xx: Informational responses
• 2xx: Successful responses
• 3xx: Redirection messages
• 4xx: Client error responses
• 5xx: Server error responses

Best Practices

• Use appropriate status codes for your API
• Provide meaningful error messages
• Handle all possible status codes in clients
• Use 2xx for successful operations
• Use 4xx for client errors, 5xx for server errors

How to use HTTP Status Code Lookup

Search or browse for an HTTP status code.
Read its name, category, and meaning.
Review when the code is appropriate to use.
Use the explanation to debug your request or response.

Frequently asked questions

What do the status code categories mean?

1xx are informational, 2xx indicate success, 3xx are redirects, 4xx are client errors (the request was wrong), and 5xx are server errors (the server failed to fulfill a valid request).

What's the difference between 301 and 302?

301 is a permanent redirect (browsers and search engines update to the new URL) while 302 is temporary and the original URL should still be treated as canonical.

When should I return 401 vs 403?

401 Unauthorized means authentication is missing or invalid; 403 Forbidden means you're authenticated but not allowed to access the resource.

Related Web & Network tools

User Agent Parser: Parse user agent strings to extract browser and device info
IP Address Lookup: Get location and network info for IP addresses
DNS Lookup Tool: Check DNS records (A, MX, TXT, etc.) for any domain name
Server Status Checker: Check server health and monitor website availability
SSL Certificate Checker: Check SSL certificate validity and expiration dates
SEO Analyzer: Analyze and optimize your website's SEO performance