HTTP 410 Gone
Updated Free mock REST & WebSocket APIs
HTTP 410 Gone — The resource used to exist but was removed on purpose and won't come back.
- Class
- 4xx Client Error
- Defined in
- RFC 9110 §15.5.11
- Official
- Yes (IANA registry)
- Cacheable by default
- Yes (heuristically, per RFC 9110)
- Safe to retry
- Not without changing the request
Try it: get a real 410 response
Our test endpoint answers every request with 410 Gone.
curl -i https://mockfox.dev/api/status/410Use it in tests, health-check monitors or to see how your client handles a 410. Add ?delay=2000 to slow it down.
What does HTTP 410 mean?
A stronger 404: tells clients and search engines the removal is permanent and intentional, so links should be deleted. Google treats 410 like 404 but may drop the URL from its index slightly faster. Use it for deleted products, expired listings or retired API versions; if there's a replacement page, a 301 redirect is better.
How to fix 410
- Visitors: Reload the page, check the address for typos, and clear the site's cookies. If it persists, the site owner needs to fix it.
- Developers: Read the response body and server logs for details, fix the request (method, headers, body, credentials) and return a clear error message to clients.
Example 410 response
HTTP/1.1 410 Gone
Cache-Control: max-age=86400
Content-Type: application/json
{"status":410,"error":"Gone"}4xx Client Error: The request contains an error or can't be fulfilled — fix the request before retrying. See the full list of HTTP status codes.
Related status codes
- 404 Not FoundThe server can't find anything at the requested URL.
- 301 Moved PermanentlyThe resource has a new permanent URL, given in the Location header.
- 308 Permanent RedirectThe resource has a new permanent URL and the client must repeat the request with the same method and body.
Related tools
Frequently asked questions
What does HTTP 410 Gone mean?
The resource used to exist but was removed on purpose and won't come back.
Is 410 a client or a server error?
410 is a 4xx code, so it signals a problem with the request (as seen by the server). Retrying the identical request usually gives the same result.
Where is 410 defined?
In RFC 9110 §15.5.11. It's listed in the IANA HTTP Status Code Registry.
How can I test how my app handles a 410?
Call https://mockfox.dev/api/status/410 — it responds with 410 to any method, with CORS enabled. Add ?delay=2000 to simulate a slow response.