InstantTools.siteZero Latency Utilities
dev Tool
100% In-Memory (Zero Server Upload)

HTTP Status Code Reference

Search the common HTTP status codes by number, name or class, with what each one means and the usual reason it appears.

Search, filter and jump

Status codes

32 of 32 shown
CodeNameClassDescriptionTypical cause / what to doCopy
100Continue
1xx
The request headers have been received and the client should continue sending the body.Sent by servers that need the full request before responding. Clients rarely see it directly — expect 100 Continue on large uploads.
101Switching Protocols
1xx
The server is switching to the protocol requested in the Upgrade header.Used for WebSocket handshakes and HTTP/2 upgrades. Seeing it on a normal page load is unexpected.
200OK
2xx
The request succeeded and the response body contains the result.The default success response for GET, POST, PUT and DELETE. If you expected a 201 or 204, check your API contract.
201Created
2xx
The request succeeded and one or more new resources were created.Correct for POST that creates something. The Location header usually points at the new resource.
202Accepted
2xx
The request was accepted for processing but has not been completed.Use for asynchronous jobs. Poll the status URL you return; a 202 does not mean the work is done.
204No Content
2xx
The request succeeded and there is deliberately no response body.Standard for DELETE and successful PUT/PATCH. Do not try to parse a body — there isn't one.
206Partial Content
2xx
The server is delivering only part of the requested resource (range request).Used for video streaming, audio seeking and resumable downloads driven by the Range header.
301Moved Permanently
3xx
The resource has a new permanent URL.Search engines and browsers cache it aggressively. Use when the old URL should stop being advertised; update internal links.
302Found
3xx
The resource is temporarily at a different URL.Classic post-login redirect. Historically browsers changed POST to GET on 302, so use 303 for POST workflows.
303See Other
3xx
The response to the request can be retrieved with a GET at another URL.The right choice after a successful POST — it forces the follow-up request to be a GET.
304Not Modified
3xx
The cached copy is still valid; no body is sent.Returned when If-None-Match or If-Modified-Since matches. Correct and efficient — not an error.
307Temporary Redirect
3xx
Temporary redirect that must preserve the original method and body.Safer than 302 for POST: the request is replayed unchanged at the new URL.
308Permanent Redirect
3xx
Permanent redirect that must preserve the original method and body.The method-preserving, cacheable sibling of 301 — preferred for permanent HTTPS or API migrations.
400Bad Request
4xx
The server cannot process the request because of a client error.Malformed syntax, invalid parameters or a failed schema validation. Fix the request; retrying unchanged will fail again.
401Unauthorized
4xx
Authentication is required and has failed or was not provided.Misleadingly named — it means unauthenticated, not unauthorised. Send valid credentials or obtain a token; check the WWW-Authenticate header.
403Forbidden
4xx
The server understood the request but refuses to authorise it.The identity is known but lacks permission. Logging in again will not help — the role or policy must change.
404Not Found
4xx
The server cannot find the requested resource.Wrong URL, missing record, or a deliberately hidden resource. Check the path, and consider whether a 403 would be less revealing.
405Method Not Allowed
4xx
The method is understood by the resource but not supported by it.For example POST to a read-only endpoint. The Allow header lists which methods do work.
408Request Timeout
4xx
The server timed out waiting for the client to send the request.Slow client or network stall. Retry with backoff; for large uploads, check the body-size limits.
409Conflict
4xx
The request conflicts with the current state of the resource.Version conflicts on updates, duplicate keys, or a failed concurrency check. Re-read the resource and retry with the current state.
410Gone
4xx
The resource was deliberately removed and is permanently unavailable.Stronger than 404: it will never come back. Use for content removed on purpose, e.g. a retired endpoint.
413Content Too Large
4xx
The request body is larger than the server is willing to process.Upload or payload size limit exceeded. Reduce the payload, chunk the upload, or ask for the limit to be raised.
415Unsupported Media Type
4xx
The body format is not supported by this endpoint.A Content-Type mismatch — e.g. sending JSON to a form-only endpoint. Check the Accept and Content-Type headers.
418I'm a Teapot
4xx
A joke code from an April Fools' RFC, used to indicate that the server refuses to brew coffee.Deliberately not implemented. A real 418 in production usually means an unhandled branch in your code.
422Unprocessable Content
4xx
The syntax is correct but the content failed semantic validation.Well-formed JSON that fails business rules — e.g. a past date or an unknown enum value. The body should describe the failing field.
429Too Many Requests
4xx
The client has sent too many requests in a given amount of time.Rate limiting. Back off and retry after the interval in the Retry-After header; add jitter so clients don't resynchronise.
500Internal Server Error
5xx
The server hit an unexpected condition and could not fulfil the request.An unhandled exception or bug on the server. This is not the client's fault — retrying may work, but the server must be investigated.
501Not Implemented
5xx
The server does not support the functionality required to fulfil the request.The method or feature is not implemented at all — different from 405, where the method exists for the resource.
502Bad Gateway
5xx
A server acting as a gateway or proxy received an invalid response from the upstream server.The upstream application crashed, timed out or is unreachable. Check the upstream service, not the client.
503Service Unavailable
5xx
The server is temporarily unable to handle the request.Planned maintenance, overload or a dependency that is down. Clients should retry with backoff and honour Retry-After.
504Gateway Timeout
5xx
A gateway or proxy did not receive a timely response from the upstream server.The upstream took too long to respond. Often fixed with a longer proxy timeout, pagination, or by speeding up the slow query.
505HTTP Version Not Supported
5xx
The server does not support the HTTP protocol version used in the request.A client sent a version the server cannot handle — rare, usually an old client against a strict server.

About these codes

HTTP status codes are registered with IANA and their semantics are defined by the HTTP specifications (RFC 9110 and friends). The 1xx–5xx class tells you who is responsible: 4xx means the client must change something, 5xx means the server failed. The bundled table covers 32 of the codes people actually hit — it is not the complete IANA registry, so a missing code means “not in this reference”, not “invalid”. The listed causes are typical cases, not rules; real servers misuse codes. This is a static local reference and no HTTP request is ever made.

429 and 503 are the two codes a client should retry — with exponential backoff and jitter.

About HTTP Status Code Reference

Find out what a response code means and where it comes from. Search across the common 1xx to 5xx codes, filter by class, or jump straight to one code for a detailed card. Each entry gives the status name, the class it belongs to, what the code signifies, and the usual reason you would meet it — from a moved page and a missing resource through to a rate limit or an upstream gateway timeout. The list is a local reference and no request is ever sent from this page.

Key Features & Privacy Guarantee

  • Zero server transmission: all computation happens instantly in your local browser runtime.
  • No sign-up, no subscriptions, and no usage quotas.
  • Optimized for maximum speed, accuracy, and lightweight performance.
  • Instant one-click clipboard copying.

Frequently Asked Questions

Common questions and helpful answers about this utility.

It can mean the link is wrong, the route changed, or a page returns 404 to a bot but not to a person. Case-sensitive paths and differences between server-rendered and client-rendered routes are common culprits.