4xx Client ErrorHTTP Status Code Reference

HTTP Status Code 404Reference for Developers — Meaning, Causes & Fixes

This URL is a documentation page about HTTP status code 404 (Not Found), not an error page generated by DuskTools.

The server cannot find the requested resource. This is the most well-known HTTP error. The URL may be mistyped, the resource may have been deleted, or it may have never existed.

Live URL Status Checker

Enter any URL to see its real HTTP response code

Common Causes

  • Mistyped URL or broken link
  • Resource has been deleted or moved without a redirect
  • API endpoint does not exist or has been deprecated
  • Case-sensitive URL mismatch on the server

How to Fix

  1. 1Double-check the URL for typos
  2. 2Use the site's search or sitemap to find the correct page
  3. 3Set up 301 redirects for moved or renamed resources
  4. 4Return a helpful 404 page with navigation links

Example

HTTP 404 Not Found
GET /blog/nonexistent-post HTTP/1.1
Host: api.example.com

HTTP/1.1 404 Not Found
Content-Type: application/json

{
  \"error\": \"not_found\",
  \"message\": \"No resource exists at this URL\",
  \"status\": 404
}

404 Troubleshooting Playbook

In production, 404 usually means one of four things: a moved URL without a redirect, an incorrect client route, a stale external link, or a case-sensitive path mismatch. Confirm the exact request path first, then trace rewrite/redirect rules in your edge, proxy, and app router.

For SEO-sensitive pages, replace legacy URLs with permanent redirects and update internal links so crawlers stop requesting retired paths. If a page is intentionally removed, keep a useful custom error page and link users to relevant alternatives.

Standards reference: RFC 9110 Section 15.5.5 (404 Not Found).

View RFC 9110 section →

Related Client Error Codes

Commonly Referenced Status Codes

The most frequently searched HTTP status codes

Related Tools