HTTP Status Code Reference — searchable, with use cases and RFC specs

#javascript #webdev #programming #tools

What I built

Added HTTP Status Code Reference to devnestio — a searchable, browser-only reference for all HTTP 1xx–5xx status codes.

👉 https://http-status-ref.pages.dev

Features

60+ status codes covered across all ranges (1xx through 5xx)
Search by code number, name, keyword, or use case — e.g. search "rate limit" → finds 429, "websocket" → finds 101
Category filters — click 1xx / 2xx / 3xx / 4xx / 5xx to narrow the view, with live counts
Detail panel — click any card for full description, use case, and RFC reference
Copy button on every card — copy the status code or "404 Not Found" string instantly
Zero dependencies, single HTML file, nothing sent to a server

Status codes covered

1xx Informational: 100, 101, 102, 103

2xx Success: 200, 201, 202, 203, 204, 205, 206, 207, 208, 226

3xx Redirection: 300, 301, 302, 303, 304, 307, 308

4xx Client Errors: 400, 401, 403, 404, 405, 406, 407, 408, 409, 410, 411, 412, 413, 414, 415, 416, 417, 418, 421, 422, 423, 424, 425, 426, 428, 429, 431, 451

5xx Server Errors: 500, 501, 502, 503, 504, 505, 506, 507, 508, 510, 511

Why I made this

I kept confusing 401 vs 403, or 307 vs 308, or wondering when to return 202 vs 204. MDN is great but you have to navigate away, and Stack Overflow answers often disagree on use cases.

This is a quick offline-friendly reference — search for "conflict" and 409 appears, search "moved" and 301 shows up with a clear note on when to use 307 or 308 instead.