How to check HTTP Responses (including status codes and free tools!)
What is HTTP?
HTTP is how the internet communicates and is the foundation of data communication. It stands for Hypertext Transfer Protocol. In essence, you use HTTP every time you navigate to a new website, or make a call to an API, or download an app.
What is an HTTP response code?
A response code or status code tells you if an HTTP request was successful. The values of response codes vary from 100-599. For a comprehensive list of all of the HTTP response codes, you can visit this link at W3.
You can check your page status with these codes.
Chances are you are having a very specific HTTP response that you want to look up. There are a lot of response codes, but let’s cover the basic list below to learn how to check HTTP response codes and how to read them!
Informational Status Codes (100-199)
100 Continue: A response that tells you that your request has worked thus far and that you may continue further if you need to.
Successful Status Codes (200-299)
200 OK: Your request was received and has succeeded!
Redirection Status Codes (300-399)
301 PERMANENT REDIRECT: This means that the page you were trying to reach has been permanently moved to a new location.
302 FOUND (now means temporary redirect): This means that the page you were trying to reach has changed, but only temporarily.
Client Error Status Codes (400-499)
400 BAD REQUEST: The server did not understand the request. This will be due to user syntax errors.
403 FORBIDDEN: This means that your device does not have authorization to access this content.
404 NOT FOUND: Exactly what it sounds like! You’ve probably seen this one before if you’ve tried to go to a page that doesn’t exist on a website. The server can not find the page you were looking for.
410 GONE: This response will be sent when the content has been deleted from the server and there is no redirect. Usually used for when temporary content meant to expire.
418 I’M A TEAPOT (no seriously): Okay, this one isn’t going to come up much, it’s a funny joke referring an April Fools joke in the Hyper Text Coffee Pot Control Protocol. Make no mistake though, it is a real protocol and some programmers may use it. This protocol is supposed to be used by teapots which are mistakenly asked to brew coffee. In-face Google has a fun little Easter Egg for this error code.
Server Error Status Codes (500-599)
500 INTERNAL SERVER ERROR: This means the server doesn’t know what to do with what you sent it. Trying again can usually solve this issue. Nothing is perfect!
503 SERVICE UNAVAILABLE: This means what it sounds like, the server is unavailable.
HTTP Response Code Checkers
httpstatus.io allows you to check headers of a website, check your redirects and status codes check your URL status and more. httpstatus.io is a bulk URL HTTP Status Code checker, so you can use it on more than one URL at a time!
For the below example I checked google.com and received the following readout:
Hey! We know these status codes! 301 permanently redirects us, 302 means the site was found and then 200 means it was successful!
Something interesting to note is that this redirect is from ‘google.com’ to ‘www.google.com’
If you put www.google.com, you only get codes 302 and 200. Pretty nifty huh? that allows you to follow redirect chains.
A redirect chain shows you where the original request bounces around to and from. Redirects usually happen to quickly for you to notice, but it’s important to know on a step-by-step level when you are trying to figure out HTTP issues. Another good site for this is called WhereGoes.com, all it does is- you guessed it – tell you where something goes!
HTTP Header Check Tools
WebSniffer has a powerful header checker tool for more advanced requests. The first thing it does is connect to the site’s IP address and then it displays your HTTP Response Header.
See TheFasterFixer.com’s HTTP Response Header below! It even gives you the content of the page as well. WebSniffer is a fantastic way to troubleshoot your HTTP response issues and get HTTP header information.
Hopefully this helped you identify some issues you may have had with your HTTP Response Codes. There are a lot more responses than the ones I’ve listed here. If you are having a specific issue, please reach out and let me know!
I plan on writing specific guides for ways to fix and troubleshoot each error code. I will add them to this guide as I write them.
Leave a comment if you have any questions!
Hi Everyone! I’m an IT manager and I’ve noticed that there are a lot of problems out there that just do not have clear and concise language for solving daily IT issues! On this channel, I hope to help you fix your IT issues and make life easier for you, whether you work in IT or if you just have something that needs fixing!