GetStatusCode.com/410 will always return a 410 HTTP Status Code. That is by design.

410 Gone

Client Error

The 4XX class of codes indicate you did something wrong. Specifically, there's an error on the client side.
Status Code Details, Courtesy of Wikipedia

Indicates that the resource requested is no longer available and will not be available again. This should be used when a resource has been intentionally removed and the resource should be purged. Upon receiving a 410 status code, the client should not request the resource again in the future. Clients such as search engines should remove the resource from their indices. Most use cases do not require clients and search engines to purge the resource, and a "404 Not Found" may be used instead.

GetStatusCode Heatmap

Request Details

For easy reference, some of the details of your request have been included below.

IP Address Info

107.22.118.242

ec2-107-22-118-242.compute-1.amazonaws.com

  • Ashburn City
  • VA State
  • US Country
  • 39.0437 / -77.4875 Net Location

User Agent Info

CCBot/2.0 (http://commoncrawl.org/faq/)

GET

    POST

      About GetStatusCodes.com

      This is a tool that I built just to give me an easy way to test scripts that need to handle a variety of http status codes. Even if I'm not integrating with a REST API or other web service that might present a variety of status codes, I often still need to gracefully handle the occasional unexpected 500 error. Short of deliberately coding a glitch (which is only an option if I'm in control of the remote end, which isn't always the case), it's hard to test this. So, I wrote this handy site that responds with the appropriate header for the major codes.

      Whether you want to test code like I often do or just see an example 410 http status code, this is a handy tool to use. Plus, it offers some basic information that I occasionally need as well, like IP geolocation (and it even uses HTML5 geolocation to tell how far off they are from each other) and user agent parsing for browser and operating system.

      This tool is free to use, but you should be mindful of its limitations. It does not fully and properly implement the HTTP specification (it's not RESTful in the slightest). It only spits out this page (roughly, with some variation by code requested) and the associated HTTP status code headers. My scripts key off those response headers (as do most frameworks I've dealt with), so that's sufficient to test. But if you're expecting a 301 to actually include a Location header, you won't find it here.

      If you appreciate this tool, feel free to link to it, share it on Facebook, and the like. The more people use this, the more I can justify adding features.

      Recent Categories
      Recent Cities
      City Region Country Status Code
      Dallas TX US 200 OK
      Dallas TX US 403 Forbidden
      Dallas TX US 500 Internal Server Error
      Ashburn VA US 422 Unprocessable Entity (WebDAV; RFC 4918)
      Dallas TX US 503 Service Unavailable
      Recent Operating Systems