HTTP Headers: doc.gov

Cache-Control
Connection
Content-Encoding
Content-Language
Content-Length
Content-Security-Policy
Content-Type
Date
Expect-CT
Expires
Permissions-Policy
Referrer-Policy
Server
Strict-Transport-Security
Vary
Via
X-Amz-Cf-Id
X-Amz-Cf-Pop
X-Cache
X-Content-Type-Options
X-Fastcgi-Cache
X-Frame-Options
X-Permitted-Cross-Domain-Policies
X-Robots-Tag
X-UA-Compatible
X-XSS-Protection

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.

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