HTTP Headers Analyzer

6 / 10

https://metadrop.net/en

Drupal → Nginx → Browser
0 missing headers, 3 warnings, 4 notices
JSON API

Header	Value	Explanation
server	nginx	Identifies the software used by the origin server to handle the request (e.g. Apache, Nginx, Cloudflare). Notice Consider removing or minimizing the `Server` header. Even without a version number, it reveals the server software, which aids reconnaissance.
date	wed, 11 nov 2026 01:03:53 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-type	text/html; charset=utf-8	The type of the message body, specified as a MIME type.
cache-control	max-age=900, public	`public` means the response may be stored by all caches, including browser caches, CDNs, and shared caches. `max-age` specifies the maximum amount of seconds a page is considered valid. The higher `max-age`, the longer a page can be cached.
x-drupal-dynamic-cache	hit	The page was served from Drupal's "dynamic page cache". This is a special cache that can cache pages minus the personalized parts. It makes it possible to cache pages with dynamic content.
link	<https://metadrop.net/en/node/4.md>; rel="alternate"; type="text/markdown"; title="drupal development & consultancy for growth"	`rel="alternate"` specifies an alternate version of the current page, often using a different language (`hreflang` attribute), a different MIME type (`type` attribute) or a different media format (`media` attribute).
content-language	en	Specifies the page's intended audience. For example, `en-US` means that the document is intended for English language speakers in the United States. The language tags are defined in RFC 5646.
x-content-type-options	nosniff	The `X-Content-Type-Options` header prevents browsers from guessing a response's content type. Without it, browsers may interpret files differently than intended, which can lead to security vulnerabilities. The value `nosniff` is correctly set.
x-frame-options	sameorigin	`X-Frame-Options` prevents this URL from being embedded in an `iframe`. This protects against clickjacking attacks. `sameorigin` allows this page to be displayed in an `iframe` on the same origin. This is the recommended setting.
vary	cookie,accept,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-generator	drupal 11 (https://www.drupal.org)	Some of the software used to generate or serve this page.
content-security-policy-report-only	script-src 'self' 'unsafe-inline' 'unsafe-eval' https://unpkg.com/ cdn.jsdelivr.net https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://d3js.org https://unpkg.com https://www.recaptcha.net; script-src-attr 'self' 'unsafe-inline'; script-src-elem 'self' 'unsafe-inline' http://stats.metadrop.pro/ https://www.googletagmanager.com/ https://unpkg.com/ https://www.recaptcha.net/ https://www.gstatic.com/ https://www.googleadservices.com/ cdn.jsdelivr.net https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://d3js.org https://unpkg.com https://www.recaptcha.net; style-src 'self' cdn.jsdelivr.net https://unpkg.com; style-src-attr 'self' 'unsafe-inline'; style-src-elem 'self' 'unsafe-inline' cdn.jsdelivr.net https://unpkg.com; frame-ancestors 'self'; report-uri /en/system/reporting/csp; report-to csp	Works like `Content-Security-Policy`, but violations are only reported, not blocked. This lets you test a new CSP in production without breaking anything: the browser logs violations to the specified `report-uri` while still loading all resources normally.
content-security-policy	object-src 'none'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://unpkg.com/ cdn.jsdelivr.net https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://d3js.org https://unpkg.com https://www.recaptcha.net; script-src-attr 'self' 'unsafe-inline'; script-src-elem 'self' 'unsafe-inline' http://stats.metadrop.pro/ https://www.googletagmanager.com/ https://unpkg.com/ https://www.recaptcha.net/ https://www.gstatic.com/ https://www.googleadservices.com/ cdn.jsdelivr.net https://cdn.jsdelivr.net https://cdnjs.cloudflare.com https://d3js.org https://unpkg.com https://www.recaptcha.net; style-src 'self' cdn.jsdelivr.net https://unpkg.com; style-src-attr 'self' 'unsafe-inline'; style-src-elem 'self' 'unsafe-inline' cdn.jsdelivr.net https://unpkg.com; frame-ancestors 'self'; report-uri /en/system/reporting/csp; report-to csp; upgrade-insecure-requests	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. `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. `frame-ancestors` defines what parents may embed a page using `<frame>`, `<iframe>`, `<object>`, `<embed>` or `<applet>`. `report-to` defines the URL that violations will be reported to. `report-to` is designed to replace `report-uri`, but still lacks universal browser support. `report-uri` defines the URL that violations will be reported to. While `report-uri` is officially deprecated in favor of `report-to`, limited browser support for the latter means `report-uri` remains a viable option for now. `upgrade-insecure-requests` instructs browsers to replace insecure URLs (HTTP) with secure URLs (HTTPS). Warning `unsafe-inline` in `script-src` allows execution of inline scripts, which effectively disables CSP's XSS protection. Consider using nonces or hashes instead. Warning `unsafe-eval` allows `eval()` and similar dynamic code execution, which can be exploited for XSS. Consider refactoring code to avoid `eval()`. Notice No `default-src` directive is set. Without it, directives that are not explicitly defined have no fallback restriction. Notice Consider adding `base-uri 'self'` or `base-uri 'none'` to prevent base tag injection, which can redirect relative URLs to an attacker-controlled domain.
reporting-endpoints	csp="/en/system/reporting/csp", csp_reportonly="/en/system/reporting/csp_reportonly", default="/en/system/reporting/default"	Defines named endpoints where the browser should send reports about security violations, deprecations, and other issues. This is the modern replacement for the `Report-To` header, using a simpler key-value syntax.
cross-origin-embedder-policy	require-corp	Controls whether this page can load resources (images, scripts, iframes) from other origins. When set, every cross-origin resource must explicitly opt in (via a `Cross-Origin-Resource-Policy` header or CORS) before this page can load it. This protects those other origins: by requiring their consent, the browser ensures their resources aren't exposed to Spectre-style timing attacks from this page. Setting this header (together with `Cross-Origin-Opener-Policy: same-origin`) is also required to enable powerful features like `SharedArrayBuffer` and high-resolution timers. `require-corp` means this page can only embed same-origin resources, or cross-origin resources that explicitly consent by sending a `Cross-Origin-Resource-Policy: cross-origin` header (or the equivalent CORS headers). Resources without that consent are blocked.
etag	"1794359033-gzip"	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 has become stale. For example, a browser 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.
content-encoding	gzip	Specifies how the resource is compressed. Not to be confused with `Transfer-Encoding` which specifies how the data is transferred. `gzip` means that the data is compressed with `gzip`. Warning Add a `Content-Length` header. The Content-Length header is required, unless the message is transported using chunked encoding. Without a `Content-Length` header some servers will respond with 400 (bad request) or terminate connections early.
x-proxy-cache	miss	The page was not served from a cache.
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	strict-origin-when-cross-origin	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. `strict-origin-when-cross-origin` means that the full URL (protocol, host, port, path and query string) is shared for same-origin requests. For cross-origin requests, only the origin (protocol, host, and port) is shared, and only when the protocol security level stays the same or improves (HTTP → HTTP, HTTPS → HTTPS). For cross-origin requests where the protocol downgrades (HTTPS → HTTP), nothing is shared.
permissions-policy	accelerometer=(), camera=(), geolocation=(), microphone=()	Controls which browser features and APIs (camera, microphone, geolocation, payment, USB, etc.) this page and its embedded iframes are allowed to use. Each feature is set to an allowlist of origins; an empty list `()` disables the feature entirely. This is a defense-in-depth measure: even if an attacker injects script via XSS, they cannot access the restricted APIs.
cross-origin-opener-policy	same-origin-allow-popups	Controls whether other pages can access this page's `window` object (and vice versa) when opened via `window.open()` or by navigating to a new page. Without this header, a malicious page could open your site and retain a reference to its `window`, enabling script-based attacks through the shared browsing context. Setting this to `same-origin` severs that link for cross-origin pages. Note: COOP governs top-level documents and popups, not iframes. Use `X-Frame-Options` or CSP `frame-ancestors` to control iframe embedding. `same-origin-allow-popups` isolates this page from cross-origin openers (like `same-origin`), but still allows popups opened by this page to retain a connection if the popup has COOP set to `unsafe-none` (any origin) or `same-origin-allow-popups` (same origin only). This is useful for pages that need to interact with OAuth or payment popups.
cross-origin-resource-policy	cross-origin	Controls which origins are allowed to load this resource (e.g. embed this image, load this script). This prevents other sites from hotlinking your resources and is how a resource signals its consent to be loaded by pages that use `Cross-Origin-Embedder-Policy`. Notice `cross-origin` means the resource can be loaded by documents from any origin. This is the least secure option.
x-permitted-cross-domain-policies	none	Instructs clients like Flash and Acrobat Reader what cross-domain policy they have to use. `none` is the most secure setting. Data can't be shared across domains.