HTTP Code: 404 (Not Found)

HTTP Status Code Reference

Status Category

4xx — Client Error

Meaning & Definition

The origin server did not find a current representation for the target resource or is not willing to disclose that one exists.

Common Causes

Wrong URL paths typed
Deleted pages or assets files
Wrong server routing rewrite configurations

How to resolve HTTP code errors

1. Inspect Logs: Check server logs (e.g. error.log) to locate runtime exceptions or database disconnects.

2. Test Endpoint: Use our Uptime Checker or redirects prober to verify response headers and payload size.

3. Configure Rules: Implement custom redirect rules or error fallback paths below in Nginx/Apache config.

Nginx Configuration Setup

error_page 404 /404.html;
location = /404.html {
  root /usr/share/nginx/html;
  internal;
}

Apache Configuration Setup

ErrorDocument 404 /404.html

Standard HTTP Status Codes

HTTP 100 HTTP 200 HTTP 201 HTTP 204 HTTP 301 HTTP 302 HTTP 304 HTTP 400 HTTP 401 HTTP 403 HTTP 404 HTTP 429 HTTP 500 HTTP 502 HTTP 503 HTTP 504

HTTP Diagnostic Tools

Website Uptime Checker — Monitor HTTP response codes in real-time HTTP Headers Inspector — Examine server response headers and status codes SSL Certificate Checker — Verify HTTPS configuration and redirects IT Expert AI — Ask about server configuration and HTTP issues

Authoritative Standards

IETF RFC 9110 — HTTP Semantics (June 2022, current standard)MDN Web Docs — HTTP Response Status Codes Reference IANA HTTP Status Code Registry

HTTP status codes standardized in RFC 9110. IANA maintains the official registry of all assigned codes.