My Tool Studio
Developer

HTTP Status Codes

This http status codes list puts every response code you'll realistically encounter on one searchable page, from 100 Continue through 511 Network Authentication Required. Each entry shows the code, its official name, a color-coded group badge, and a one-line description of what the server is telling you. Reach for it when an API returns 422 and you can't remember how that differs from 400, or when you need a quick http error codes lookup in the middle of a debugging session. The table doubles as an http response codes reference for the whole team: filter by number, name, or description text, then copy any code with a single click.

Always freeNo sign upRuns in your browser
32 / 32
CodeNameGroupDescription
100Continue1xx InformationalServer received the request headers; client should send the body.
101Switching Protocols1xx InformationalServer is switching protocols as requested.
103Early Hints1xx InformationalUsed to preload resources before final response.
200OK2xx SuccessStandard response for successful HTTP requests.
201Created2xx SuccessRequest succeeded and a new resource was created.
202Accepted2xx SuccessRequest accepted for processing but not yet complete.
204No Content2xx SuccessRequest succeeded; no content to return.
206Partial Content2xx SuccessServer delivered only part of the resource (range request).
301Moved Permanently3xx RedirectionResource has been permanently moved to a new URL.
302Found3xx RedirectionResource temporarily moved to a different URL.
303See Other3xx RedirectionResponse can be found at a different URL (use GET).
304Not Modified3xx RedirectionCached version of the resource is still valid.
307Temporary Redirect3xx RedirectionLike 302 but method must not change.
308Permanent Redirect3xx RedirectionLike 301 but method must not change.
400Bad Request4xx Client ErrorMalformed syntax, server cannot process the request.
401Unauthorized4xx Client ErrorAuthentication is required and has failed.
403Forbidden4xx Client ErrorServer refuses to authorize the request.
404Not Found4xx Client ErrorRequested resource could not be found.
405Method Not Allowed4xx Client ErrorRequest method not supported for this resource.
408Request Timeout4xx Client ErrorServer timed out waiting for the request.
409Conflict4xx Client ErrorRequest conflicts with current state of the resource.
410Gone4xx Client ErrorResource is no longer available and will not return.
413Payload Too Large4xx Client ErrorRequest body exceeds server limits.
418I'm a Teapot4xx Client ErrorRFC 2324 April Fools' joke, server refuses to brew coffee.
422Unprocessable Entity4xx Client ErrorRequest well-formed but contains semantic errors.
429Too Many Requests4xx Client ErrorClient has sent too many requests in a given time.
500Internal Server Error5xx Server ErrorGeneric error, something went wrong on the server.
501Not Implemented5xx Server ErrorServer does not support the functionality required.
502Bad Gateway5xx Server ErrorUpstream server returned an invalid response.
503Service Unavailable5xx Server ErrorServer is temporarily down or overloaded.
504Gateway Timeout5xx Server ErrorUpstream server failed to respond in time.
511Network Authentication Required5xx Server ErrorClient needs to authenticate to gain network access.

How to use

01

Search for a code or symptom

Type a number like 404, a name like Gateway Timeout, or any word from a description into the search field. The table filters live across the code, name, and description columns.

02

Check the group badge

Every row carries a colored badge: green marks 2xx Success, blue 3xx Redirection, yellow 4xx Client Error, and red 5xx Server Error. The family alone tells you which side of the connection failed.

03

Copy the code you need

Click the copy icon beside any code number to grab it for a bug report, a test assertion, or the API spec you're writing, without retyping it.

Why HTTP Status Codes

Common questions

What's the difference between a 401 and a 403 response?
401 Unauthorized means authentication failed or is missing, so the server doesn't know who you are yet. 403 Forbidden means it knows exactly who you are and still refuses. In practice, 401 says try logging in, while 403 says logging in won't help.
Does this http status codes list include 308 and 422?
Yes, along with 103 Early Hints, 429 Too Many Requests, and other modern codes that older cheatsheets tend to skip. It even lists 418 I'm a Teapot, the RFC 2324 joke code that some real servers return to blocked clients.
Why do 4xx status codes matter most during frontend work?
Because 4xx status codes mean the request itself is wrong: malformed syntax gets 400, missing auth gets 401, an unknown route gets 404, an unsupported verb gets 405. When one shows up, the fix belongs in your client code or payload, not on the server.
How can I tell whether a 502 or a 504 is my server's fault?
Both point at an upstream dependency behind a proxy or load balancer. A 502 Bad Gateway means the upstream answered with something invalid, while a 504 Gateway Timeout means it never answered in time. Start with the reverse proxy logs to see which hop broke.
Is a 429 something my client should retry automatically?
Only with backoff. 429 Too Many Requests means you've hit a rate limit, and if the response includes a Retry-After header, wait at least that long. Retrying instantly in a loop is the fastest way to turn a throttle into a block.
When would a server return 204 instead of 200?
204 No Content signals success with nothing to send back, which fits DELETE requests or settings updates where the client already has the state. Returning 200 with an empty body works too, but 204 states the intent explicitly and skips body parsing.
Can the search find a code from its description text?
Yes, the filter runs over descriptions as well as codes and names. Typing cache surfaces 304 Not Modified, and typing range brings up 206 Partial Content, which is handy when you remember the behavior but not the number.

More Developer tools

View all