Search every standard HTTP status code — 1xx to 5xx, color-coded, with plain-English explanations.
Every HTTP response begins with a three-digit status code that tells the client how the request went, and the first digit alone carries the headline: 1xx is informational, 2xx means success, 3xx redirects you elsewhere, 4xx says the client got something wrong, and 5xx says the server itself failed. This reference lists all the standard codes — the core set defined in RFC 9110 plus the commonly registered extensions from WebDAV and related specs, about sixty in total — grouped by class and color-coded so the shape of the protocol is visible at a glance.
The official names (reason phrases) such as "Not Found" or "Bad Gateway" are kept in English on purpose: they are universal technical vocabulary that appears verbatim in logs, browser DevTools and API documentation in every language. On top of that, the roughly 25 codes you actually meet in daily work — 200, 301, 404, 429, 500, 503 and friends — carry a short plain-language explanation that expands when you click the row. The list follows current RFC 9110 naming, so 413 appears as "Content Too Large" and 422 as "Unprocessable Content", and yes, 418 "I'm a teapot" is real — an April Fools RFC from 1998 that servers still ship as an easter egg.
Reach for the reference when debugging an API response, deciding which code your own endpoint should return, or reading server logs: the difference between a 301 and a 302 affects how search engines transfer ranking, the difference between 401 and 403 defines your authentication flow, and telling 502 from 504 points you at the right broken layer behind a proxy. The search box filters by number or name as you type, and everything — list, search and descriptions — is embedded in the page and runs 100% in your browser.
A 301 says the resource moved permanently and clients (including search engines) should update their links; a 302 says the move is temporary and the original URL should keep being used. For SEO, a 301 transfers ranking signals to the new URL, a 302 generally does not.
It identifies the class of the response: 1xx informational, 2xx success, 3xx redirection, 4xx client error (the request is at fault), 5xx server error (the server failed to fulfill a valid request).
Return 401 when the client is not authenticated — credentials are missing or invalid, and trying again with valid ones could work. Return 403 when the client is authenticated but simply not allowed to do what it asked.
502 means a gateway or proxy received an invalid response from the server behind it; 503 means the server itself is temporarily unavailable, usually overloaded or in maintenance; 504 means the gateway gave up waiting for the upstream server to respond.
No. The entire list of codes ships embedded in the page and the search filters it locally in JavaScript — nothing you type is transmitted or stored.
Vai.la turns any URL into a short link with click statistics, QR Code and your own biolink.
Vai.la is not responsible for how the tools are used or for decisions made based on their results.