HTTP Status Codes
Every status code explained — search 200 to 511 in seconds
Continue with the request.
Switching protocols.
Early hints before the final response.
OK, request succeeded.
Created successfully.
Accepted for later processing.
Success, but modified by a proxy.
Success, no content to return.
Success, reset the form.
Returning the requested file range.
Multiple statuses at once (WebDAV).
Already reported, no duplicate.
Using the instance manipulation result.
Multiple choices — pick one.
Moved permanently, update bookmarks.
Moved temporarily, usually followed.
Fetch again with GET at the new address.
Not modified, cache is fine.
Temporary move, method and body must not change.
Permanent move, method and body must not change.
The request is malformed.
Log in or authenticate first.
Payment required (reserved).
Understood, but access forbidden.
Nothing lives at this address.
Method not allowed here.
No acceptable format available.
Proxy login comes first.
Client gave up waiting.
Conflicts with the current state.
Existed once, deleted forever.
Content-Length missing.
A precondition failed.
Body too large, rejected.
URL too long.
This media type is not supported.
Requested range unavailable.
I am a teapot (April Fools' joke, kept with honors).
Request sent to the wrong server.
Well-formed but semantically wrong.
Resource is locked.
A dependency failed first.
Too early, server refuses (replay protection).
Upgrade protocols first.
A required conditional header is missing.
Too many requests — rate limited, take a break.
Request headers too large.
Unavailable for legal reasons.
The server blew up internally.
Not implemented here.
The gateway's upstream is broken.
Temporarily unavailable (overload or maintenance).
Gateway timed out waiting upstream.
HTTP version not supported.
Negotiation looped back.
Server storage is full.
Circular reference detected.
Extension declaration missing.
Authenticate through the captive portal first.
Status codes are a conversation
Every HTTP response carries a three-digit status: the server telling the client what happened in one number. 200s mean it worked, 300s mean look over there, 400s mean your request was wrong, 500s mean the server broke. Reading them fluently turns cryptic failures into five-second diagnoses.
What this tool does
- 🚦 All common codes 100–511 with plain-language meanings
- 🔍 Instant search by number or phrase, plus class filters
- 🔗 Deep links (?code=404) you can share
- 🍵 The 418 teapot, preserved with honors
When to use it
- Decoding a failed fetch in devtools
- Choosing the right redirect for an SEO migration
- Settling what 422 vs 400 means in your API
Privacy: a static reference page — nothing to compute, nothing to upload.
Last updated · 2026-09-01
How the reference works
A static table of codes, phrases and classes renders server-side for instant load and indexing; the search filter runs locally in a few lines of script. No network, no database, nothing to break.
Why look codes up here?
Searchable, not scrollable
Type 404 or timeout and land directly on the card — plus one-click class filters and shareable ?code= links for pairing sessions and code reviews.
Advice, not just definitions
Each card says when servers actually send the code and what to do about it, instead of quoting the RFC and leaving you hanging.
Complete and current
From 103 Early Hints to 451 Unavailable For Legal Reasons, including the modern 425 Too Early — the set your framework actually emits.
Frequently asked questions
What do the number ranges mean?⌄
1xx is informational, 2xx means success, 3xx redirects elsewhere, 4xx blames the client request, 5xx blames the server. The first digit tells you who should act.
301 vs 302 vs 307 vs 308 — which redirect?⌄
301/308 are permanent (browsers and SEO pass it on), 302/307 temporary. 301/302 historically allowed method changes; 307/308 strictly preserve the method — use 308 for permanent API moves.
Is 418 a joke?⌄
Half: an April Fools RFC that stuck around as the community mascot (I'm a teapot). Some APIs and test suites genuinely return it — and now you know why.
Frequently asked questions
What do the number ranges mean?
1xx is informational, 2xx means success, 3xx redirects elsewhere, 4xx blames the client request, 5xx blames the server. The first digit tells you who should act.
301 vs 302 vs 307 vs 308 — which redirect?
301/308 are permanent (browsers and SEO pass it on), 302/307 temporary. 301/302 historically allowed method changes; 307/308 strictly preserve the method — use 308 for permanent API moves.
Is 418 a joke?
Half: an April Fools RFC that stuck around as the community mascot (I'm a teapot). Some APIs and test suites genuinely return it — and now you know why.