WebTools
WebTools

Free online tools for developers, designers, and everyday users. 100+ tools, no signup required.

Popular Tools

  • JSON Formatter
  • Base64 Codec
  • QR Code
  • Compress
  • Text Diff

Resources

  • About Us
  • Blog
  • Settings

More Tools

  • APIPulse
  • CodeJet
  • PeerBeam

Legal

  • Privacy Policy
© 2026 WebTools. All rights reserved.
NetworkHTTP Status Codes

HTTP Status Codes

Quickly look up any HTTP status code and understand its meaning. This comprehensive reference covers all official HTTP status codes from 1xx Informational to 5xx Server Error, with clear descriptions, common use cases, and helpful tips — all processed in your browser with no data sent to any server.

Header Label
67 Items
100
Continue

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

101
Switching Protocols

The server is switching protocols as requested by the client.

102
Processing

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

200
OK

The request has succeeded.

201
Created

The request has been fulfilled and a new resource has been created.

202
Accepted

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

203
Non-Authoritative Information

The returned meta-information is from a local or third-party copy, not the origin server.

204
No Content

The server has fulfilled the request but does not need to return an entity-body.

205
Reset Content

The server has fulfilled the request and the user agent should reset the document view.

206
Partial Content

The server has fulfilled the partial GET request for the resource.

207
Multi-Status

The message body that follows is an XML message with multiple response codes.

208
Already Reported

The members of a DAV binding have already been enumerated in a previous reply.

226
IM Used

The server has fulfilled a GET request for the resource with instance manipulations.

300
Multiple Choices

The requested resource has multiple choices, each with a different URI.

301
Moved Permanently

The requested resource has been assigned a new permanent URI.

302
Found

The requested resource resides temporarily under a different URI.

303
See Other

The response to the request can be found under another URI using a 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 requested resource resides temporarily under a different URI.

308
Permanent Redirect

The requested resource has been assigned a new permanent URI.

400
Bad Request

The server could not understand the request due to malformed syntax.

401
Unauthorized

The request requires user authentication.

402
Payment Required

This code is reserved for future use.

403
Forbidden

The server understood the request, but is refusing to fulfill it.

404
Not Found

The server has not found anything matching the Request-URI.

405
Method Not Allowed

The method specified in the Request-Line is not allowed for the identified resource.

406
Not Acceptable

The resource identified by the request is not capable of generating response entities.

407
Proxy Authentication Required

The client must first authenticate itself with the proxy.

408
Request Timeout

The client did not produce a request within the time the server was prepared to wait.

409
Conflict

The request could not be completed due to a conflict with the current state of the resource.

410
Gone

The requested resource is no longer available at the server and no forwarding address is known.

411
Length Required

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

412
Precondition Failed

The precondition given in one or more of the request-header fields evaluated to false.

413
Payload Too Large

The server is refusing to process a request because the request payload is larger than the server is willing to process.

414
URI Too Long

The server is refusing to service the request because the Request-URI is longer than the server is willing to interpret.

415
Unsupported Media Type

The server is refusing to service the request because the entity of the request is in a format not supported.

416
Range Not Satisfiable

The requested Range header field cannot be fulfilled.

417
Expectation Failed

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

418
I'm a Teapot

The resulting entity body may be short and stout.

421
Misdirected Request

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

422
Unprocessable Entity

The server understands the content type and syntax but was unable to process the contained instructions.

423
Locked

The source or destination resource of a method is locked.

424
Failed Dependency

The method could not be performed because the requested action depended on another action that 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 its header fields are too large.

451
Unavailable For Legal Reasons

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

500
Internal Server Error

The server encountered an unexpected condition which prevented it from fulfilling the request.

501
Not Implemented

The server does not support the functionality required to fulfill the request.

502
Bad Gateway

The server received an invalid response from the upstream server.

503
Service Unavailable

The server is currently unable to handle the request due to temporary overloading or maintenance.

504
Gateway Timeout

The server did not receive a timely response from the upstream server.

505
HTTP Version Not Supported

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

506
Variant Also Negotiates

Transparent content negotiation for the request results in a circular reference.

507
Insufficient Storage

The method could not be performed on the resource because the server is unable to store the representation.

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.

499
Client Closed Request

The client closed the connection before the server could respond. (Nginx non-standard)

520
Web Server Unknown Error

The origin server returned an unknown or unexpected response. (Cloudflare)

521
Web Server Is Down

The origin server has refused the connection from Cloudflare. (Cloudflare)

522
Connection Timed Out

Cloudflare could not negotiate a TCP handshake with the origin server. (Cloudflare)

523
Origin Is Unreachable

Cloudflare could not reach the origin server. (Cloudflare)

524
A Timeout Occurred

Cloudflare established a TCP connection but did not receive a timely HTTP response. (Cloudflare)

Total Count

Section Title

Desc1xx

Desc2xx

Desc3xx

Desc4xx

Desc5xx

Badge1xxBadge2xxBadge3xxBadge4xxBadge5xx

HTTP Status Code Reference & Lookup

Quickly look up any HTTP status code and understand its meaning. This comprehensive reference covers all official HTTP status codes from 1xx Informational to 5xx Server Error, with clear descriptions, common use cases, and helpful tips — all processed in your browser with no data sent to any server.

  • Complete reference of all official HTTP status codes across five categories
  • Instant search by code number or keyword to find any status code fast
  • Organized by category: Informational, Success, Redirection, Client Error, and Server Error
  • Detailed descriptions with common use cases and troubleshooting tips
  • One-click copy of status codes and descriptions for documentation
  • Filter by category to browse codes within a specific range
  • Works entirely in your browser — no server calls, fully private

How to Use the HTTP Status Code Lookup

  1. 1

    Search by code or keyword

    Type an HTTP status code (e.g., 404) or a keyword (e.g., 'not found') into the search field.

  2. 2

    Browse by category

    Click on a category tab like 2xx Success or 4xx Client Error to see all codes in that range.

  3. 3

    View detailed information

    Click on any status code to see its full description, common causes, and recommended actions.

  4. 4

    Copy for your reference

    Use the copy button to copy the status code and its description for use in your documentation or code.

Frequently Asked Questions

Related Tools

JSON FormatterJWT DecoderMIME Type LookupIP Address LookupURL Encoder/DecoderHTML Entity Encoder/Decoder