HTTP Status Codes screenshot

HTTP Status Codes

Every common HTTP status code with its name and meaning, filterable by number or text. A reference table that runs in your browser.

Privacy First
0 Runs
Updated 2026-11-06
Runs in your browser
Works offline after load
No request sent

Every status code, in one table

An HTTP response carries a three-digit status code, and the first digit is the family: 1xx is informational, 2xx succeeded, 3xx points somewhere else, 4xx is the client's problem and 5xx is the server's. This page lists the codes you actually meet, with the registered name and a sentence saying what the code means in practice.

Filtering

One input filters the table as you type. It matches the number, the name and the meaning, so 404 finds Not Found and cache finds the codes that describe cached responses. The row count under the table reports how many entries matched, so an empty result is visible rather than looking like a broken page.

What it is for

It is a reference, not a diagnostic. When an API returns 422 and you cannot remember whether that is a validation failure or an authentication failure, the table answers in one line. The distinction between 301 and 308, or between 401 and 403, is exactly the kind of thing that is easy to half-remember.

What it does not do

It does not send a request, so it cannot tell you what a particular URL answers. Nothing here contacts a server, and no code is looked up from a remote registry: the table is compiled into the page, which is why it works offline after the page loads.

This page is a reference table of the HTTP status codes you actually meet, with the registered name and a sentence saying what the code means in practice. One filter matches the number, the name or the meaning as you type.

It is a lookup, not a diagnostic. It cannot tell you why a particular server answered 502 this morning, because it never sends a request and has no idea what your server is doing.

The table is compiled into the page. Nothing is fetched and no registry is queried, which is why the page works offline after it loads.

The five families, and what each one blames

The first digit is the family. 1xx means the request is still being negotiated, 2xx means it succeeded, 3xx means the client should look somewhere else, 4xx means the request was the problem and 5xx means the server failed to handle a request it accepted.

That distinction is the most useful thing on the page: a 429 is your client being throttled, a 503 is the server being unavailable, and a 401 and a 403 differ in whether authenticating again could possibly help.

  • 1xx: informational, the request continues
  • 2xx: success
  • 3xx: redirection
  • 4xx: the client's request
  • 5xx: the server's failure

Codes that get confused with each other

301 and 308 both move a URL permanently, but 308 requires the method and body to be preserved. 302 and 307 are the temporary pair with the same difference, which is why a POST that must stay a POST needs the newer code.

401 and 403 look alike and are not: 401 says authentication is missing or was not accepted, 403 says the server knows who you are and still refuses. Sending credentials again fixes the first and never fixes the second.

204 and 304 both carry no body, for different reasons: one says the request did what it should and there is nothing to return, the other says the copy you already have is still current.

How to use the filter

Type into the Filter by code, name or meaning box and the table narrows as you type across the five families: 1xx still negotiating, 2xx succeeded, 3xx look elsewhere, 4xx the request was the problem, 5xx the server failed. The registered name and a practice sentence come with each code, with the count of matching status codes beside them.

A 429 is your client throttled and a 503 the server unavailable; 401 means authentication may help and 403 means it will not; 204 and 304 both carry no body for different reasons. It is a lookup, not a diagnostic: it cannot say why a server answered 502 this morning because it never sends a request.

What to Expect

Best for

  • Looking up what a status code means
  • Telling a client-error code from a server-error code
  • Checking whether two similar codes differ in method handling

Not ideal for

  • Diagnosing a live response
  • Vendor-specific or unofficial status codes
  • Testing what a particular URL returns

What this tool keeps

  • The registered name of each code
  • One sentence of practical meaning per code
  • A filter that matches number, name and meaning

What may need cleanup

  • A code outside the table, which will not be found by the filter
  • A response whose real cause is in the body, not the code
  • Website-specific codes such as 999, which are not standard

Common errors

  • Reading 403 as a login problem
  • Using 302 for a POST that must keep its body
  • Treating 5xx as a client mistake

Example use cases

  • Reading a log line that quotes a code
  • Choosing the right redirect code for a moved page
  • Explaining an API error to a client

Sample input

Type cache into the filter.

Sample output

The codes whose name or meaning mentions caching, with 304 Not Modified among them and the matched count shown under the table.

Who this is for

  • Web developers reading a response
  • Support engineers triaging an error report
  • Anyone learning what the numbers mean

Frequently asked questions

What does the HTTP status code table contain?

The codes you actually meet, each with its registered name and a sentence of practical meaning, searchable by number, name or meaning.

Can it diagnose why a particular response was sent?

No. It explains what a code means in general; the cause of a specific response lives in that server's logs and body.

Why is a vendor-specific code missing?

The table carries registered codes only, so a non-standard value such as 999 is not found.

Developer program

Build custom tools for your store

Join the SDK program to create useful ecommerce utilities for your store.