HTTP 410 Gone — What It Means & How to Debug
HTTP 410 Gone is an HTTP response status code that indicates the requested resource is no longer available at the requested URI and no forwarding address is known. Unlike a 404, which is ambiguous about whether the resource ever existed, a 410 explicitly tells the client that the resource was intentionally removed and will not be returning.
What It Means
Defined in RFC 7231 Section 6.5.9, the 410 status code is the server’s definitive statement: “This resource existed, it is gone, and there is no redirect.” Search engines that encounter a 410 will typically remove the URI from their index much faster than they would for a 404.
The response body often includes a page explaining why the resource was removed and pointing to alternative resources.
When It’s Sent
- Deleted content — A user deleted their account or a specific post, and the server intentionally removes the resource.
- Expired promotions — A limited-time offer or event page that is no longer relevant.
- Deprecated API endpoints — An old API version is decommissioned with no migration path (though 308 or 301 with a redirect is usually preferred).
- Legal takedowns — Content removed due to DMCA notice or other legal requests.
- Removed documentation — A tutorial or reference page that has been superseded and intentionally deleted.
Real Example
The following curl command simulates a request to a resource that has been permanently removed:
curl -v https://httpbin.org/status/410Expected response:
< HTTP/1.1 410 GONE
< Date: Sat, 20 Jun 2026 12:00:00 GMT
< Content-Type: text/html; charset=utf-8
< Content-Length: 247
< Server: gunicorn/19.9.0
<
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2 Final//EN">
<title>410 Gone</title>
<h1>Gone</h1>
<p>The requested resource is no longer available at this URI.</p>How to Debug
Client-Side
- Double-check the URL — Ensure there is no typo. A 410 means the server explicitly deletes the resource, but typos can produce 404 or 410 depending on server config.
- Search for the new location — The resource may have moved to a new URI. Use site search or look for redirects at a different path.
- Check API changelog — If the resource was a deprecated API endpoint, the provider likely announced a replacement. Look for migration guides.
- Remove bookmarks — If you have the URI bookmarked, delete it. The resource is gone permanently.
- Handle gracefully in code — If your application encounters a 410, treat it as a permanent error. Remove the URI from your database and stop retrying.
Server-Side
- Log the request — Record which resources are producing 410s to understand user behavior and identify unintended deletion.
- Provide a helpful body — Include a message explaining why the resource was removed and link to alternatives or a contact page.
- Use 301/308 instead if possible — If the resource exists at a new URI, redirect instead of returning 410. Only use 410 when deletion is intentional and permanent.
- Return 410 versus 404 — Use 410 when you want to signal deletion explicitly (e.g., to search engines). Use 404 when you want to remain ambiguous about the resource’s existence.
Common Causes Table
| Scenario | Likely Cause | How to Fix |
|---|---|---|
| Old blog post returns 410 | Post was deleted by the author | Restore from backup or use 301 to a related post |
| API v1 endpoint returns 410 | API version was deprecated and removed | Migrate to v2 endpoint; check migration docs |
| User avatar returns 410 | User deleted their account | Display default avatar; remove reference |
| Promotional page gone | Campaign ended and page was removed | Redirect to current promotions or homepage |
| Legal takedown notice | Content removed due to DMCA | Serve a 410 with takedown notice info |
FAQ
Related Codes
HTTP 404 Not Found — The server cannot find the requested resource.
HTTP 301 Moved Permanently — The resource has been assigned a new permanent URI.
HTTP 410 Gone — The requested resource is permanently gone.
HTTP 451 Unavailable For Legal Reasons — The resource was removed due to legal demand.
Built by the developers of DodaTech
Doda Browser, DodaZIP & Durga Antivirus Pro