All tools

HTTP Status Codes

Network

Reference guide for all HTTP status codes with search and category filter

Search by code number, like 429, and get its meaning and typical use back instantly, or filter by category (2xx, 4xx, 5xx) to browse related codes while deciding which one actually fits a response you're designing. It covers the official IANA-registered codes plus a handful of widely used unofficial ones like 418, clearly marked as non-standard so you don't mistake them for spec. Beyond definitions it includes the judgment calls that trip people up in practice: 401 signals missing or invalid credentials and implies the client should try authenticating, while 403 means the credentials are fine but access still isn't allowed, so retrying auth won't help; for validation errors, 422 is the more semantically correct choice over 400, though plenty of APIs use them interchangeably. It's a static reference: searching and filtering all happen client-side with nothing sent anywhere.

httpstatuscodesreference

How to use HTTP Status Codes

  • 1.Search by status code number (e.g. "429") to instantly see its meaning and typical use case.
  • 2.Filter by category (2xx success, 4xx client error, 5xx server error) to browse related codes when deciding which one fits your API response.
  • 3.Look up an unfamiliar code you encountered in a log or API response to understand what it signals before writing error-handling logic.

Frequently asked questions

Is this list official or does it include unofficial codes?
It covers the official IANA-registered HTTP status codes, plus a few widely used unofficial ones (like 418 or 599) clearly noted as non-standard.
Is any of my data sent anywhere?
No, this is a static reference — searching and filtering happen entirely in your browser.
Should I use 401 or 403 for an unauthenticated request?
401 means the request lacks valid authentication credentials, while 403 means the credentials are valid but the user doesn't have permission — use 401 when the client should try authenticating, 403 when authentication won't help.
What's the right code for a validation error?
422 Unprocessable Entity is the most semantically correct choice for valid syntax but invalid data (e.g. a missing required field), though many APIs use 400 Bad Request interchangeably.

Use via API, SDK, or MCP

cURLcurl "https://api.utilix.tech/v1/tools/http-status" \
  -H "Authorization: Bearer utx_live_..."
# Free: 1,000 req/day · Pro: 10,000 req/day

Get an API key from your dashboard · Full API docs →

Related tools

HTTP Headers ReferenceSearchable reference for 80+ HTTP request and response headersNetworkCache-Control Header BuilderBuild and explain an HTTP Cache-Control response header from directives like max-age, s-maxage, no-store, and immutableNetworkCORS Header BuilderGenerate CORS headers with nginx, Express, and Apache config snippetsNetwork