HTTP Status Codes Reference

Look up 1xx-5xx HTTP status codes per RFC 9110 with caching and retry rules, or extract status counts from access logs locally in your browser.

No uploadsNo sign-upInstant results
60+ RFC 9110 & IANA CodesLog & HAR Status ExtractorStatus Line & JSON Copy
Browse HTTP Status Codes
Offline engine ready100% private in-browser workspace • Zero cloud uploads
100% Private • Zero Server File Uploads

Why Use Utiliome's Free HTTP Status Codes Reference?

Built from the ground up for strict privacy, instant execution, and zero friction. No subscriptions, paywalls, or account registrations required.

IANA & RFC 9110 Registry Coverage

Covers standard 1xx-5xx codes per RFC 9110 alongside WebDAV (RFC 4918), rate-limiting and header extensions (RFC 6585), legal blocks (RFC 7725 451), and common Nginx or Cloudflare proxy codes.

Heuristic Caching & Retry Semantics

Details default shared-cache eligibility, HTTP method and body preservation across 301/302 versus 307/308 redirects, and safe idempotency retry boundaries.

Access-Log Status Extractor

Parses Common Log Format, Combined Log Format, JSON structured access logs, and raw HTTP response lines to tally status code counts and error-class percentages.

100% Client-Side Log Privacy

Processes production Nginx, Envoy, ALB, and Apache log snippets entirely in browser memory so internal IP addresses, request paths, and query tokens never leave your machine.

Utiliome vs Traditional Cloud Alternatives

Compare our local-first WebAssembly engine against legacy cloud tools.

Feature Utiliome (Local Browser) Legacy Cloud Converters
Specification Accuracy Complete IANA & RFC 9110 (1xx–5xx) reference plus NGINX, Cloudflare & AWS codes Outdated RFC 2616 descriptions missing 422, 429, 451, 103, and CDN codes
Access Log Status Extractor Paste NGINX/Apache/HAR logs to tally status code frequencies and error rates Static text glossary with zero log parsing or diagnostic capabilities
Retryability & Cacheability Metadata Explicitly flags idempotency, default heuristic caching, and Retry-After semantics Vague one-line summaries without HTTP caching or retry guidance
Instant Search by Code or Keyword Filter immediately by status number (429), constant name, or symptom (rate limit) Multi-page documentation requiring manual scrolling through 60+ subpages
How it works

How to Use HTTP Status Codes Reference in 3 Easy Steps

No software installation required. Everything runs directly inside your web browser.

1

Search by Code, Phrase, or Class

Filter the reference by numeric status code (such as 429 or 503), reason phrase, or 1xx-5xx response class to inspect its defining RFC specification.

2

Verify Caching, Headers, and Retry Rules

Check required companion headers like Location, Retry-After, or WWW-Authenticate, default heuristic cacheability, and method preservation rules.

3

Paste or Drop Access Logs for Triage

Load an Nginx, Apache, or JSON access log snippet to compute per-code frequencies, class ratios, and top failing status codes locally.

Extracting HTTP Status Distributions from Production Access Logs

Quick Answer: Paste Combined Log Format or JSON access log lines into the extractor to parse three-digit status tokens, aggregate counts by individual code and 1xx-5xx class, and separate 4xx client rejections from 5xx upstream failures.

During incident triage, scanning raw reverse-proxy logs by eye makes it difficult to distinguish a spike in client rate-limiting (429) or premature client disconnects (499) from genuine upstream crashes (502 and 504). The built-in log extractor scans pasted lines or dropped .log files locally in your browser, isolates the HTTP response status token following the quoted request line or JSON status key, and computes an exact frequency breakdown.

Consider a mixed Nginx Combined Log Format sample from an API gateway experiencing latency spikes:

198.51.100.42 - - [01/Nov/2026:14:22:01 +0000] "GET /v2/orders?limit=50 HTTP/2.0" 200 4812 "-" "curl/8.7.1"
198.51.100.42 - - [01/Nov/2026:14:22:02 +0000] "POST /v2/orders HTTP/2.0" 308 0 "-" "curl/8.7.1"
203.0.113.19 - - [01/Nov/2026:14:22:03 +0000] "POST /v2/orders/ HTTP/2.0" 429 118 "-" "python-httpx/0.27.0"
192.0.2.88 - - [01/Nov/2026:14:22:05 +0000] "GET /v2/reports/export HTTP/2.0" 499 0 "-" "Mozilla/5.0"
192.0.2.88 - - [01/Nov/2026:14:22:09 +0000] "GET /v2/reports/export HTTP/2.0" 504 569 "-" "Mozilla/5.0"
203.0.113.55 - - [01/Nov/2026:14:22:10 +0000] "GET /v2/inventory HTTP/2.0" 200 1940 "-" "Go-http-client/2.0"

The extractor aggregates both individual codes and RFC 9110 response classes so you can immediately evaluate SLI error budgets:

{
  "totalResponses": 6,
  "byClass": {
    "2xx": { "count": 2, "share": "33.33%" },
    "3xx": { "count": 1, "share": "16.67%" },
    "4xx": { "count": 2, "share": "33.33%" },
    "5xx": { "count": 1, "share": "16.67%" }
  },
  "byCode": [
    { "code": 200, "phrase": "OK", "count": 2, "standard": "RFC 9110" },
    { "code": 308, "phrase": "Permanent Redirect", "count": 1, "standard": "RFC 9110" },
    { "code": 429, "phrase": "Too Many Requests", "count": 1, "standard": "RFC 6585" },
    { "code": 499, "phrase": "Client Closed Request", "count": 1, "standard": "Nginx Extension" },
    { "code": 504, "phrase": "Gateway Timeout", "count": 1, "standard": "RFC 9110" }
  ]
}

Pairing 499 and 504 on /v2/reports/export immediately reveals the failure pattern: impatient clients abort the connection before the upstream worker responds (499), and connections kept open past proxy_read_timeout terminate with 504 Gateway Timeout.

RFC 9110 Status Semantics: Redirect Method Preservation, Heuristic Caching, and Vendor Extensions

Quick Answer: RFC 9110 obsoletes RFC 7231 and defines how HTTP clients and intermediaries classify three-digit status codes by their leading digit, enforce method preservation across 3xx redirects, apply heuristic caching defaults, and handle non-standard proxy extensions.

Every HTTP status code is a three-digit integer where the first digit defines the response class (1xx through 5xx). Under RFC 9110 Section 15, an HTTP client that encounters an unrecognized code such as a custom 599 MUST treat it as equivalent to the generic x00 code of that class (500 Internal Server Error). Furthermore, while HTTP/1.1 transmits a human-readable <reason-phrase> after the numeric <status-code> (for example, HTTP/1.1 200 OK), HTTP/2 (RFC 9113) and HTTP/3 (RFC 9114) strip reason phrases from the wire entirely, serializing only the three-digit :status pseudo-header field.

Redirect Method and Payload Preservation (301/302 vs. 307/308)

A frequent source of broken webhook and REST API integrations is redirect method rewriting:

  • 301 Moved Permanently and 302 Found: For historical browser compatibility with HTML form submissions, RFC 9110 permits user agents to rewrite a POST request into a GET request and discard the request body when following the Location header.
  • 303 See Other: Explicitly instructs the client to retrieve the Location URI using GET, implementing the Post/Redirect/Get pattern cleanly.
  • 307 Temporary Redirect and 308 Permanent Redirect: Strictly prohibit changing the HTTP method or body when reissuing the redirected request. APIs redirecting trailing slashes on POST, PUT, or DELETE endpoints must emit 307 or 308.

Heuristic Cacheability Defaults

Per RFC 9110 and RFC 9111 (HTTP Caching), responses carrying status codes 200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414, and 501 are heuristically cacheable by shared CDN and proxy caches unless explicitly restricted by Cache-Control directives or request authentication rules. Emitting an uncached 404 Not Found or 301 Moved Permanently without an explicit Cache-Control: no-store or max-age header can cause CDNs or browsers to cache transient routing mistakes.

Auxiliary RFCs and Reverse-Proxy Extensions

Production traffic spans specifications beyond core RFC 9110:

  • Core Promotions: 422 Unprocessable Content (formerly "Unprocessable Entity" in WebDAV RFC 4918) and 418 I'm a teapot (reserved as an unused sentinel) now reside directly in RFC 9110.
  • Operational Extensions: RFC 6585 defines 428 Precondition Required, 429 Too Many Requests (paired with Retry-After), 431 Request Header Fields Too Large, and 511 Network Authentication Required. RFC 7725 defines 451 Unavailable For Legal Reasons (paired with a Link header carrying rel="blocked-by"). RFC 8297 defines 103 Early Hints for preloading assets before the final 200 response.
  • Non-Standard Proxy Codes: Reverse proxies emit local diagnostic codes that never cross standard IANA registries, notably Nginx 444 (connection closed without response) and 499 (client closed connection while upstream was processing), plus Cloudflare 520 through 526 indicating origin TCP resets, timeouts, or TLS certificate handshake failures.

HTTP Status Codes Reference vs MIME Type Lookup vs URL Parser: Which One Do You Need?

Quick Answer: Use HTTP Status Codes Reference to decode 1xx-5xx response semantics and audit access-log error rates, MIME Type Lookup to verify Content-Type headers and file magic bytes, and URL Parser to inspect RFC 3986 URI components and query parameters.

Debugging HTTP transactions often spans three distinct protocol surfaces: the response status line, the payload media type headers, and the target URI structure.

Capability HTTP Status Codes Reference MIME Type Lookup URL Parser
HTTP Protocol Layer Response status line (:status 1xx–5xx) Payload representation (Content-Type & Accept) Request target & Location redirect URIs
Governing Specifications RFC 9110, RFC 6585, RFC 7725, RFC 8297 RFC 6838, RFC 2046, RFC 9239, WHATWG Sniffing RFC 3986, WHATWG URL Standard
Local Input Analyzer Access-log status extractor & frequency counter Binary magic-byte vs. file extension inspector Live URI component & query-string tokenizer
Primary Debugging Target Redirect loops, retry logic, 4xx/5xx error spikes nosniff blocks, wrong MIME headers, spoofed uploads Malformed percent-encoding, broken redirect targets

When to Switch Tools

  • Investigating 406 Not Acceptable or 415 Unsupported Media Type: Once you confirm the status semantics here, open MIME Type Lookup to look up the canonical IANA media type (such as application/problem+json or text/javascript) and verify that dropped files match their declared binary magic bytes.
  • Investigating 301/308 Redirect Targets, 400 Bad Request, or 414 URI Too Long: Copy the request URL or Location response header into URL Parser to inspect scheme, host, port, path segments, and percent-encoded query parameters.
FAQ

HTTP Status Codes Reference FAQ and Technical Guide

Everything you need to know about using Utiliome's free online http status codes.

Why did my POST request turn into a GET request after a 301 or 302 redirect?

RFC 9110 permits user agents to rewrite POST requests to GET and drop the request payload on 301 Moved Permanently and 302 Found responses to match legacy web browser behavior. To preserve the original HTTP method and request body across a redirect, configure your server or ingress controller to return 307 Temporary Redirect or 308 Permanent Redirect.

What is the exact difference between 401 Unauthorized and 403 Forbidden in RFC 9110?

Despite its historical name, 401 Unauthorized indicates missing or invalid authentication credentials and MUST include a WWW-Authenticate response header challenging the client. By contrast, 403 Forbidden means the server understood the request and authenticated the caller (or requires no credentials) but refuses authorization; re-authenticating will not change the outcome. Servers wishing to hide the existence of restricted resources from unauthorized callers may return 404 Not Found instead of 403.

Should a REST or JSON API return 400 Bad Request or 422 Unprocessable Content for validation errors?

Return 400 Bad Request when the request cannot be parsed due to malformed JSON syntax, invalid framing, or corrupt headers. Return 422 Unprocessable Content (promoted from WebDAV into core RFC 9110 Section 15.5.21) when the payload content type is supported and the JSON syntax is valid, but semantic domain rules fail—such as a negative quantity field or an end date preceding a start date.

How do 502 Bad Gateway, 503 Service Unavailable, and 504 Gateway Timeout differ during incident triage?

A 502 Bad Gateway means an intermediary proxy or CDN received an invalid response, premature TCP RST, or malformed HTTP frame from an upstream origin. A 503 Service Unavailable means the server or origin pool is temporarily overloaded or in maintenance mode (often accompanied by a Retry-After header). A 504 Gateway Timeout means the proxy waited past its configured upstream read timeout without receiving timely response bytes.

Why are reason phrases like OK or Not Found missing in HTTP/2 and HTTP/3 responses?

HTTP/2 (RFC 9113) and HTTP/3 (RFC 9114) omit human-readable reason phrases entirely on the wire, transmitting only the three-digit ASCII numeric code in the :status pseudo-header field. This reduces header framing overhead and prevents clients from writing brittle string-matching logic against non-normative text.