A worked example, rendered from real sample data. Sign in to run the tool on your own input.
404═══ 404 Not Found ═══
Class: 4xx · Client error
Meaning: Resource does not exist (or the server doesn't want to admit it does).
Specification: RFC 9110 §15.5.5
Response body allowed: yes
Cacheable by default: no
Safe to retry: no
ℹ Some APIs return 404 instead of 403 to hide private resources.
─── When you will see it ───
• GET /users/999 — no such user.
─── Sample response ───
HTTP/1.1 404 Not Found
Date: Mon, 01 Jan 2024 12:00:00 GMT
Server: example/1.0
Content-Type: application/json
{
"error": "not_found",
"message": "Resource does not exist (or the server doesn't want to admit it does)."
}
─── fetch() handler ───
const res = await fetch("https://api.example.com/resource");
if (res.status === 404) {
// Not Found: Resource does not exist (or the server doesn't want to admit it does).
showNotFound();
}
─── Nearby codes ───
• 401 Unauthorized
• 402 Payment Required
• 403 Forbidden
• 405 Method Not Allowed
• 406 Not Acceptable
• 407 Proxy Authentication Required
Quick lookup of HTTP status codes and their meanings. Part of the DevTools Surf developer suite. Browse more tools in the Networking collection.