How to use HTTP Status Codes

What it does

Search and read server response headers, specs, and status definitions from 100 to 599. It runs entirely in your browser — your input never leaves your device.

Options

Every setting this tool exposes, straight from the code that validates it.

Worked example

Run these settings on the tool page:

No settings needed — paste your input and go.

You get:

{
  "count": 24,
  "results": [
    {
      "code": 100,
      "title": "Continue",
      "category": "1xx Informational",
      "desc": "The server has received the request headers and the client should proceed to send the request body."
    },
    {
      "code": 101,
      "title": "Switching Protocols",
      "category": "1xx Informational",
      "desc": "The requester has asked the server to switch protocols and the server has agreed to do so."
    },
    {
      "code": 200,
      "title": "OK",
      "category": "2xx Success",
      "desc": "Standard response for successful HTTP reques
… (truncated)

Getting the result you want

Most of the control here is in the options above. If the output is not what you expected, the setting to check first is code and query — those change the shape of the output rather than the input it accepts.

Troubleshooting

• It is slow on very large input. Everything runs in your browser, so speed depends on your device. Very large inputs are best split up, or run through the API where the work happens on our servers.

Automating it

The same logic is available as a REST endpoint, so you can run it from a script, a CI job or your own app.

Bash
curl "https://api.toolsxpo.com/v1/http-status-codes" \
  -H "Authorization: Bearer $TOOLSXPO_KEY"

It costs 1 credit per successful call. See the full endpoint reference, or try it in the playground.

Related tools

• Curl to Fetch Converter
• Fetch to Curl Converter
• HTTP Headers Viewer
• MIME Types Lookup
• Open Graph Inspector
• Punycode Decoder