HTTP Header Response Codes Check Tool

See how to use HTTP Header Response Codes Check Tool

We limit this tool to 5 runs per day, per user, because of the resources our HTTP Header Response Codes Check Tool uses. If you would like to use the online sitemap generator tool more than 5 times, please bookmark this page and come back after 24 hours.

Use the HTTP Header Check Tool to see which response code your webserver is returning for a requested URL. This header checker tool can provide valuable information on the status of a requested URL. Simply type or paste the URL in the box below, and then click Ninja Check.

Note: There may be more than one response code returned by the HTTP header checker tool if the original URL is redirected to another URL.

Get important information about the status of a URL by using this HTTP Header Check Tool up to 5 times a day. Know in an instant if the URL is returning a 200 OK, 301 redirect, 404, or anything else that might indicate a problem with the website. This tool is perfect for periodically checking on the HTTP headers of a homepage and top landing pages as an ongoing quality check, or determining the success of a recent site architecture change. Make sure your redirects are all 301s, or that your users are not encountering errors you did not know about with the HTTP Header Check Tool HTTP Header Check Tool Response Code Key

100's InformationalResponses

  • 100 Trying: extended search being performed may take a significant time so a forking proxy must send a 100 Trying response
  • 180 Ringing
  • 181 Call Is Being Forwarded
  • 182 Queued
  • 183 Session Progress

200's SuccessfulResponses

  • 200 OK
  • 202 accepted: It Indicates that the request has been understood but actually can't be processed
  • 204 No Notification [RFC5839]

300's RedirectionResponses

  • 300 Multiple Choices
  • 301 Moved Permanently
  • 302 Moved Temporarily
  • 305 Use Proxy
  • 380 Alternative Service

400's Client FailureResponses

  • 400 Bad Request
  • 401 Unauthorized (Used only by registrars or user agents. Proxies should use proxy authorization 407)
  • 402 Payment Required (Reserved for future use)
  • 403 Forbidden
  • 404 Not Found (User not found)
  • 405 Method Not Allowed
  • 406 Not Acceptable
  • 407 Proxy Authentication Required
  • 408 Request Timeout (Couldn't find the user in time)
  • 409 Conflict
  • 410 Gone (The user existed once, but is not available here anymore.)
  • 412 Conditional Request Failed
  • 413 Request Entity Too Large
  • 414 Request-URI Too Long
  • 415 Unsupported Media Type
  • 416 Unsupported URI Scheme
  • 417 Unknown Resource-Priority
  • 420 Bad Extension (Bad SIP Protocol Extension used, not understood by the server)
  • 421 Extension Required
  • 422 Session Interval Too Small
  • 423 Interval Too Brief
  • 424 Bad Location Information
  • 428 Use Identity Header
  • 429 Provide Referrer Identity
  • 433 Anonymity Disallowed
  • 436 Bad Identity-Info
  • 437 Unsupported Certificate
  • 438 Invalid Identity Header
  • 480 Temporarily Unavailable
  • 481 Call/Transaction Does Not Exist
  • 482 Loop Detected
  • 483 Too Many Hops
  • 484 Address Incomplete
  • 485 Ambiguous
  • 486 Busy Here
  • 487 Request Terminated
  • 488 Not Acceptable Here
  • 489 Bad Event
  • 491 Request Pending
  • 493 Undecipherable (Could not decrypt S/MIME body part)
  • 494 Security Agreement Required

500's Server FailureResponses

  • 500 Server Internal Error
  • 501 Not Implemented: The SIP request method is not implemented here
  • 502 Bad Gateway
  • 503 Service Unavailable
  • 504 Server Time-out
  • 505 Version Not Supported: The server does not support this version of the SIP protocol
  • 513 Message Too Large
  • 580 Precondition Failure

600's Global FailureResponses

  • 600 Busy Everywhere
  • 603 Decline
  • 604 Does Not Exist Anywhere
  • 606 Not Acceptable

Feedback

 

Users comments:

Login or register to post comments and rate

Not rated yet.