HTTP Headers Analyzer
5 / 10
https://kontraktorpipagas.com
WordPress → LiteSpeed → Browser8 missing headers, 1 warnings, 2 notices
Header
Value
Explanation
x-powered-by
php/7.4.33
Some of the software used to generate or serve this page.
Warning Sharing too many details about a server or web application makes it easier for hackers to target a website. Avoid specific version numbers such as 7.4.33, especially when running software that is end-of-life and/or has known security bugs. Consider removing this header. At a miminum, remove any version number.
Warning Sharing too many details about a server or web application makes it easier for hackers to target a website. Avoid specific version numbers such as 7.4.33, especially when running software that is end-of-life and/or has known security bugs. Consider removing this header. At a miminum, remove any version number.
link
<https://kontraktorpipagas.com/wp-json/>; rel="https://api.w.org/"
rel="https://api.w.org/"
is where you can learn more about WordPress' REST API. Applications can interact with this WordPress site by sending and receiving JSON objects.link
<https://kontraktorpipagas.com/wp-json/wp/v2/pages/59>; rel="alternate"; type="application/json"
Specifies a link that might be of interest to the browser.
link
<https://kontraktorpipagas.com/>; rel=shortlink
rel="shortlink"
specifies a shorter URL for the current page, to be used in space constrained interfaces and/or for manual entry.etag
"342-1743404542;;;"
A unique identifier that changes every time a page at a given URL changes. It acts as a fingerprint. A cache can compare
Etag
values to see if the page has changed and became stale. For example, a browsers will send the ETag
value of a cached page in an If-None-Match
header. The web server compares the ETag
value sent by the browser with the ETag
value of the current version of the page. If both values are the same, the web server sends back a 304 Not Modified
status and no body.x-litespeed-cache
hit
The page was served from LiteSpeed's cache.
date
sun, 06 apr 2025 17:04:58 gmt
The date and time at which the request was made. A browser uses it for age calculations rather than using its own internal date and time; e.g. when comparing against
Max-Age
or Expires
.server
litespeed
platform
hostinger
Some of the software used to generate or serve this page.
strict-transport-security
max-age=31536000; includesubdomains; preload
The
Strict-Transport-Security
header (HSTS) instructs browsers to only use HTTPS for future connections to this domain, enhancing security by preventing downgrade attacks and cookie hijacking.max-age
specifies the time, in seconds, that the browser should remember to use HTTPS only for this domain.includesubdomains
instructs the browser that all subdomains are HTTPS-only as well.preload
recommends the domain for inclusion in browsers' preload lists. If accepted, the domain would get hardcoded into browsers as HTTPS-only.x-xss-protection
1; mode=block
This header enables the browser's built-in XSS protection. However, it's considered legacy and modern browsers may ignore it.
Notice While this header provides some protection, it's recommended to use
1
enables the browser's cross-site scripting (XSS) filtering.mode=block
instructs the browser to block the response if a XSS attack is detected, instead of sanitizing the page.Notice While this header provides some protection, it's recommended to use
Content-Security-Policy
instead, as it offers more comprehensive and flexible protection against XSS and other injection attacks.x-content-type-options
nosniff
The
The value
X-Content-Type-Options
header, when set to nosniff
, prevents MIME type sniffing. This enhances security by ensuring browsers respect the declared Content-Type of the response, mitigating MIME confusion attacks.The value
nosniff
is correctly set, providing protection against MIME type sniffing attacks.vary
user-agent
The
Notice Varying on
Vary
header specifies a list of headers that must be considered when caching responses. For a cached response to be used, these headers must match between the cached response and the new request. This ensures that the appropriate version of a resource is served based on factors like language, encoding, or device type.Notice Varying on
user-agent
can lead to low cache efficiency due to the high number of unique user agents. Only use this if you're serving significantly different content based on user agent.content-security-policy
missing Add a
Content-Security-Policy
header. The Content-Security-Policy
header helps browsers prevent cross site scripting (XSS) and data injection attacks.referrer-policy
missing Add a
Referrer-Policy
header. When a visitor navigates from one page to another, browsers often pass along referrer information. The Referrer-Policy
header controls how much referrer information a browser can share. This is important to configure when private information is embedded in the path or query string and passed onto an external destination.permissions-policy
missing Add a
Permissions-Policy
header. Restrict access to device features like the camera, microphone, location, accelerometer and much more.cross-origin-embedder-policy
missing Add a
Cross-Origin-Embedder-Policy
to specify how this page can be loaded by cross-origin resources.cross-origin-opener-policy
missing Add a
Cross-Origin-Opener-Policy
header to opt-in into better browser isolation.cross-origin-resource-policy
missing Add a
Cross-Origin-Resource-Policy
header to specify who can load this page.x-frame-options
missing Add a
X-Frame-Options
header. The X-Frame-Options
header prevents this URL from being embedded in an iframe
. This protects against clickjacking attacks. Alternatively, set a Content-Security-Policy
header with a frame-ancestor
directive.x-permitted-cross-domain-policies
missing Add a
X-Permitted-Cross-Domain-Policies
header to prevent Flash, Adobe Reader and other clients from sharing data across domains.Questions or feedback? Email dries@buytaert.net.