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.

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.

Code	Reason	Class
100	Continue	1xx Informational
101	Switching Protocols	1xx Informational
102	Processing	1xx Informational
103	Early Hints	1xx Informational
200	OK	2xx Success
201	Created	2xx Success
202	Accepted	2xx Success
203	Non-Authoritative Information	2xx Success
204	No Content	2xx Success
205	Reset Content	2xx Success
206	Partial Content	2xx Success
207	Multi-Status	2xx Success
208	Already Reported	2xx Success
226	IM Used	2xx Success
300	Multiple Choices	3xx Redirection
301	Moved Permanently	3xx Redirection
302	Found	3xx Redirection
303	See Other	3xx Redirection
304	Not Modified	3xx Redirection
305	Use Proxy	3xx Redirection
307	Temporary Redirect	3xx Redirection
308	Permanent Redirect	3xx Redirection
400	Bad Request	4xx Client Error
401	Unauthorized	4xx Client Error
402	Payment Required	4xx Client Error
403	Forbidden	4xx Client Error
404	Not Found	4xx Client Error
405	Method Not Allowed	4xx Client Error
406	Not Acceptable	4xx Client Error
407	Proxy Authentication Required	4xx Client Error
408	Request Timeout	4xx Client Error
409	Conflict	4xx Client Error
410	Gone	4xx Client Error
411	Length Required	4xx Client Error
412	Precondition Failed	4xx Client Error
413	Payload Too Large	4xx Client Error
414	URI Too Long	4xx Client Error
415	Unsupported Media Type	4xx Client Error
416	Range Not Satisfiable	4xx Client Error
417	Expectation Failed	4xx Client Error
418	I'm a teapot	4xx Client Error
421	Misdirected Request	4xx Client Error
422	Unprocessable Content	4xx Client Error
423	Locked	4xx Client Error
424	Failed Dependency	4xx Client Error
425	Too Early	4xx Client Error
426	Upgrade Required	4xx Client Error
428	Precondition Required	4xx Client Error
429	Too Many Requests	4xx Client Error
431	Request Header Fields Too Large	4xx Client Error
451	Unavailable For Legal Reasons	4xx Client Error
500	Internal Server Error	5xx Server Error
501	Not Implemented	5xx Server Error
502	Bad Gateway	5xx Server Error
503	Service Unavailable	5xx Server Error
504	Gateway Timeout	5xx Server Error
505	HTTP Version Not Supported	5xx Server Error
506	Variant Also Negotiates	5xx Server Error
507	Insufficient Storage	5xx Server Error
508	Loop Detected	5xx Server Error
510	Not Extended	5xx Server Error
511	Network Authentication Required	5xx 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

Interpret API errors during debugging

Review status behavior in gateway and CDN logs

Pick consistent status codes for REST endpoints

Create incident runbooks with status explanations

Teach team members semantic differences across 4xx/5xx

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.

Search

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

Filter by class

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

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

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.

Network Tools

View all →

DNS Lookup

Perform DNS lookups (A, MX, TXT, etc.) for any domain.

IP & Location Lookup

See your current public IP, ISP, and approximate location.

CIDR / Subnet Calculator

Enter an IPv4 CIDR to instantly calculate the network address, broadcast address, and host range.

User Agent Parser

Analyze browser, OS, device, and engine details from any user agent string.