HTTP Status Code Reference
Search and browse every standard HTTP status code by class, with its name and a one-line description.
Related tools
All Web & network tools →HTTP Status Code Reference works straight from this page — free, instant, nothing to install. Its place is under Web & network; ISO 8601 date converter (RFC 2822, HTTP) and ASCII code converter answer the questions closest to this one.
How to use it
- Open the tool — no signup or install needed.
- Enter your input or adjust the available options.
- Get your result instantly, then copy or download it.
Frequently asked questions
What does HTTP Status Code Reference do?
Search and browse every standard HTTP status code by class, with its name and a one-line description.
When would I actually use this?
Getting usable data out of something that was never meant to be parsed: pulling every address out of a pasted thread, turning a column of lines into a JSON array or an SQL IN clause, renaming a hundred identifiers from snake_case to camelCase in one pass.
What is the most common mistake?
Trusting an extraction to be exhaustive. A pattern that catches every address in the sample will still miss the one wrapped across a line break, the one written with a display name, and the one an email client turned into a link — count what came out against what you expected before you use the list.
How is HTTP Status Code Reference different from ISO 8601 date converter (RFC 2822, HTTP)?
They sit next to each other but answer different questions. ISO 8601 date converter (RFC 2822, HTTP): turn any date, time and UTC offset into ISO 8601, RFC 3339, week/ordinal date, RFC 2822, HTTP date and Unix timestamps. Pick whichever matches what you're starting from — both are free.
Is there a tool for the next step?
ASCII code converter is the closest one after this: Convert text to ASCII/Unicode code points and back.
What else is worth having open alongside it?
Morse code translator and Flip Image — they come up in the same task often enough to be worth a second tab.
Where do the figures come from?
Extraction runs on patterns, not on a parser: it recognises the common shapes of an address, a URL or an IP rather than validating them against their specification. That is the right trade for a paste, and the wrong one for input you are about to store.