HTTP Status Code Lookup — All 1xx–5xx Codes Explained | Tinker
← Tinker

HTTP Status Code Categories

RangeCategoryWhat it means
1xxInformationalRequest received; server is continuing the process. Rarely seen by clients.
2xxSuccessThe request was received, understood, and accepted. Your happy path.
3xxRedirectionFurther action is needed to complete the request — usually a redirect to another URL.
4xxClient ErrorThe request contains bad syntax or cannot be fulfilled. The client needs to fix something.
5xxServer ErrorThe server failed to fulfil a valid request. Something went wrong on your side.

Codes every developer should know

CodeNameWhen to use / what it means
200OKStandard success. Return with a response body for GET/POST.
201CreatedA new resource was created (e.g. POST to create a user). Include a Location header.
204No ContentSuccess, but nothing to return — common for DELETE or PUT.
301Moved PermanentlyURL has changed forever. Browsers and crawlers update their records. Use for SEO-friendly redirects.
304Not ModifiedCached version is still valid. Browser uses its cached copy — fast and bandwidth-efficient.
400Bad RequestThe client sent invalid data. Return a clear error message explaining what's wrong.
401UnauthorizedMissing or invalid authentication. The client can try again with credentials.
403ForbiddenAuthenticated but not allowed. Don't reveal whether the resource exists.
404Not FoundResource doesn't exist. Can also be used deliberately to avoid revealing restricted resources.
429Too Many RequestsRate limiting. Include a Retry-After header so clients know when to retry.
500Internal Server ErrorUnhandled exception. Log it, alert on it, and return a generic message to the client.
503Service UnavailableDown for maintenance or overloaded. Use with Retry-After for planned downtime.

© 2026, Tinker - tools · calculators · practice games