Web / Server

HTTP Status Codes

This tool explains important HTTP status codes, groups them by category and shows typical causes, practical fixes and notes for redirects, error pages, caching and SEO.

Search and understand status codes

Search for a status code such as 404, terms such as redirect, or filter by category. The table shows what the status means, when it usually appears and which actions are useful.

Searches code, name, category, cause, fix and notes.

0 Results
– Selected
– Category

Searchable table

Code Category Meaning Quick fix

Output

The output contains the currently filtered list or the selected status code. You can copy it or download it as a text file.

HTTP status code categories

1xx Informational

The request has been received and processing continues. These codes are rarely seen directly in everyday work.

2xx Success

The request was successful. Common examples are 200 OK, 201 Created and 204 No Content.

3xx Redirection

The client needs to use another URL. Important examples are 301, 302, 307 and 308.

4xx Client error

The request is invalid, not allowed or points to a missing resource.

5xx Server error

The server cannot process the request correctly. The cause is usually in the application, server or infrastructure.

Practical notes

  • 301 and 308 are suitable for permanent redirects.
  • 302 and 307 should be used for temporary redirects.
  • 404 means not found; 410 signals that content was intentionally removed.
  • 500 is a generic server error and should be checked in the error logs.
  • 503 is useful for planned maintenance, ideally with a suitable retry hint.