Skip to content
epitometool

HTTP status code reference

Reference & converters

Search common HTTP response codes with class and meaning.

Updated

Search status codes

Matches (20)

CodeTitleGroupDescription
100Continue1xxRequest headers received; continue request body.
200OK2xxRequest succeeded.
201Created2xxResource created successfully.
204No Content2xxRequest succeeded with no response body.
301Moved Permanently3xxResource permanently moved to new URL.
302Found3xxTemporary redirect.
304Not Modified3xxCached resource still valid.
400Bad Request4xxMalformed request syntax.
401Unauthorized4xxAuthentication required.
403Forbidden4xxServer understood request but refuses it.
404Not Found4xxResource not found.
405Method Not Allowed4xxHTTP method not allowed for resource.
409Conflict4xxRequest conflicts with current state.
410Gone4xxResource permanently removed.
422Unprocessable Content4xxSemantically invalid request payload.
429Too Many Requests4xxRate limit exceeded.
500Internal Server Error5xxGeneric server-side failure.
502Bad Gateway5xxInvalid upstream response.
503Service Unavailable5xxServer temporarily unavailable.
504Gateway Timeout5xxUpstream response timeout.

Quick start

How to use HTTP status reference

Search status codes by number, title or error type.

  1. Step 1
    Search code

    Type code like 404 or keyword like timeout.

  2. Step 2
    Read meaning

    Inspect category and practical interpretation.

  3. Step 3
    Apply fix

    Use result while debugging API or backend responses.

In-depth guide

HTTP status code reference

Search common HTTP response codes and understand what each status means in API and web workflows.

Status families

1xx informational, 2xx success, 3xx redirects, 4xx client errors, 5xx server errors.

Debugging tip

Pair status codes with response body and server logs to find root causes faster.

When to use it vs alternatives

Use this tool for quick browser-based work when you need an answer or output immediately. Use a dedicated application or automated workflow when you need bulk processing, approvals, or repeatable production rules.

Step-by-step usage

  1. Search code — Type code like 404 or keyword like timeout.
  2. Read meaning — Inspect category and practical interpretation.
  3. Apply fix — Use result while debugging API or backend responses.

Common pitfalls

  • Check the result before replacing the original input.
  • Watch for unit, format, encoding, and browser memory limits on large inputs.
  • Keep a copy of important source material until the output is verified.

Privacy and security

Browser-first by design. The tool page explains any exception before you use it.

Your input is handled in the browser wherever the tool can process it locally. EpitomeTool does not add an upload step unless a tool page explicitly says so.

Frequently asked questions

Does this include all HTTP status codes?

This release includes the most commonly used response codes across 1xx-5xx.

Can I search by keyword?

Yes. Search matches code, title, group and description text.

Is this meant for debugging APIs?

Yes, it is optimized for quick API and backend debugging lookup.

Keep exploring

More tools you'll like

Hand-picked utilities that pair well with the one you're on — all free, client-side, and zero-signup.

More reference & converters

See all →

Popular across EpitomeTool

Browse all →
Browse all 200+ free tools