All HTTP status codes

HTTP 404 Not Found

Client Error

The server can't find anything at the requested URL. It says nothing about whether the resource ever existed or will exist.

Defined in RFC 9110

Common causes

  • Mistyped or outdated URL / broken link
  • Resource deleted or moved without a redirect
  • Route not registered (deploy missing, wrong base path)
  • Case-sensitivity mismatches on the server

How to fix it

  1. Add a 301/308 redirect if content moved

  2. Audit internal links and sitemaps for stale URLs

  3. Confirm the route exists in the deployed version (not just locally)

  4. Return 410 instead when something is gone on purpose

Related status codes

410 Gone

The resource existed but was intentionally and permanently removed. Stronger than 404 — clients and crawlers should stop asking.

403 Forbidden

The server understood the request and refuses to authorize it. Unlike 401, re-authenticating won't help — the identity is known but lacks permission.

301 Moved Permanently

The resource has permanently moved to the URL in the Location header. Browsers cache it and search engines transfer ranking signals to the new URL.

Want to explore status codes interactively? Try the free HTTP Status Code Reference — search, categories and example responses, right in your browser.