HTTP Status Codes

Look up what each HTTP response status code means.

Back to tools

Tool Panel

Processed locally
Loading tool...
About HTTP Status Codes

Browses HTTP status codes by class (1xx–5xx) with their meanings and typical uses, searchable.

All HTTP status codes

The standard 1xx–5xx response codes, grouped by the class their first digit names. The tool above looks up the common ones by keyword; this is the complete table, including the WebDAV and later extension codes. Reason phrases follow RFC 9110.

1xx — Informational

100 Continue
The server received the request headers and the client should send the body.
101 Switching Protocols
The client asked to change protocols and the server agreed — what a successful WebSocket upgrade returns.
102 Processing
The server is still working on a long request, so the client does not time out (WebDAV).
103 Early Hints
Sends link headers before the final response so the browser can start preloading.

2xx — Success

200 OK
The request succeeded and the body carries the result.
201 Created
The request created a resource; the Location header points at it.
202 Accepted
The request was accepted for processing but is not finished — usually queued.
203 Non-Authoritative Information
The response came from a proxy that modified the origin payload.
204 No Content
Succeeded with nothing to return — common for DELETE and form posts.
205 Reset Content
Succeeded, and the client should reset the document view, such as clearing a form.
206 Partial Content
Returns part of a resource, as asked by a Range header — how resumable downloads work.
207 Multi-Status
Carries several independent results, each with its own status, in one body (WebDAV).
208 Already Reported
The same binding was already reported in this 207 response, so it is not repeated (WebDAV).
226 IM Used
The server applied one or more instance manipulations, such as delta encoding.

3xx — Redirection

300 Multiple Choices
Several representations exist and the client picks one; rarely used in practice.
301 Moved Permanently
The resource now lives at a new URL, and search engines pass the ranking on.
302 Found
Temporary redirect; historically implemented loosely, and some clients turn POST into GET.
303 See Other
Fetch the result from another URL with GET — the usual answer to a form post.
304 Not Modified
The cached copy is still fresh, so no body is sent.
307 Temporary Redirect
Temporary redirect that preserves the method and body.
308 Permanent Redirect
Permanent redirect that preserves the method — the strict version of 301.

4xx — Client errors

400 Bad Request
The server cannot understand the request — malformed syntax or invalid parameters.
401 Unauthorized
Authentication is required, or the credentials are wrong.
402 Payment Required
Reserved for payment systems and almost never used in practice.
403 Forbidden
The server understood the request but refuses to authorise it, whatever the credentials.
404 Not Found
No resource exists at this URL — it says nothing about whether it was ever there.
405 Method Not Allowed
The URL exists but not for this method; the Allow header lists what works.
406 Not Acceptable
No representation matches the Accept headers.
407 Proxy Authentication Required
The proxy in front of the server demands credentials, not the origin.
408 Request Timeout
The client took too long to finish sending the request.
409 Conflict
The request conflicts with the resource state — a concurrent edit, for example.
410 Gone
The resource is permanently gone, which tells an index it can be dropped.
411 Length Required
The request must carry a Content-Length header.
412 Precondition Failed
A precondition such as If-Match did not hold, so the data changed meanwhile.
413 Content Too Large
The request body exceeds what the server accepts.
414 URI Too Long
The URL is longer than the server will process, usually because data went into the query string.
415 Unsupported Media Type
This endpoint does not support the media type of the body.
416 Range Not Satisfiable
The requested byte range cannot be served for this resource.
417 Expectation Failed
The expectation in the Expect header cannot be met.
418 I'm a teapot
An April Fools' joke from RFC 2324 that libraries and servers still implement.
421 Misdirected Request
The request reached a server that cannot answer for this authority.
422 Unprocessable Content
The syntax is fine but the contents fail validation.
423 Locked
The resource is locked by another operation (WebDAV).
424 Failed Dependency
The request failed because a request it depends on failed (WebDAV).
425 Too Early
The server refuses a request that might be replayed in an early handshake.
426 Upgrade Required
The server requires a different protocol; the Upgrade header says which.
428 Precondition Required
The server wants a conditional request so concurrent updates cannot overwrite each other.
429 Too Many Requests
The client hit a rate limit; Retry-After may say when to try again.
431 Request Header Fields Too Large
The request headers are too long — an oversized cookie is the usual cause.
451 Unavailable For Legal Reasons
Blocked for legal reasons, such as a takedown order.

5xx — Server errors

500 Internal Server Error
Something on the server broke; the catch-all 5xx.
501 Not Implemented
The server does not support this method.
502 Bad Gateway
An upstream server returned something the gateway could not use.
503 Service Unavailable
The server is overloaded or under maintenance, often with Retry-After.
504 Gateway Timeout
An upstream server did not answer in time — the timeout counterpart of 502.
505 HTTP Version Not Supported
The HTTP version of the request is not supported.
506 Variant Also Negotiates
A configuration error in content negotiation.
507 Insufficient Storage
The server has no space left to store the request (WebDAV).
508 Loop Detected
An infinite loop was detected while processing the request (WebDAV).
510 Not Extended
Further extensions to the request are required.
511 Network Authentication Required
A captive portal asks the client to authenticate before reaching the network.
  • 1

    All processing happens locally in your browser, data never leaves your device

  • 2

    Quick network parameter parsing at a glance

  • 3

    Multiple network tools in one place

Related tools

View all
Network Tools

IP Info

See your public IP address and where it resolves to.

Network Tools
IP Info
Network Tools

URL Parser

Break a URL into protocol, host, path and query parameters.

Network Tools
URL Parser
Network Tools

URL Query Builder

Assemble long query strings without escaping mistakes.

Network Tools
URL Query Builder