Command Palette

Search for a command to run...

HTTP Status

HTTP Status Lookup

Search HTTP status codes, filter by class, and review practical meanings quickly.

Status Search
Find status entries by code, reason phrase, or practical usage text.

Limits: query up to 256 bytes

Status Detail
Selected status summary, semantics, and practical use context.

Showing default status set. Add a query to narrow results.

200 OK

Class: 2xx Success

Summary: Request completed successfully.

Typical Use: Default success status for most GET and POST requests.

Reference Table
Click a row to inspect details and copy status line.
CodeReasonClass
100Continue1xx Informational
101Switching Protocols1xx Informational
102Processing1xx Informational
103Early Hints1xx Informational
200OK2xx Success
201Created2xx Success
202Accepted2xx Success
203Non-Authoritative Information2xx Success
204No Content2xx Success
205Reset Content2xx Success
206Partial Content2xx Success
207Multi-Status2xx Success
208Already Reported2xx Success
226IM Used2xx Success
300Multiple Choices3xx Redirection
301Moved Permanently3xx Redirection
302Found3xx Redirection
303See Other3xx Redirection
304Not Modified3xx Redirection
305Use Proxy3xx Redirection
307Temporary Redirect3xx Redirection
308Permanent Redirect3xx Redirection
400Bad Request4xx Client Error
401Unauthorized4xx Client Error
402Payment Required4xx Client Error
403Forbidden4xx Client Error
404Not Found4xx Client Error
405Method Not Allowed4xx Client Error
406Not Acceptable4xx Client Error
407Proxy Authentication Required4xx Client Error
408Request Timeout4xx Client Error
409Conflict4xx Client Error
410Gone4xx Client Error
411Length Required4xx Client Error
412Precondition Failed4xx Client Error
413Payload Too Large4xx Client Error
414URI Too Long4xx Client Error
415Unsupported Media Type4xx Client Error
416Range Not Satisfiable4xx Client Error
417Expectation Failed4xx Client Error
418I'm a teapot4xx Client Error
421Misdirected Request4xx Client Error
422Unprocessable Content4xx Client Error
423Locked4xx Client Error
424Failed Dependency4xx Client Error
425Too Early4xx Client Error
426Upgrade Required4xx Client Error
428Precondition Required4xx Client Error
429Too Many Requests4xx Client Error
431Request Header Fields Too Large4xx Client Error
451Unavailable For Legal Reasons4xx Client Error
500Internal Server Error5xx Server Error
501Not Implemented5xx Server Error
502Bad Gateway5xx Server Error
503Service Unavailable5xx Server Error
504Gateway Timeout5xx Server Error
505HTTP Version Not Supported5xx Server Error
506Variant Also Negotiates5xx Server Error
507Insufficient Storage5xx Server Error
508Loop Detected5xx Server Error
510Not Extended5xx Server Error
511Network Authentication Required5xx Server Error

What

HTTP Status Lookup definition

HTTP status codes communicate request outcomes between clients and servers. This lookup tool helps you search by code or phrase and understand response intent.

Cases

Use Cases

1

Interpret API errors during debugging

2

Review status behavior in gateway and CDN logs

3

Pick consistent status codes for REST endpoints

4

Create incident runbooks with status explanations

5

Teach team members semantic differences across 4xx/5xx

6

Copy canonical status lines for documentation

How To

How to Use HTTP Status Lookup

Search by code or phrase, filter classes, and inspect detailed references.

1

Search

Enter a code like 404 or a phrase like timeout, then run search.

2

Filter by class

Use 1xx-5xx filter to narrow results quickly.

3

Inspect and copy

Select a status in the reference table and copy its canonical status line.

Knowledge

HTTP Status Knowledge

Class-Level Semantics
1xx indicates interim responses, 2xx success, 3xx redirection, 4xx client issues, and 5xx server failures.
Operational Consistency
Consistent status usage across services improves client behavior, monitoring quality, and debugging speed.
Incident Triage
Separating 4xx from 5xx early helps identify whether to focus on caller behavior or backend reliability.

FAQ

FAQ

What is the difference between 4xx and 5xx?
4xx usually indicates client-side request issues, while 5xx indicates server-side failures.
When should I use 429?
Use 429 when the client exceeds rate limits and should retry later.
Is 404 always an error?
It signals not found for that resource. It can be expected in some discovery or probing workflows.
Why distinguish 301/302/307/308?
They differ in permanence and whether method/body should be preserved across redirects.
Can this tool replace RFC docs?
It is a fast operational reference. For authoritative protocol behavior, consult RFC specifications.
Does this tool call external APIs?
No. The status catalog is static and processed locally in the browser.
HTTP Status Lookup