How to read an HTTP answer
Every answer from a web server starts with a three-digit code. The first digit tells the kind: 2 means success, 3 means go elsewhere, 4 means the request has a problem, 5 means the server has a problem. After the code come headers, small labelled facts about the answer, then the page or data.
What is on this site
- A page for each of 37 common status codes with a real recorded response, the meaning, fixes for site owners and visitors, and a mistake to avoid.
- A checker that explains pasted response headers.
- Guides on redirects, caching, cookies, security headers, content types and range requests.
- A copy of the IANA registry of all status codes.
Which codes matter most?
404, 301, 302, 403, 500, 502, 503 and 429 cover most of what site owners meet.
Are the examples real?
Yes. We ran a small server on our own computer and saved its answers.
This is an independent guide. It is not connected with the IETF, IANA, any browser maker or any company named here. Meanings were checked against the RFC texts on 14 November 2026. Responses shown were recorded on 14 November 2026 from a small test server on the author's own computer.