HSTS - Browser HTTPS Only for domain and subdomains
Download List of All Websites using HSTS - Browser HTTPS Only for domain and subdomains
The HTTP Strict-Transport-Security response header (often abbreviated as HSTS) lets a web site tell browsers that it should only be accessed using HTTPS, instead of using HTTP for domain and subdomainsfor 15552000 seconds
Private Cache-Control Header
Download List of All Websites using Private Cache-Control Header
The Cache-Control general-header field is used to specify directives for caching mechanisms in both requests and responses. Caching directives are unidirectional, meaning that a given directive in a request is not implying that the same directive is to be given in the response.
Tags:
No Cache Content
Download List of All Websites using No Cache Content
Forces caches to submit the request to the origin server for validation before releasing a cached copy.
Tags:
NO Store HTTP Cache-Control
Download List of All Websites using NO Store HTTP Cache-Control
The cache should not store anything about the client request or server response.
Tags:
Must Revalidate HTTP Cache-Control
Download List of All Websites using Must Revalidate HTTP Cache-Control
Indicates that once a resource has become stale (e.g. max-age has expired), a cache must not use the response to satisfy subsequent requests for this resource without successful validation on the origin server.
Tags:
Cache-Control Header Max-Age
Download List of All Websites using Cache-Control Header Max-Age
Specifies the maximum amount of time a resource will be considered fresh. Contrary to Expires, this directive is relative to the time of the request. this website is having max-age=0 secs.
Tags:
Vary Header check for User-Agent
Download List of All Websites using Vary Header check for User-Agent
When using the Vary: User-Agent header, caching servers should consider the user agent when deciding whether to serve the page from cache
Tags:
Vary Header Accept-Encoding
Download List of All Websites using Vary Header Accept-Encoding
The Accept-Encoding request HTTP header advertises which content encoding, usually a compression algorithm, the client is able to understand. Using content negotiation, the server selects one of the proposals, uses it and informs the client of its choice with the Content-Encoding response header.
Tags: