{
    "url": "https://firstnow.ru/blog/post/12-zachem-nuzhen-bortovoy-kompyyuter-i-kakoy-vybraty",
    "score": 1,
    "summary": {
        "missing": 8,
        "warnings": 4,
        "notices": 6
    },
    "caches": [
        "Website",
        "Nginx",
        "Browser"
    ],
    "headers": {
        "server": {
            "value": "nginx/1.22.0",
            "findings": [
                {
                    "severity": "info",
                    "message": "Identifies the software used by the origin server to handle the request (e.g. Apache, Nginx, Cloudflare)."
                },
                {
                    "severity": "warning",
                    "message": "The server header exposes a specific version number (1.22.0). This makes it easier for attackers to find known vulnerabilities for that version. Remove or suppress the version number."
                }
            ]
        },
        "date": {
            "value": "tue, 20 oct 2026 08:25:25 gmt",
            "findings": [
                {
                    "severity": "info",
                    "message": "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 <code>Max-Age</code> or <code>Expires</code>."
                }
            ]
        },
        "content-type": {
            "value": "text/html; charset=utf-8",
            "findings": [
                {
                    "severity": "info",
                    "message": "The type of the message body, specified as a <a href=\"https://en.wikipedia.org/wiki/Media_type\">MIME type</a>."
                }
            ]
        },
        "transfer-encoding": {
            "value": "chunked",
            "findings": [
                {
                    "severity": "info",
                    "message": "Specifies how the resource is <em>transferred</em>. Not to be confused with <code>Content-Encoding</code> which specifies how the request body is compressed. Transfer encoding operates at a lower level than content encoding."
                },
                {
                    "severity": "info",
                    "message": "<code>chunked</code> means that the data is sent in chunks. Chunks are sent out and received independently of one another. The server can <em>stream</em> the document and does not have to wait for the full document to be generated. Similarly, the browser can start processing chunks as they come in rather than having to wait for the entire document to be downloaded."
                }
            ]
        },
        "connection": {
            "value": "keep-alive",
            "findings": [
                {
                    "severity": "info",
                    "message": "Controls whether the TCP connection stays open after this request finishes. <code>keep-alive</code> means the browser can reuse the same connection for additional requests, avoiding the overhead of a new TCP handshake. <code>close</code> means the connection will be shut down after this response."
                }
            ]
        },
        "x-powered-by": {
            "value": "fat-free framework",
            "findings": [
                {
                    "severity": "info",
                    "message": "Some of the software used to generate or serve this page."
                }
            ]
        },
        "x-frame-options": {
            "value": "sameorigin",
            "findings": [
                {
                    "severity": "info",
                    "message": "<code>X-Frame-Options</code> prevents this URL from being embedded in an <code>iframe</code>. This protects against clickjacking attacks."
                },
                {
                    "severity": "info",
                    "message": "<code>sameorigin</code> allows this page to be displayed in an <code>iframe</code> on the same origin. This is the recommended setting."
                }
            ]
        },
        "x-xss-protection": {
            "value": "1; mode=block",
            "findings": [
                {
                    "severity": "info",
                    "message": "A legacy header that enables the browser's built-in cross-site scripting (XSS) filter. Modern browsers ignore it in favor of <code>Content-Security-Policy</code>."
                },
                {
                    "severity": "info",
                    "message": "<code>1</code> enables XSS filtering."
                },
                {
                    "severity": "info",
                    "message": "<code>mode=block</code> blocks the response entirely if an attack is detected, instead of sanitizing the page."
                },
                {
                    "severity": "notice",
                    "message": "Add a <code>Content-Security-Policy</code> header for more comprehensive protection."
                }
            ]
        },
        "x-content-type-options": {
            "value": "nosniff",
            "findings": [
                {
                    "severity": "info",
                    "message": "The <code>X-Content-Type-Options</code> 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."
                },
                {
                    "severity": "info",
                    "message": "The value <code>nosniff</code> is correctly set."
                }
            ]
        },
        "pragma": {
            "value": "no-cache",
            "findings": [
                {
                    "severity": "notice",
                    "message": "<code>Pragma: no-cache</code> forces revalidation with the origin server on every request. <code>Pragma</code> is a legacy HTTP/1.0 directive, superseded by <code>Cache-Control</code>. Remove <code>Pragma</code> to save bandwidth and processing power."
                }
            ]
        },
        "cache-control": {
            "value": "no-cache, no-store, must-revalidate",
            "findings": [
                {
                    "severity": "info",
                    "message": "<code>no-cache</code> means the response can be stored by <em>any</em> cache, but the stored response <strong>must</strong> be validated with the origin server before each reuse. If the origin confirms that the response hasn't changed, downloading of the full response body can be skipped."
                },
                {
                    "severity": "warning",
                    "message": "<code>no-cache</code> will cause a revalidation request to the origin server for <em>every</em> use of the cached response. Consider using <code>public</code> with appropriate <code>max-age</code> to improve caching efficiency."
                },
                {
                    "severity": "warning",
                    "message": "<code>no-store</code> means the response may <em>not</em> be stored in <em>any</em> cache, including the browser's cache. Every request will hit the origin server. If this page can be cached, consider using <code>public</code> with an appropriate <code>max-age</code>."
                },
                {
                    "severity": "info",
                    "message": "<code>must-revalidate</code> indicates that once a page becomes stale, both shared caches and browser caches must not use their stale copy without validating it with the origin server first."
                },
                {
                    "severity": "notice",
                    "message": "<code>must-revalidate</code> has no effect with <code>no-store</code> since nothing is cached. Remove <code>must-revalidate</code>."
                },
                {
                    "severity": "notice",
                    "message": "<code>must-revalidate</code> is redundant with <code>no-cache</code> since <code>no-cache</code> already requires revalidation. Remove <code>must-revalidate</code>."
                },
                {
                    "severity": "notice",
                    "message": "<code>no-cache</code> is redundant when <code>no-store</code> is set, though some sites keep both for compatibility with older caches."
                }
            ]
        },
        "expires": {
            "value": "thu, 01 jan 1970 00:00:00 +0000",
            "findings": [
                {
                    "severity": "info",
                    "message": "This <code>Expires</code> date is in the past: the page is considered stale and will be removed from <em>all</em> caches."
                },
                {
                    "severity": "notice",
                    "message": "The <code>Cache-Control</code> header, introduced in HTTP/1.1, supersedes the <code>Expires</code> header. Use a <code>Cache-Control</code> header with a <code>max-age</code> directive instead of <code>Expires</code>. <code>Cache-Control</code> is more powerful, but also more efficient in that it avoids roundtrips to the origin server."
                }
            ]
        },
        "content-encoding": {
            "value": "gzip",
            "findings": [
                {
                    "severity": "info",
                    "message": "Specifies how the resource is <em>compressed</em>. Not to be confused with <code>Transfer-Encoding</code> which specifies how the data is transferred."
                },
                {
                    "severity": "info",
                    "message": "<code>gzip</code> means that the data is compressed with <code>gzip</code>."
                },
                {
                    "severity": "warning",
                    "message": "Add a <code>Content-Length</code> header. The Content-Length header is required, unless the message is transported using chunked encoding. Without a <code>Content-Length</code> header some servers will respond with 400 (bad request) or terminate connections early."
                }
            ]
        }
    },
    "missing": {
        "strict-transport-security": {
            "message": "Add a <code>Strict-Transport-Security</code> header. The <code>Strict-Transport-Security</code> header or <i>HSTS</i> header is used to instruct browsers to only use HTTPS, instead of using HTTP. It helps enforce secure communication."
        },
        "content-security-policy": {
            "message": "Add a <code>Content-Security-Policy</code> header. The <code>Content-Security-Policy</code> header helps browsers prevent cross site scripting (XSS) and data injection attacks."
        },
        "referrer-policy": {
            "message": "Add a <code>Referrer-Policy</code> header. When a visitor navigates from one page to another, browsers often pass along <em>referrer information</em>. The <code>Referrer-Policy</code> header controls how much referrer information a browser can share. This is important to configure when private information is embedded in the <i>path</i> or <i>query string</i> and passed onto an external destination."
        },
        "permissions-policy": {
            "message": "Add a <code>Permissions-Policy</code> header. Restrict access to device features like the camera, microphone, location, accelerometer and much more."
        },
        "cross-origin-embedder-policy": {
            "message": "Add a <code>Cross-Origin-Embedder-Policy</code> header. It requires cross-origin resources to explicitly consent before this page can load them, protecting those resources from being exposed to Spectre-style timing attacks. Together with <code>Cross-Origin-Opener-Policy</code>, it enables cross-origin isolation and access to <code>SharedArrayBuffer</code>."
        },
        "cross-origin-opener-policy": {
            "message": "Add a <code>Cross-Origin-Opener-Policy</code> header. It prevents other sites from retaining a <code>window</code> reference to this page when opened via <code>window.open()</code> or navigation, blocking script-based attacks through shared browsing contexts."
        },
        "cross-origin-resource-policy": {
            "message": "Add a <code>Cross-Origin-Resource-Policy</code> header. It controls which origins can embed or load this page's resources (images, scripts, etc.), preventing hotlinking and cross-origin data leaks."
        },
        "x-permitted-cross-domain-policies": {
            "message": "Add a <code>X-Permitted-Cross-Domain-Policies</code> header to prevent Flash, Adobe Reader and other clients from sharing data across domains."
        }
    }
}