This page validates the HTTP security headers returned by gitlab.com, scoring its protection against common web attacks.
Below you can review which headers gitlab.com sends, which are missing, and recommendations to harden the configuration.
HTTP security headers are response headers that instruct the browser to apply protective policies, mitigating attacks such as XSS, clickjacking and content sniffing.
Key headers include Content-Security-Policy (CSP), Strict-Transport-Security (HSTS), X-Frame-Options, X-Content-Type-Options and Referrer-Policy.
A higher score means gitlab.com sends more of the recommended security headers with secure values. Missing headers are highlighted so you know what to add.
Focus first on CSP and HSTS for gitlab.com, as they provide the strongest protection against scripting and downgrade attacks.
This page lists the HTTP security headers present on gitlab.com, such as CSP, HSTS, X-Frame-Options and X-Content-Type-Options, along with their values.
The results show whether gitlab.com sends a Content-Security-Policy header and whether its value is considered secure.
The Strict-Transport-Security section indicates whether gitlab.com forces HTTPS and for how long, including includeSubDomains and preload flags.
A low score means gitlab.com is missing important headers or sends insecure values. The missing-headers and recommendations sections explain how to improve it.
Yes. The XploreNetHub Security Headers Validator is completely free, requires no sign-up and runs directly in your browser.