http · 1xx · 2xx · 3xx · 4xx · 5xx · live

All HTTP status codes

Searchable catalog of every standard HTTP status code with RFC references, retryability, and clear descriptions. Runs entirely in your browser.

HTTP Status Codes

Total

registered

Visible

all

How to use the status-code catalog

Filter by class, search by code or description, click to copy.

01
Filter by class
Pick 1xx through 5xx to narrow to a single semantic class, or stay on all to scroll the full RFC 9110 registry plus common WebDAV (RFC 4918), conditional-request (RFC 9110 § 13), and IETF extension codes.
The five classes map directly to response-handler logic: 1xx informational, 2xx success, 3xx redirection, 4xx client error, 5xx server error. A coloured left rule on each row mirrors the class.
RFC 91101xx2xx3xx · 4xx · 5xxWebDAV
filter · class4xx · client error
```
400 401 403 404 405 …
```
≈25 codes · narrowedRFC 9110 § 15
02
Search by code or text
Type a numeric code like 404, an English term from the canonical reason phrase, or any word from the description — gateway, conflict, teapot all jump straight to the matching rows.
The filter runs against code, reason phrase, and description in parallel, so a query like retry surfaces every retryable code at once for designing backoff policies.
full-text searchreason phraseretryablebackofflive
query · gateway2 hits · 5xx
```
502 Bad Gateway
504 Gateway Timeout
```
matched · 2 of 70+RFC 9110 · live
03
Inspect details
Each row shows the canonical reason phrase, a plain-English description, the defining RFC reference (e.g. RFC 9110, RFC 6585, RFC 4918), and a retryable flag for idempotent requests.
The retryable flag follows convention: 408, 425, 500, 502, 503, and 504 are safe to retry with exponential backoff. 4xx codes other than these typically need a request change, not a retry.
RFC 9110RFC 6585RFC 4918retryableidempotent
row · 503 detailRFC 9110 · retryable
```
503 Service Unavailable
retryable · RFC 9110
```
1 row · 5xx classsafe to retry
04
Copy one or all
Click any row to copy code reason (for example 404 Not Found) into your clipboard, or hit Copy all to grab the full catalog as plain text for offline use, docs, or a constants file.
The catalog is static data shipped with the page — the filter, sort, and clipboard write all run client-side. See the HTTP Methods tool for the verb-side reference.
clipboardbulk exportconstantsdocsprivacy-first
export · clipboard1 row · 404
```
Copied 404 Not Found
```
ready to ship0 outbound

Pro tips

Web-spec details that bite later

Idempotency saves retries

POST/PUT/DELETE should be safely retried. Use idempotency keys and return the same response on duplicate requests.

Match RFC 9110 status codes

Don’t invent codes. 422 for validation errors, 409 for conflicts, 429 for rate limits. Standard codes work with off-the-shelf clients.

Set <code>Cache-Control</code> deliberately

Default browser caching is conservative. Use max-age + stale-while-revalidate for hot endpoints.

Validate Open Graph in dev

OG tags break silently. Use a previewer like OG Generator + Facebook’s debugger before launch.

CORS is a server concern

The browser sends the preflight; the server decides. Wildcard origins disable credentials — be explicit.

MIME drives behaviour

Servers must send the right Content-Type. Browsers sniff but the spec says they shouldn’t — be explicit to avoid surprises.

Use Cases

When to reach for the status catalog

Debug APIs, write docs, design retry logic.

API debugging

Look up the meaning of an unexpected response code. Bundled from IANA registries at build time — no live network call, no rate limit, no leaked queries. The MIME, TLD, and status-code tables are baked in so the tool works offline once loaded.

spec-compliant

Retry policies

Decide which codes are safe to retry automatically. Output is canonical per the relevant RFC (9110 for HTTP, 5322 for headers, 3986 for URLs), so spec-compliant parsers accept it as-is. Cross-browser and cross-library behaviour stays consistent.

offline

Docs / spec writing

Cite the right code for each error path. Pairs with the curl-to-fetch converter for end-to-end test stubs — copy the curl from DevTools, paste, get an idiomatic fetch() body. Drop into Playwright/Vitest fixtures without manual translation.

IANA-backed

Client error UX

Map status to user-facing copy. Catches common pitfalls (uppercase header names, smart quotes inside Content-Type, missing ;charset=utf-8) before they bite production. Validation flags rather than auto-corrects so you stay in control.

RFC-aligned

Onboarding

Quick reference for new engineers. Validation runs as you type — copy only when the output is shaped correctly. The output drops directly into nginx, Apache, or CDN configs without re-formatting or re-quoting.

production-grade

Integration tests

Assert against the right code, not just OK. Same input plus same options always produces identical canonical output, so the tool is safe to embed in CI scripts that diff against expected configs.

curl-ready

FAQ

Frequently asked questions

What does HTTP 200 mean?

200 OK — the request succeeded and the response body is the requested representation.

What does HTTP 404 mean?

404 Not Found — the server has no resource at that URL right now. The URL may exist later.

What does HTTP 500 mean?

500 Internal Server Error — the server hit an unexpected condition. Usually safe to retry once with backoff.

Which codes are safe to retry?

Idempotent methods returning 408, 425, 500, 502, 503, or 504 are usually safe. The catalog flags each retryable code.

Is anything sent to a server?

No — the entire catalog is static data and the filter runs locally in your browser.

Suggest a tool

Something missing?

Tell us what you need. We ship the top requests every two weeks.

47 in queue·8 shipped this month

Request queued. Thanks!