410 Gone

The resource is gone permanently and no forwarding address is known.

410 at a glance

Code: 410
Name: Gone
Class: 4xx Client error
Status: IANA-registered standard code
Defined in: RFC 9110, Section 15.5.11
Cacheable by default: Yes, heuristically cacheable (RFC 9110 section 15.1): without Cache-Control or Expires, caches may store it and pick a freshness lifetime themselves. Send explicit Cache-Control to stay in control.

What 410 means

410 Gone is a stronger 404: the server knows the resource used to exist, has removed it on purpose, and expects the removal to be permanent. Search engines drop 410 URLs from the index somewhat faster than 404s. 410 is heuristically cacheable.

What typically causes a 410

Expired listings, deleted accounts or retired API versions.
Deliberate content removal during a site clean-up.

Fix it on the server

Use 410 only when you are sure; if the content moved, use 301 instead.
For deprecated API versions, return 410 with a body pointing to the replacement and announce the date ahead with Sunset/Deprecation headers.

Fix it as a client or visitor

Remove the URL from bookmarks, sitemaps and integrations; retrying will not help.

Headers that go with 410

Header	Role
`Sunset`	RFC 8594: announces when a resource will go away, before it returns 410.

Example response

HTTP/1.1 410 Gone
Content-Type: application/json

{"error": "API v1 was retired on 2026-01-01, use /v2"}