Does this cover every status code?

It covers the most commonly used codes across all five categories; it's not the full IANA registry.

Can I search by category?

Yes, typing a category name like 'redirect' or 'server error' filters the list.

Is this list editable?

No, it's a static reference — use it alongside your API documentation.

Is my data uploaded to a server?

No. This tool runs entirely in your browser using standard web APIs, so your input never leaves your device and nothing is logged or stored on our servers.

Does it work offline and on mobile?

Yes. Once the page has loaded it keeps working without a network connection, and the layout is responsive so it stays usable on phones and tablets.

HTTP Status Codes

Searchable reference of HTTP status codes with meaning and usage guidance.

Support

Works Offline

Privacy First

No Login

No API

HTTP status codes

Search by code, name, or category

100Continue

Informational

Client should continue the request.

When to use: Sent before a large request body to confirm the server will accept it.

101Switching Protocols

Informational

Server is switching protocols per the client's request.

When to use: Used during WebSocket handshakes.

200OK

Success

The request succeeded.

When to use: Default success response for GET, PUT, or POST that returns data.

201Created

Success

A new resource was created.

When to use: Return after a successful POST that creates a record.

202Accepted

Success

Request accepted for processing but not completed.

When to use: Use for async or queued operations.

204No Content

Success

Success with no response body.

When to use: Use for DELETE or updates that don't need to return data.

301Moved Permanently

Redirection

Resource permanently moved to a new URL.

When to use: Use for permanent redirects that should update bookmarks/SEO links.

302Found

Redirection

Resource temporarily at a different URL.

When to use: Use for temporary redirects, e.g. after login.

304Not Modified

Redirection

Cached version is still valid.

When to use: Returned in response to conditional GET requests (ETag / If-Modified-Since).

307Temporary Redirect

Redirection

Like 302 but preserves the HTTP method.

When to use: Use when a redirect must keep POST/PUT semantics intact.

308Permanent Redirect

Redirection

Like 301 but preserves the HTTP method.

When to use: Permanent redirect that must not change the request method.

400Bad Request

Client Error

Malformed request syntax or invalid parameters.

When to use: Return when validation fails on the client's input.

401Unauthorized

Client Error

Authentication is required or has failed.

When to use: Return when credentials are missing or invalid.

403Forbidden

Client Error

Authenticated but not permitted to access the resource.

When to use: Return when the user lacks permission, even if identity is known.

404Not Found

Client Error

Resource does not exist.

When to use: Return for unknown routes or deleted/missing resources.

405Method Not Allowed

Client Error

HTTP method not supported for this resource.

When to use: Return when e.g. DELETE is called on a read-only endpoint.

409Conflict

Client Error

Request conflicts with the current state of the resource.

When to use: Use for edit conflicts, duplicate resource creation, etc.

410Gone

Client Error

Resource existed but was permanently removed.

When to use: Use instead of 404 when you want to signal permanent removal.

415Unsupported Media Type

Client Error

Request payload format is not supported.

When to use: Return when Content-Type doesn't match what the endpoint accepts.

422Unprocessable Entity

Client Error

Request is well-formed but semantically invalid.

When to use: Common for form/schema validation errors in APIs.

429Too Many Requests

Client Error

Client has sent too many requests in a given time.

When to use: Return when rate limits are exceeded, often with Retry-After.

500Internal Server Error

Server Error

Generic server-side failure.

When to use: Return for unexpected exceptions that aren't the client's fault.

501Not Implemented

Server Error

Server doesn't support the requested functionality.

When to use: Use for unimplemented endpoints or methods.

502Bad Gateway

Server Error

Upstream server returned an invalid response.

When to use: Common when a reverse proxy or gateway fails to reach a backend.

503Service Unavailable

Server Error

Server temporarily unable to handle requests.

When to use: Use during maintenance windows or overload, often with Retry-After.

504Gateway Timeout

Server Error

Upstream server did not respond in time.

When to use: Use when a proxy times out waiting on a backend.

About the HTTP Status Codes

Browse a searchable reference of common HTTP status codes grouped by category (informational, success, redirection, client error, server error), including what each means and when to use it in an API.

Examples

Search 404

Output

404 Not Found — Resource does not exist.

Keyboard shortcuts

Copy the main outputCtrl / ⌘ + Shift + C
Download the resultCtrl / ⌘ + S
Share this toolCtrl / ⌘ + Shift + S
Reset the inputsAlt + R
Open the tool search paletteCtrl / ⌘ + K

Related tools

Bulk URL Status Checker

Network & IP

Check HTTP status codes and redirects for many URLs at once.

Cookie Attribute Analyzer

Network & IP

Parse Set-Cookie headers and flag security issues.

HTTP Cache Header Planner

Network & IP

Plan Cache-Control, ETag and max-age headers for any asset type.

HTTP Header Comparator

Network & IP

Diff two sets of HTTP headers, case-insensitively.

HTTP Headers Explainer

Network & IP

Look up common HTTP headers and explain pasted raw headers.

HTTP/2 & TLS Version Test

Network & IP

See which TLS versions a site accepts and whether it serves HTTP/2.

Frequently asked questions

HTTP status codes developers actually need
Not all 60-odd status codes matter day to day. Here's the practical subset, what each one actually implies, and common mix-ups.
Understanding CORS errors and how to fix them
Why 'No Access-Control-Allow-Origin header' shows up, what the browser is actually enforcing, and the exact headers that fix each case.
Testing APIs from the browser: what works, what CORS blocks, and why
How a browser-based REST client sends real requests, why some endpoints fail with a CORS error, and how to work around it without installing anything.
A browser API client with environments, history and saved requests
Environment variables, request history and a saved collection turn a one-off request form into something you can actually work in — without installing a desktop client.

Version 1.0.0 · Updated 2026-08-06 · Runs entirely in your browser

HTTP Status Codes

About the HTTP Status Codes

Examples

Keyboard shortcuts

Related tools

Bulk URL Status Checker

Cookie Attribute Analyzer

HTTP Cache Header Planner

HTTP Header Comparator

HTTP Headers Explainer

HTTP/2 & TLS Version Test

Frequently asked questions

Does this cover every status code?

Can I search by category?

Is this list editable?

Is my data uploaded to a server?

Does it work offline and on mobile?

Read more