HTTP Headers: gitlab.co

Security score: 0/100

🛡️ Security Headers

Header	Status
Strict-Transport-Security	❌ Missing
Content-Security-Policy	❌ Missing
X-Content-Type-Options	❌ Missing
X-Frame-Options	❌ Missing
X-XSS-Protection	❌ Missing

📋 All Response Headers

Date
Content-Type
Connection
CF-Ray
CF-Cache-Status
x-guploader-uploadid
Age
Cache-Control
Expires
Last-Modified
Server
Strict-Transport-Security
Vary
alt-svc
x-goog-generation
x-goog-hash
x-goog-metageneration
x-goog-storage-class
x-goog-stored-content-encoding
x-goog-stored-content-length
Content-Encoding

ℹ️ About HTTP Security Headers

Strict-Transport-Security (HSTS) forces browsers to use HTTPS. Content-Security-Policy (CSP) prevents XSS attacks by controlling which resources can load. X-Content-Type-Options stops MIME-type sniffing. X-Frame-Options blocks clickjacking by preventing iframe embedding.

gitlab.co's security score of 0/100 reflects how many of these protective headers are configured. Higher scores indicate better defense against common web attacks.

🔧 More Tools for Gitlab

📊 Full Analysis 📋 WHOIS Lookup 🌐 DNS Records 🔒 SSL Certificate ⬆️ Uptime Status 📑 Full Report