HTTP Headers Analyzer
8 / 10
https://homeelevatorscottsdaleaz.com
WordPress → Nginx → Browser4 missing headers, 0 warnings, 2 notices
Header
Value
Explanation
server
nginx/1.17.9
date
sat, 10 may 2025 09:27:31 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
.content-length
63465
The size of the message body, in bytes.
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.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.x-frame-options
sameorigin
X-Frame-Options
prevents this URL from being embedded in an iframe
. This protects against clickjacking attacks.sameorigin
means that this page can be displayed in a iframe
, but only on the currrent origin. It can't be displayed on another domain. Consider setting this to deny
for added security.x-frame-options
sameorigin
X-Frame-Options
prevents this URL from being embedded in an iframe
. This protects against clickjacking attacks.sameorigin
means that this page can be displayed in a iframe
, but only on the currrent origin. It can't be displayed on another domain. Consider setting this to deny
for added security.strict-transport-security
max-age=31536000; includesubdomains
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.referrer-policy
no-referrer-when-downgrade
When a visitor navigates from one page to another page, browsers often pass along referrer information. The
Referrer-Policy
header controls how much referrer information a browser can share. This is important because private information can be embedded in the path or query string.no-referrer-when-downgrade
means that the protocol, host, port, path and query string are shared. It is only shared when the protocol security level remains the same (HTTP → HTTP, HTTPS → HTTPS) or improves (HTTP → HTTPS). When the protocol becomes less secure (HTTPS → HTTP), nothing is shared.content-security-policy
default-src *; script-src * 'unsafe-inline' 'unsafe-eval'; object-src *; style-src * 'unsafe-inline'; img-src * data:; media-src *; frame-src *; font-src * data:; connect-src *
The Content Security Policy (CSP) header helps prevent cross-site scripting (XSS), clickjacking, and other code injection attacks by specifying which dynamic resources are allowed to load.
Notice Consider adding the
default-src
sets the default policy for fetching resources like JavaScript, images, CSS, fonts, AJAX requests, frames, HTML5 media.script-src
specifies valid sources for JavaScript. This includes not only URLs loaded directly into <script>
elements, but also things like inline script event handlers (onclick) and XSLT stylesheets which can trigger script execution.object-src
defines what <object>
, <embed>
and <applet>
elements are allowed to be loaded and executed.style-src
defines what CSS stylesheets are allowed to be loaded.media-src
defines what <audio>
, <video>
and <track>
elements are allowed to be loaded.img-src
defines what images and favicons can be loaded.font-src
defines what fonts can be loaded using CSS's font-face
.frame-src
defines what <frame>
and <iframe>
elements can be loaded.Notice Consider adding the
upgrade-insecure-requests
directive to automatically upgrade HTTP requests to HTTPS, helping to prevent mixed content issues.x-content-security-policy
default-src *; script-src * 'unsafe-inline' 'unsafe-eval'; object-src *; style-src * 'unsafe-inline'; img-src * data:; media-src *; frame-src *; font-src * data:; connect-src *
Notice This is a deprecated version of the Content Security Policy header. Modern browsers use the
Content-Security-Policy
header without the "X-" prefix.x-webkit-csp
default-src *; script-src * 'unsafe-inline' 'unsafe-eval'; object-src *; style-src * 'unsafe-inline'; img-src * data:; media-src *; frame-src *; font-src * data:; connect-src *
permissions-policy
autoplay=*
Instructs a browser to selectively allow or deny certain browser APIs and features. It helps improve security.
etag
w/"f7e9-lsfoiquuxnky91mpyiyhwpzqfzk"
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. This particular Etag
value starts with w/
which means that it is a weak identifier; while unlikely, multiple pages might have the same identifier. Weak identifiers are used because strong identifiers can be difficult and costly to generate.vary
accept-encoding
The
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.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.
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.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-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.