This tool shows the headers of a specific page on your website. It also checks the redirect and explains if the redirect is permanent or temporary.
A 301 redirect is a status code that provides information about search engines and users that the page has permanently moved and makes sure they are sent to the correct page. As this is permanent, when a 301 redirect is used it means that the content of the page has moved forever. Users are redirected to a new page, which has replaced the previous one.
Redirection usually helps to change the URL of the page when it appears in search engine results. If you have invested in creating a website or opening an online store, pay close attention to the impact this has on your site.
You can think of a 301 redirect as a change of address form that you would have to fill out with the Postal Service if you had to move. Just as your mail is redirected from your old address to your new address, your web traffic is sent from your old URL to your new URL.
Fortunately, you won't lose all your hard work building your old site in the search engine results pages (SERPs). All of your existing SEO value and link equity for the old URL is transferred to your new URL.
As we know that 301 redirect is a permanent relocation of your URL, a 302 redirect is a temporary change that redirects both users and search engines to the desired new location for a limited period of time, until the redirect is removed. . This 302 redirect can show up as a 302 found (HTTP 1.1) or move temporarily (HTTP 1.0).
A 302 redirect is much easier to do, as it can be done using a meta tag or in Javascript, rather than requiring the webmaster to access server files and spend the extra time needed to create a 301 redirect.
Using a 302 redirect when you should have used a 301 redirect becomes a problem when search engines try to determine which page is of higher value. The search engine is likely to only include one version of the page in the search engine results, which means the wrong page could end up being the one listed. This problem will get worse over time as a chain of redirects to older sites develops.
Visit Home and click on the tools and select header
Then Enter the URL of any page and click on the submit button
All the information of that page will displayed with details
Xhaami's Header Checker Free tools provide you with a comprehensive report of any page or post on your website. Its includes many features which are going to be discussed below
The HTTP Cache-Control header field contains directives (instructions), both in requests and responses, that control caching across browsers and shared caches (eg Proxies, CDN).
This feature provides information regarding text/HTML; charset=UTF-8
The HTTP ETag (or entity tag) response header is an identifier for a specific version of a resource. It allows caches to be more efficient and save bandwidth since a web server does not need to resend a full response if the content has not changed. In addition, electronic Etags help prevents simultaneous updates to a resource from overwriting each other ("mid-air collisions").
If the resource at a given URL changes, a new Etag value must be generated. A comparison of them can determine whether two representations of a resource are the same.
The X-Content-Type-Options response HTTP header is a marker used by the server to indicate that the MIME types advertised in the Content-Type headers should be followed and not changed. The header allows you to prevent the detection of MIME types by saying that the MIME types are set deliberately.
This header was introduced by Microsoft in IE 8 as a way for webmasters to block content crawling from happening and could transform non-executable MIME types into executable MIME types. Other browsers have since introduced it, even if their MIME detection algorithms were less aggressive.
As of Firefox 72, top-level documents also prevent MIME detection (if the content type is provided). This can cause HTML web pages to download instead of render when served with a MIME type other than text/html. Make sure you set both headers correctly.
The X-Frame-Options HTTP response header can be used to indicate whether or not a browser should be allowed to render a page in a <frame>, <iframe>, <embed>, or <object>. Sites can use this to prevent clickjacking attacks by making sure their content is not embedded on other sites.
Additional security is provided only if the user accessing the document uses a browser that supports X-Frame-Options.
The idea of X-Request-ID is that a client can create a random ID and pass it to the server. The server then includes that ID in every log statement it creates. If a client receives an error, it can include the ID in an error report which allows the server operator to look up the corresponding log statements (without having to rely on IP timestamps etc).
The X-XSS-Protection HTTP response header is a feature in Internet Explorer, Chrome, and Safari that prevents pages from loading when they detect reflected cross-site scripting (XSS) attacks. These protections are largely unnecessary in modern browsers when sites implement a strong content security policy that disables the use of JavaScript online ('unsafe-inline').
The Content-Length header tells the size of the message body, in bytes, sent to the recipient. You may read more about content length here