'humble' (HTTP Headers Analyzer)
https://github.com/rfc-st/humble | v.2024-11-16
[0. Info]
Date : 2024/11/16 - 20:05:16
URL : https://facebook.com
File : humble_https_facebook_com_20241116_200517_en.html
Note : The URL returns an error (HTTP code 400, 'Bad Request')
Ref : https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
[1. Enabled HTTP Security Headers]
Cache-Control:private, no-cache, no-store, must-revalidate
Content-Security-Policy:default-src data: blob: 'self' https://*.fbsbx.com *.facebook.com *.fbcdn.net;script-src *.facebook.com *.fbcdn.net 'unsafe-inline' blob: data: 'self' 'wasm-unsafe-eval';style-src *.fbcdn.net data: *.facebook.com 'unsafe-inline';connect-src *.facebook.com facebook.com *.fbcdn.net wss://*.facebook.com:* wss://*.fbcdn.net attachment.fbsbx.com blob: *.cdninstagram.com 'self' http://localhost:3103 wss://gateway.facebook.com wss://edge-chat.facebook.com wss://snaptu-d.facebook.com wss://kaios-d.facebook.com/ *.fbsbx.com;font-src data: *.facebook.com *.fbcdn.net *.fbsbx.com;img-src *.fbcdn.net *.facebook.com data: https://*.fbsbx.com facebook.com *.cdninstagram.com fbsbx.com fbcdn.net blob: android-webview-video-poster: *.oculuscdn.com https://paywithmybank.com/ https://*.paywithmybank.com/;media-src *.cdninstagram.com blob: *.fbcdn.net *.fbsbx.com www.facebook.com *.facebook.com data:;frame-src *.facebook.com *.fbsbx.com fbsbx.com data: *.fbcdn.net https://paywithmybank.com/ https://*.paywithmybank.com/;worker-src blob: *.facebook.com data:;block-all-mixed-content;upgrade-insecure-requests;report-uri https://www.facebook.com/csp/reporting/?m=c&minimize=0;
Content-Type:text/html; charset="utf-8"
Cross-Origin-Opener-Policy:same-origin-allow-popups
Strict-Transport-Security:max-age=15552000; preload
X-Content-Type-Options:nosniff
X-Frame-Options:DENY
[2. Missing HTTP Security Headers]
Clear-Site-Data
Clears browsing data (cookies, storage, cache) associated with the requesting website.
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Clear-Site-Data
Cross-Origin-Embedder-Policy
Prevents documents and workers from loading non-same-origin requests unless allowed.
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Cross-Origin-Embedder-Policy
Cross-Origin-Resource-Policy
Protect servers against certain cross-origin or cross-site embedding of the returned source.
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Cross-Origin_Resource_Policy_(CORP)
(*) NEL
Enables web applications to declare a reporting policy to report errors.
Ref: https://scotthelme.co.uk/network-error-logging-deep-dive/
(*) Permissions-Policy
Previously called "Feature-Policy", allow and deny the use of browser features.
Ref: https://scotthelme.co.uk/goodbye-feature-policy-and-hello-permissions-policy/
Referrer-Policy
Controls how much referrer information should be included with requests.
Ref: https://scotthelme.co.uk/a-new-security-header-referrer-policy/
X-Permitted-Cross-Domain-Policies
Limit which data external resources (e.g. Adobe Flash/PDF documents), can access on the domain.
Ref: https://owasp.org/www-project-secure-headers/#div-headers
[3. Fingerprint HTTP Response Headers]
These headers can leak information about software, versions, hostnames or IP addresses:
X-FB-Debug [facebook.com Platform]
Value: 'Mc5EeqU5XiZhQ3CR+zMc/AMdqsopEWF6PIrawTtrXYovR4a/LVE24IEQdSh1yJnBq2BJUeURR+haaoW+mo3nZA=='
[4. Deprecated HTTP Response Headers/Protocols and Insecure Values]
The following headers/protocols are deprecated or their values may be considered unsafe:
Content-Security-Policy (Deprecated Directives)
Avoid using deprecated directives: 'report-uri', 'block-all-mixed-content'
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Content-Security-Policy
Content-Security-Policy (Insecure Schemes)
Do not allow insecure, unencrypted schemes: 'http:'
Ref: https://www.cloudflare.com/learning/ssl/why-is-http-not-secure/
Ref: https://http.dev/wss
Content-Security-Policy (Too Permissive Sources)
Limit these permissive origins: 'blob:', 'data:'
Ref: https://content-security-policy.com/
Content-Security-Policy (Unsafe Values)
'unsafe-inline' and 'unsafe-eval' negate most of the security benefits provided by this header.
Ref: https://csper.io/blog/no-more-unsafe-inline
Ref: https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Global_Objects/eval
Pragma (Deprecated Header)
This header is deprecated.
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Pragma
Report-To (Deprecated Header)
This header is deprecated. Use instead "Reporting-Endpoints".
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Report-To
Strict-Transport-Security (Recommended Values)
Add 'includeSubDomains' and 'max-age' (with 31536000 -one year- as minimum).
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security
Ref: https://https.cio.gov/hsts/
Strict-Transport-Security (Required Values)
'preload' requires 'includeSubDomains' and 'max-age' (with 31536000 -one year- as minimum).
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Strict-Transport-Security
Vary (Potentially Unsafe Header)
The values of this header may expose others, facilitating attacks if user input is accepted.
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/Vary
Ref: https://www.yeswehack.com/fr/learn-bug-bounty/http-header-exploitation
X-XSS-Protection (Deprecated Header)
This header is deprecated in the three major web browsers.
Instead, use the "Content-Security-Policy" header restrictively.
Ref: https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/X-XSS-Protection
[5. Empty HTTP Response Headers Values]
Empty HTTP headers (and are therefore considered disabled):
Nothing to report, all seems OK!
[6. Browser Compatibility for Enabled HTTP Security Headers]
https://caniuse.com/?search=Cache-Control
https://caniuse.com/?search=contentsecuritypolicy2
https://caniuse.com/?search=Content-Type
https://caniuse.com/?search=Cross-Origin-Opener-Policy
https://caniuse.com/?search=Origin-Agent-Cluster
https://caniuse.com/?search=Reporting-Endpoints
https://caniuse.com/?search=Strict-Transport-Security
https://caniuse.com/?search=Vary
https://caniuse.com/?search=X-Content-Type-Options
https://caniuse.com/?search=X-Frame-Options
https://caniuse.com/?search=X-XSS-Protection
[7. Analysis Results]
Done in 0.55 seconds! (changes with respect to the last analysis in parentheses)
Missing headers: 7 (0)
Fingerprint headers: 1 (0)
Deprecated/Insecure headers: 10 (0)
Empty headers: 0 (0)
Findings to review: 18 (0)
Analysis Grade: D (Review 'Deprecated/Insecure headers')
'(*)' meaning: Experimental HTTP response header
'(*)' ref: https://mdn.io/Experimental_deprecated_obsolete