Skip to content
WebStatus.inWebStatus.in
DEVELOPER UTILITY

HTTP Status Code Reference

Look up what 301, 401, 429, and 503 mean while you read logs or OpenAPI specs.

Loading tool…

Why keep a reference handy?

Clients, CDNs, and APIs surface status codes constantly. A quick phrase + description helps distinguish retryable errors from auth or routing mistakes.

Privacy

Editing and conversion run in your browser for these workflows—nothing is uploaded to our servers for the core tool actions. Clear sensitive data on shared machines when you are done.

Frequently asked questions

WebStatus.in

© 2026 WebStatus.in — Developer Toolkit

Privacy Policy
Terms of Use
About Us
HTTP status codes
  • 100ContinueClient should continue with request body.
  • 101Switching ProtocolsServer agrees to protocol upgrade (e.g. WebSocket).
  • 102ProcessingRequest received; still processing (WebDAV).
  • 200OKRequest succeeded.
  • 201CreatedResource created; often returns Location.
  • 202AcceptedAccepted for processing; not yet complete.
  • 204No ContentSuccess with empty body.
  • 206Partial ContentRange request fulfilled.
  • 301Moved PermanentlyResource has a new permanent URI.
  • 302FoundTemporary redirect (historically “moved temporarily”).
  • 303See OtherGET the URI in Location.
  • 304Not ModifiedCached copy still valid (conditional GET).
  • 307Temporary RedirectRepeat request to URI in Location (method preserved).
  • 308Permanent RedirectPermanent redirect; method preserved.
  • 400Bad RequestMalformed syntax or invalid framing.
  • 401UnauthorizedAuthentication required or failed.
  • 402Payment RequiredReserved for future use.
  • 403ForbiddenAuthenticated but not allowed.
  • 404Not FoundNo matching resource for URI.
  • 405Method Not AllowedHTTP method not supported for resource.
  • 406Not AcceptableCannot satisfy Accept headers.
  • 408Request TimeoutServer gave up waiting for request.
  • 409ConflictConflict with current resource state.
  • 410GoneResource permanently removed.
  • 413Payload Too LargeRequest body exceeds limit.
  • 414URI Too LongRequest-URI too long.
  • 415Unsupported Media TypeContent-Type not supported.
  • 418I'm a teapotRFC 2324 / RFC 7168 Easter egg.
  • 422Unprocessable EntitySemantic errors (often validation) in Web APIs.
  • 425Too EarlyReplay risk with early data.
  • 426Upgrade RequiredSwitch protocol (e.g. TLS).
  • 428Precondition RequiredConditional headers required.
  • 429Too Many RequestsRate limited.
  • 431Request Header Fields Too LargeHeaders exceed server limit.
  • 451Unavailable For Legal ReasonsBlocked for legal reasons.
  • 500Internal Server ErrorUnexpected server failure.
  • 501Not ImplementedServer does not support capability.
  • 502Bad GatewayInvalid response from upstream.
  • 503Service UnavailableTemporary overload or maintenance.
  • 504Gateway TimeoutUpstream did not respond in time.
  • 505HTTP Version Not SupportedHTTP version not supported.