Skip to content
OneKitly

HTTP Status Code Reference

Search and browse every standard HTTP status code by class, with its name and a one-line description.

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

  1. Open the tool — no signup or install needed.
  2. Enter your input or adjust the available options.
  3. 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.

Further reading

All guides →
GuideHTTP Status Codes Explained: The Ones That Actually Get Confused301 against 308, 302 against 307, 401 against 403, 404 against 410 — plus what Retry-After on a 429 or a 503 actually promises. The pairs where picking the wrong code changes behaviour, not just wording.How-toHow to Write a Cron Expression: Five Fields and the OR Rule Nobody MentionsMinute, hour, day of month, month, day of week. The traps are that a step is a stride through a range and not an interval, and that the two day fields are combined with OR — so 0 0 1 * 1 fires on the 1st and on every Monday.ExplainerWriting a Date as ISO 8601, and Why It Is the Only Unambiguous Format01/02/2026 is 1 February in most of Europe and 2 January in the United States, and nothing in the string says which. ISO 8601 fixes that, sorts as text, and stops being ISO 8601 in four specific places that RFC 3339 rejects.How-toHow Long Does It Take to Upload a File? The Size Times 8 Divided by Speed FormulaEstimate upload time with one formula: file size in bits divided by your upload speed. Learn why upload is usually slower than download and how overhead affects the result.ExplainerWhat Is UTF-8 and Unicode? Code Points, Byte Encoding, and Why UTF-8 WonUnicode assigns every character a code point; UTF-8 encodes those code points in one to four bytes. Here is how it works and why it beat the alternatives.ExplainercamelCase vs snake_case: A Guide to Naming Conventions in CodecamelCase, snake_case, PascalCase, and kebab-case explained: what each looks like, where it is the convention, and how to choose one consistently.