Security Headers Scanner
Check a site's HTTP response headers: Content-Security-Policy, HSTS, X-Frame-Options, referrer and permissions policy, and the dozens of value-level mistakes that weaken each one.
High11Medium28Low44Info50
High11 checks
- Missing HTTP Strict Transport Security (HSTS)The server does not send the Strict-Transport-Security header, which tells browsers to only connect via HTTPS.
- Missing Content Security Policy (CSP)No Content-Security-Policy header was found. CSP helps prevent cross-site scripting (XSS) and data injection attacks.
- CSP Allows unsafe-inline ScriptsCSP script-src permits inline scripts without nonce or hash.
- CSP Allows unsafe-evalContent Security Policy permits eval().
- X-Frame-Options: ALLOWALLALLOWALL (Chromium extension) explicitly disables framing protection. Use CSP frame-ancestors instead.
- Cache-Control: public on sensitive resourceA response containing authenticated or user-specific content is served with Cache-Control: public, allowing it to be cached by shared proxies.
- Site served over plain HTTP (no TLS at all)The scanned URL uses the plain http:// scheme, meaning the connection is not encrypted at all. This check does not negotiate a TLS handshake or detect specific deprecated TLS versions (TLS 1.0/1.1) on an HTTPS endpoint; it only flags a bare HTTP URL.
- HTTP resources loaded on HTTPS page (mixed content)An HTTPS page loads scripts, images, or other resources over HTTP, triggering browser mixed content warnings.
- Form submits data over unencrypted HTTPAn HTML form uses an HTTP (not HTTPS) action URL, transmitting form data in plaintext.
- Cookies missing security attributesOne or more cookies are set without required security attributes (Secure, HttpOnly, SameSite).
- Private Network Access Allowed With Wildcard CORSAccess-Control-Allow-Private-Network is set to true while Access-Control-Allow-Origin is a wildcard, letting any public website's script reach into the private network.
Medium28 checks
- Missing Clickjacking ProtectionNeither X-Frame-Options nor CSP frame-ancestors directive is set, leaving the site vulnerable to clickjacking.
- Wildcard CORS PolicyThe Access-Control-Allow-Origin header is set to '*', allowing any origin to make cross-origin requests.
- Dangerous CORS ConfigurationThe server allows credentials with a wildcard origin, a self-defeating combination that no compliant browser will actually honor.
- CSP Report-Only Without EnforcementCSP-Report-Only is set but no enforcing CSP header exists.
- Content Security Policy Contains Weak DirectivesThe CSP header contains weak directives that reduce its effectiveness.
- Missing CSP frame-ancestors DirectiveNeither CSP frame-ancestors nor X-Frame-Options header is present.
- CSP Missing form-action DirectiveThe CSP header exists but does not contain a form-action directive to restrict form submission targets.
- CSP Missing base-uri DirectiveThe CSP header exists but does not contain a base-uri directive.
- CSP Missing object-src DirectiveThe CSP header exists but does not contain an object-src directive to block plugins.
- CSP Uses Wildcard SourceContent Security Policy uses wildcard (*) as a source.
- Unsafe Referrer-Policy ValueReferrer-Policy uses a value that leaks full URLs.
- CSP Uses unsafe-hashesCSP policy includes the unsafe-hashes directive, a hash-locked allowlist for specific pre-approved inline event handlers.
- CSP Allows Object/Embed SourcesCSP allows plugins via object-src.
- Invalid X-Frame-Options ValueX-Frame-Options has invalid value.
- Sensitive Page Missing no-storePage with credentials lacks Cache-Control: no-store.
- CORS Allow-Headers WildcardACA-Headers: * lets any browser send any header. Restrict to the headers you actually use.
- CORS Allows 'null' OriginAccess-Control-Allow-Origin is set to the literal string 'null'. The 'null' origin is sent by sandboxed iframes, data: URIs, and some file:// contexts, so trusting it lets attacker-controlled sandboxed content bypass the intended origin restriction.
- __Host- cookie prefix with wrong attributesA cookie using the __Host- prefix must have Secure, Path=/, and no Domain attribute. Otherwise the browser silently rejects it.
- Missing X-Content-Type-Options headerThe server does not send the X-Content-Type-Options: nosniff header, allowing browsers to guess content types.
- CSP allows data: URIs in script or object sourcesThe Content-Security-Policy permits data: URIs as a script or object source, enabling data-URI-based script execution.
- CSP script-src allows HTTP sourcesThe Content-Security-Policy allows scripts to be loaded over unencrypted HTTP, enabling man-in-the-middle injection of arbitrary JavaScript.
- X-Content-Type-Options set to an invalid valueThe X-Content-Type-Options header is present but set to a value other than "nosniff", making it ineffective.
- Debug header present in production responseA debug-related response header is present (e.g., X-Debug-Info, X-Debug-Token, X-Symfony-Debug), revealing application internals.
- CORS allows overly broad HTTP methodsAccess-Control-Allow-Methods lists methods (e.g., PUT, DELETE, PATCH) that the endpoint does not actually use.
- HSTS header missing includeSubDomains directiveThe Strict-Transport-Security header is present but does not include includeSubDomains, leaving subdomains unprotected.
- COOP Report-Only Without EnforcementCross-Origin-Opener-Policy-Report-Only is set but no enforcing Cross-Origin-Opener-Policy header exists.
- SharedArrayBuffer Used Without Cross-Origin IsolationAn inline script on the page constructs a SharedArrayBuffer, but the response headers do not establish cross-origin isolation: Cross-Origin-Opener-Policy: same-origin combined with Cross-Origin-Embedder-Policy: require-corp or credentialless.
- Cache-Control Missing no-store on Token-Bearing JSON ResponseA JSON API response body contains a key that looks like a live credential, such as access_token, refresh_token, api_key, or session_token, but the Cache-Control header does not include no-store.
Low44 checks
- Missing Referrer-Policy HeaderThe Referrer-Policy header is not set. This controls how much referrer information is sent with requests.
- Missing Permissions-Policy HeaderThe Permissions-Policy (formerly Feature-Policy) header is not set.
- Missing X-XSS-Protection HeaderThe X-XSS-Protection header is not set and no Content-Security-Policy is present.
- CORS Origin Reflection with Credentials (unverified)A single scanned response shows Access-Control-Allow-Origin set to the exact origin the scanner requested from, with credentials allowed. This is indistinguishable, from one response alone, between a server that blindly reflects any Origin and a server that correctly validated it against a strict allowlist.
- Logout Page Missing Clear-Site-Data HeaderA logout page was detected but it does not send the Clear-Site-Data header to clear cookies, storage, and cache.
- CSP Missing default-src FallbackCSP has no default-src directive.
- Timing-Allow-Origin wildcardTiming-Allow-Origin is set to '*', allowing any origin to read Resource Timing API data exposed via Server-Timing.
- X-XSS-Protection Explicitly DisabledX-XSS-Protection set to 0.
- CSP Missing frame-src DirectiveCSP lacks frame-src directive for iframe sources.
- CSP contains unsupported / legacy directivesThe CSP names a directive browsers no longer implement (allow-http, reflected-xss), or its script-src combines 'none' with 'unsafe-inline' or 'unsafe-eval'. Directive names are matched as names, so a host or report endpoint whose path happens to contain one of those words is not reported.
- CSP Header > 4KBCSP headers longer than ~4KB are silently dropped by some browsers.
- Server-Timing exposes sensitive keyThe Server-Timing response header includes custom keys that may expose internal metrics like db, sql, redis, cache, or query durations.
- Missing Cache-Control headerNo Cache-Control header is present, leaving caching behavior undefined and potentially caching sensitive responses.
- Sensitive header exposed via Access-Control-Expose-HeadersThe Access-Control-Expose-Headers response header names a specific sensitive header (Authorization, Set-Cookie, or X-Csrf-Token), exposing it to cross-origin JavaScript regardless of how many other headers are listed alongside it.
- Access-Control-Expose-Headers lists many response headersAccess-Control-Expose-Headers lists five or more entries, exposing a large number of response headers to cross-origin JavaScript.
- CORS preflight cache time is too longThe Access-Control-Max-Age value is very large, caching CORS preflight results for an excessively long time.
- CSP missing upgrade-insecure-requests directiveThe Content-Security-Policy header does not include upgrade-insecure-requests, leaving HTTP sub-resources unprotected.
- HSTS header has weak directives (missing preload and/or low max-age)The Strict-Transport-Security header is present but is missing the preload directive, has a max-age below the 1-year minimum, or both. The finding's evidence text states which of the two conditions actually applies.
- Server header discloses software identityThe HTTP Server response header identifies the web server software by name.
- Server header reveals detailed version numberThe Server header exposes the exact version of the web server software, enabling targeted version-specific attacks.
- X-Powered-By header reveals application frameworkThe X-Powered-By response header discloses the application framework and sometimes version (e.g., "Express", "PHP/8.1").
- X-AspNet-Version header exposes ASP.NET versionThe X-AspNet-Version header is present and reveals the exact ASP.NET framework version.
- X-AspNetMvc-Version header exposes MVC versionThe X-AspNetMvc-Version header reveals which version of ASP.NET MVC the application is running.
- Via header reveals proxy infrastructureThe Via header is present and reveals proxy server software names or versions in the request chain.
- X-Runtime header reveals request processing timeThe X-Runtime header is present, exposing per-request server processing time in milliseconds.
- X-Backend-Server header reveals backend hostnameThe X-Backend-Server header discloses the internal hostname or IP of the backend server that handled the request.
- ETag reveals server inode numberThe ETag header format suggests it includes a file inode number, potentially revealing internal server file system details.
- ETag value may contain inode informationThe ETag response header contains a value that appears to embed inode numbers from the server filesystem.
- Server-Timing header exposes internal metricsThe Server-Timing response header reveals internal performance metrics such as database query times, cache status, or backend service timings.
- External script loaded without Subresource IntegrityA script or stylesheet is loaded from an external origin without a Subresource Integrity (SRI) hash. Note: SRI is impractical for continuously-updated third-party vendor scripts (analytics, ads, payment SDKs), which is why the overwhelming majority of production sites, including large, security-conscious ones, don't use it for those; it's most actionable for pinned, versioned static library includes.
- External stylesheet without SRIA CSS stylesheet loaded from a third-party CDN does not have a Subresource Integrity hash. Note: SRI is impractical for continuously-updated third-party CSS (Google Fonts, Bootstrap CDN, and similar font/framework providers), which is why most production sites, including security-conscious ones, don't use it for those; it's most actionable for pinned, versioned stylesheet includes.
- Frame-busting relies on header only without JS fallbackClickjacking protection is provided by HTTP header only, without a JavaScript frame-busting script for older browsers.
- Referrer-Policy not set to strict-origin-when-cross-originThe Referrer-Policy header is absent or not set to a strict value, potentially leaking full URL referrers to cross-origin destinations.
- Meta refresh redirect with empty content or empty URL targetA meta refresh tag has an empty content attribute, or a url= parameter present with no target after it. This does not include a plain interval-only self-refresh (e.g. content="30"), which is a valid, common idiom for auto-reloading dashboards and status pages and is not flagged.
- Image URL uses protocol-relative scheme (//)An image source uses a protocol-relative URL (//example.com/image.jpg) that inherits the page protocol.
- OpenGraph image URL is not HTTPSThe og:image meta tag uses an HTTP URL, which may cause browsers and social platforms to block the image.
- HTML DOCTYPE declaration is missingThe page does not start with a DOCTYPE declaration, triggering quirks mode in some browsers.
- Reverse Tabnabbing: target=_blank without rel=noopenerAnchor tags use target="_blank" without rel="noopener". Since Chrome 88 and Firefox 79, browsers implicitly apply noopener behavior to <a target="_blank"> links by default, so the practical risk on modern browsers is low; this is now mainly a defense-in-depth / older-browser recommendation rather than an active vulnerability.
- Third-party iframe without sandbox attributeAn iframe embedding third-party content does not use the sandbox attribute. Note: this fires on any cross-origin iframe, including common, legitimate embeds (YouTube, Google Maps, payment SDKs, chat widgets) that routinely omit sandbox because it would break their required functionality.
- Missing X-Permitted-Cross-Domain-Policies headerThe server does not send X-Permitted-Cross-Domain-Policies: none, so legacy plugins (Adobe Flash, Acrobat Reader) fall back to permissive cross-domain policy discovery.
- Cross-Origin-Opener-Policy Explicitly Set to unsafe-noneThe Cross-Origin-Opener-Policy header is explicitly set to 'unsafe-none', which opts the page out of browsing-context isolation.
- CSP report-to Group Has No Reporting-Endpoints DefinitionThe CSP references a 'report-to' group name, but the response does not define that group via a Reporting-Endpoints header.
- Reporting-Endpoints Defines a Plaintext HTTP EndpointThe Reporting-Endpoints header defines one or more report delivery URLs using http:// instead of https://.
- CORS Reflects Origin Without Vary: OriginAccess-Control-Allow-Origin echoes back a specific origin and the response is otherwise cacheable, but there is no Vary: Origin header telling shared caches that the body differs per requesting origin.
Info50 checks
- Missing Cross-Origin-Resource-Policy (CORP)No Cross-Origin-Resource-Policy header is set.
- CSP Contains Framework-Required DirectivesThe CSP includes directives required by the frontend framework. This is expected for Next.js, React, Vue, or Angular applications.
- DNS Prefetch Explicitly EnabledX-DNS-Prefetch-Control is set to 'on', leaking which links exist on the page.
- Script Relies on Cross-Origin Isolation That COEP PreventsAn inline script branches on cross-origin isolation, by reading window.crossOriginIsolated or waiting on Atomics, but Cross-Origin-Embedder-Policy is set to a value that keeps isolation off, so that flag is permanently false and the branch behind it never runs.
- CSP Uses Deprecated report-uriCSP uses the deprecated 'report-uri' directive without the modern 'report-to' directive.
- CSP script-src Too RestrictiveCSP script-src only allows 'self'.
- Legacy Pragma Header UsedPragma: no-cache header present.
- Expires Header Set to PastExpires header set to date in the past.
- Missing Cross-Origin-Opener-Policy (COOP) HeaderNo Cross-Origin-Opener-Policy header is set. The detector checks for the real, enforcing header, not the optional Report-Only preview variant.
- Missing <meta charset> DeclarationThe HTML document does not declare a character set via <meta charset>. Without an explicit charset, older browsers could be tricked into an encoding (e.g. UTF-7) that enables reflected content to execute as script.
- Permissions-Policy geolocation allowedGeolocation should default to 'self' unless your app needs it.
- Permissions-Policy grants camera to every originThe policy grants camera to every origin (camera=*), which includes any third party the page embeds in an iframe. Granting it to the page's own origin, restricting it to an allowlist, or blocking it outright is not reported.
- Permissions-Policy microphone allowedMicrophone should default to 'self' or be blocked.
- Permissions-Policy payment allowedPayment Request API should default to 'self'.
- Permissions-Policy USB allowedWebUSB should default to 'self'.
- Permissions-Policy bluetooth allowedWeb Bluetooth should default to 'self'.
- Permissions-Policy serial allowedWeb Serial should default to 'self'.
- Permissions-Policy wake-lock allowedWake Lock should default to 'self'.
- Permissions-Policy publickey-credentials-get allowedPasskey / WebAuthn should default to 'self'.
- Permissions-Policy unload allowedPermissions-Policy: unload=() is recommended to prevent third parties from intercepting the page-unload event.
- Permissions-Policy clipboard-read allowedPermissions-Policy does not restrict the clipboard-read feature.
- Permissions-Policy clipboard-write allowedPermissions-Policy does not restrict the clipboard-write feature.
- Permissions-Policy accelerometer allowedPermissions-Policy does not restrict the accelerometer sensor.
- Permissions-Policy gyroscope allowedPermissions-Policy does not restrict the gyroscope sensor.
- Permissions-Policy magnetometer allowedPermissions-Policy does not restrict the magnetometer sensor.
- Permissions-Policy ambient-light-sensor allowedPermissions-Policy does not restrict the ambient-light-sensor feature.
- Permissions-Policy display-capture allowedPermissions-Policy does not restrict display-capture (screen capture).
- Permissions-Policy grants fullscreen to every originThe policy grants fullscreen to every origin (fullscreen=*), which includes any third party the page embeds in an iframe. A site using fullscreen itself is not reported.
- Permissions-Policy midi allowedPermissions-Policy does not restrict Web MIDI access.
- Permissions-Policy picture-in-picture allowedPermissions-Policy does not restrict the picture-in-picture feature.
- Permissions-Policy storage-access allowedPermissions-Policy does not restrict the Storage Access API used by third-party iframes.
- Permissions-Policy window-management allowedPermissions-Policy does not restrict the Window Management API for multi-screen layouts.
- Missing Cross-Origin-Embedder-Policy headerThe response lacks a Cross-Origin-Embedder-Policy (COEP) header, which is required for cross-origin isolation.
- NEL header not configuredNetwork Error Logging is not configured via the NEL header, preventing automatic collection of network-level failures.
- Deprecated Feature-Policy header in useThe Feature-Policy header is present. This header has been replaced by Permissions-Policy.
- X-Request-Id header exposed to clientsThe X-Request-Id header is returned in the response and exposes internal request tracking identifiers.
- Age header reveals CDN cache ageThe Age header is present and reveals how long the response has been cached at a CDN or proxy.
- X-Amz-Request-Id reveals AWS infrastructureThe X-Amz-Request-Id header is present, revealing that the response is served from AWS infrastructure.
- Cloudflare CF-Ray request identifier presentThe Cloudflare CF-Ray response header exposes the request identifier that Cloudflare assigns to every proxied request.
- X-Vercel-Id reveals deployment platformThe X-Vercel-Id header is present and reveals the application is hosted on Vercel.
- X-Cache header reveals CDN cache statusThe X-Cache header (e.g., X-Cache: HIT or MISS) is present and reveals CDN caching details.
- Server Date header shows clock skewThe Date response header shows a time significantly different from the current time, indicating a misconfigured server clock.
- Username field missing autocomplete="username"A username or login field does not specify autocomplete="username", hindering password manager autofill.
- Excessive inline style attributesThe page contains 3 or more HTML elements with inline style attributes, which CSP cannot inspect and which complicate theming.
- Missing Origin-Agent-Cluster headerThe server does not send Origin-Agent-Cluster: ?1, so the browser may place this page in a shared, document.domain-relaxable agent cluster instead of an origin-isolated one.
- Permissions-Policy Browsing-Topics allowedPermissions-Policy does not block the browsing-topics directive, leaving Chrome's Privacy Sandbox Topics API available to any script on the page.
- Permissions-Policy interest-cohort allowedPermissions-Policy does not block the legacy interest-cohort directive (FLoC).
- Permissions-Policy attribution-reporting allowedPermissions-Policy does not block the attribution-reporting directive, leaving the Privacy Sandbox Attribution Reporting API available to any script on the page.
- Permissions-Policy otp-credentials allowedPermissions-Policy does not restrict the otp-credentials directive (WebOTP API), leaving SMS OTP auto-fill available to any embedded frame by default.
- Origin-Agent-Cluster Has an Invalid ValueThe Origin-Agent-Cluster header is present but set to a value other than the two the spec defines, '?1' or '?0', so browsers discard it and treat the header as if it were never sent.
About the Headers checks
- What does the Headers category check?
- Check a site's HTTP response headers: Content-Security-Policy, HSTS, X-Frame-Options, referrer and permissions policy, and the dozens of value-level mistakes that weaken each one. CSP, HSTS, X-Frame-Options, referrer policy, permissions policy.
- How many headers checks are there?
- VulnRadar runs 133 checks in this category, ranging across high, medium, low, info severity.
- Do I need to install anything to run the headers checks?
- No. Paste a URL in the browser or call the REST API, and the scan itself runs from our servers against that URL. There is no agent and no appliance to deploy alongside your application. A browser extension exists if you want to scan the page you are looking at, but nothing has to be installed to use this.
Run the headers checks on your site
VulnRadar runs all 133 of these against a URL in seconds, with the evidence and fix for every finding. No agent to install, just paste a URL.