HTTP Status Code Reference
Look up the meaning and category of common HTTP response codes. Your work stays on this device whenever possible.
How to use HTTP Status Code Reference
- Type a code or keyword into "Search HTTP status codes (e.g. 404, forbidden, cache)"; matching cards appear as you type.
- Narrow the list with "Filter by Category": 1xx Informational, 2xx Success, 3xx Redirection, 4xx Client Error or 5xx Server Error.
- Or click a Quick Jump pill such as 204, 304, 429 or 503, which fills the search box and resets the category to all.
- Read each card: the coloured code badge, the cacheability note, the meaning, "Common Causes" and "How to Fix / Handle".
- Open "View code snippets (Fetch / cURL)" and press "Copy Fetch" or "Copy cURL" to take a test request with you.
Worked example
Type 304 in the search box. One card remains: a 3xx badge with "Not Modified", the note "Cacheable by default", and the meaning that the client's cached copy is still fresh. Its cause mentions a conditional request that matched If-None-Match or If-Modified-Since, and the fix says to load the resource from cache. Opening the snippets shows a Fetch example checking for status 304.
When to use this tool
- Deciding between 401 and 403 while designing an API's error responses.
- Recalling what a 429 expects a client to do, such as reading Retry-After.
- Copying a status-checking Fetch snippet into a quick test script.
Important limitations
Covers all standard RFC 9110 and IANA registered HTTP response codes. Individual web frameworks, reverse proxies, and CDN edge servers may implement custom status descriptions or proprietary codes.
Frequently asked questions
Does it cover every registered status code?
No. It holds 33 commonly met codes, from 100 Continue to 504 Gateway Timeout. Entries such as 303 See Other, 412 Precondition Failed, 416, 431, 451 and 505 are absent, so check the RFC when you need an unusual one.
Which fields does the search look at?
The number, the reason phrase, the meaning text and the causes text. The cacheability label and the fix text are not searched, so typing cache finds only cards whose meaning happens to mention caching.
How should I read the cacheability label?
It is a short default hint, for example "Not cacheable" or "Cacheable by default". Real caching is governed by Cache-Control and related headers, so the label describes the starting point rather than a guarantee.
What do the code snippets actually call?
The cURL line requests a public testing host's /status path for the chosen code, and the Fetch snippet targets a placeholder api.example.com address you must replace. Nothing runs from this page; the snippets are just text to copy.
How do 401 and 403 differ?
In HTTP semantics, 401 means authentication is missing or failed, while 403 means the server knows who you are and still refuses. Their cards list matching causes, such as an expired token for 401 and a permission gap for 403.