HTTP 404 — Not Found
A 4xx client error: the request contains bad syntax or cannot be fulfilled.
Not Found
The server cannot find the requested resource.
What it means
The server cannot find the requested resource. The URL is unrecognized; the server does not reveal whether the resource never existed or is just hidden.
When to use it
The most common error — returned when a URL does not map to any resource.
Other 4xx codes
About HTTP Status Codes
This HTTP status codes directory covers every standard response code from the 1xx informational range through 5xx server errors. Each entry shows the numeric code, its canonical reason phrase and a one-line summary, and the whole list can be searched by number, name or meaning — 301, Unauthorized and timeout all find their targets — or filtered by response class.
Every code opens onto its own dedicated page with a full explainer: what the status actually means, when to use it in your own APIs and applications, whether responses with that code are cacheable by default, and the RFC that defines it. Related codes from the same class are linked at the bottom, so comparing 401 with 403 or 301 with 308 takes one click.
The five classes are the fastest mental model for reading any response: 1xx means the request is continuing, 2xx means success, 3xx means redirection, 4xx means the client made a mistake and 5xx means the server failed. The directory is organized around exactly that structure.
How to use HTTP Status Codes
- Type a code, a reason phrase or a keyword into the search box — for example 404, Not Found or redirect.
- Use the class filter to narrow the list to informational, success, redirection, client-error or server-error codes.
- Open any code’s page to read what it means, when to use it, its default cacheability and the defining RFC.
- Check the related-codes section to compare neighbors from the same class.
- Use the copy button to grab the code for a bug report, test or API spec.