BRYME Tools · runs entirely in your browser
HTTP status code lookup
The HTTP status codes that actually matter, grouped by class, with plain-language meanings. Type to filter.
| Code | Name | What it means in practice |
|---|---|---|
| 100 | Continue | The client can go ahead and send the request body. |
| 101 | Switching Protocols | Agreed to switch — this is how a WebSocket connection upgrades. |
| 103 | Early Hints | Preliminary headers before the real response; a performance trick. |
| 200 | OK | Worked. The body holds what you asked for. |
| 201 | Created | Success that made something new — the classic POST response. |
| 202 | Accepted | Received and queued, not finished yet. |
| 204 | No Content | Success with an empty body — common after DELETE or a save. |
| 206 | Partial Content | A range was served — video scrubbing and resumable downloads. |
| 301 | Moved Permanently | The address changed for good; update links — search engines transfer rankings. |
| 302 | Found | A temporary redirect; the original URL remains the real one. |
| 304 | Not Modified | The cached copy is still fresh — the quiet workhorse of fast browsing. |
| 307 | Temporary Redirect | Temporary, but the HTTP method must not change. |
| 308 | Permanent Redirect | Permanent, but the HTTP method must not change. |
| 400 | Bad Request | The request itself is malformed; the server refuses to parse it. |
| 401 | Unauthorized | "Who are you?" — credentials missing or failed. Log in properly and retry. |
| 403 | Forbidden | "I know who you are — still no." A permissions problem, not a login one. |
| 404 | Not Found | No resource at this URL. The most famous error on the web. |
| 405 | Method Not Allowed | A GET where only POST is accepted, and similar mismatches. |
| 409 | Conflict | The request fights the resource's current state — often a duplicate. |
| 410 | Gone | Removed on purpose, permanently. Tell search engines it's final. |
| 413 | Content Too Large | The request body exceeds the server's limit. |
| 414 | URI Too Long | The URL exceeds limits — usually a query string gone rogue. |
| 415 | Unsupported Media Type | Wrong payload format for this endpoint (check Content-Type). |
| 429 | Too Many Requests | Rate limit hit — slow down; the response often says when to retry. |
| 431 | Request Header Fields Too Large | Headers too big — an oversized cookie is the usual suspect. |
| 451 | Unavailable For Legal Reasons | Blocked by a legal demand rather than a technical one. |
| 500 | Internal Server Error | The server's own code crashed. The cause lives in its logs. |
| 501 | Not Implemented | The server doesn't support this action at all. |
| 502 | Bad Gateway | A middleman server got garbage from the server behind it. |
| 503 | Service Unavailable | Overloaded or down for maintenance — often temporary. |
| 504 | Gateway Timeout | The server behind the middleman took too long to answer. |
| 511 | Network Authentication Required | The Wi-Fi wants a login page first — a captive portal. |
What this does
A filterable table of the HTTP response codes you meet in real work, grouped by class: 1xx informational, 2xx success, 3xx redirects, 4xx the client's problem, 5xx the server's problem. Type a code (404) or a word (timeout) and the table narrows as you type.
Notes
The descriptions are deliberately plain rather than quotable-spec: what the code means in practice and what usually caused it. The formal definitions live in the IANA registry linked from the full guide to HTTP status codes. This table is static and complete in the page — it works with JavaScript disabled too (the typing filter is the only dynamic part).