Developer utilities
HTTP status codes.
Every registered HTTP status code in one searchable table: what it means, whether a cache may reuse it by default, how clients should retry or follow it, and the usual fix. Search by number, class such as 5xx, or a word such as redirect.
Find a code
Codes
Loading the registry data…
Sources and limitations
Registered codes, names and defining references are copied from the IANA HTTP Status Code Registry, fetched 2026-09-30. “Cacheable by default” follows RFC 9110 section 15.1 (200, 203, 204, 206, 300, 301, 308, 404, 405, 410, 414 and 501 are heuristically cacheable), plus RFC 7725 for 451 and RFC 6585 for 428, 429, 431 and 511. Explicit Cache-Control headers can change any of this.
The meaning and retry wording is a plain-English summary of those documents, and the typical fix is practical guidance, not part of any standard. Unassigned ranges (such as 105-199, 209-225, 427, 430 and 509) are not listed. Code 104 is a temporary registration that expires 2026-11-13 unless extended; 306 and 418 are marked Unused and 510 is obsoleted. The registry changes over time, so check IANA for the latest. Nothing is sent from your browser.