developers.googleblog.com | Analytics by SecurityHeaders

HTTP Headers report for developers.googleblog.com

Header Name Header Data
HTTP status code 200
Content-Security-Policy base-uri 'self'; object-src 'none'; script-src 'strict-dynamic' http: https: 'nonce-TN6gTJr5smfCPp6eMON8TQ==' *.google-analytics.com *.googletagmanager.com *.gstatic.com *.youtube.com *.googleapis.com
Cross-Origin-Opener-Policy same-origin
X-Frame-Options DENY
X-Content-Type-Options nosniff
Content-Language en
X-Cloud-Trace-Context 653b426494340fa74fb63b5f4f7a21fe
Alt-Svc h3=":443"; ma=2592000,h3-29=":443"; ma=2592000
Content-Type text/html; charset=utf-8
Vary Accept-Encoding
Strict-Transport-Security max-age=2592000; includeSubdomains
X-Xss-Protection 1; mode=block
Referrer-Policy same-origin
Date Thu, 17 Apr 2025 12:18:56 GMT
Server Google Frontend

About the tool

By using SecurityHeaders.info, you can quickly identify missing or misconfigured headers and take steps to secure your website, improving both security and user confidence.

This tool is widely used by developers, security professionals, and organizations to ensure their websites adhere to best practices in web security.

We also have another analytic tool that is used for identifying popularity metrics, general information about the business, finding similar products and competitors, and much more.

Watch it now at TrustRadar