HTTP Headers of render.github.com: Response & Security Headers | OrbitProbe

HTTP headers of render.github.com

Add to portfolio Watch for changes Open full report

Security headers

strict-transport-security: Missing
content-security-policy: Missing
x-content-type-options: Present
nosniff
x-frame-options: Not set (optional)
referrer-policy: Not set (optional)
permissions-policy: Not set (optional)

This is a presence check on one response. A present header does not prove its policy is strict, and other pages of the site may answer differently.

All response headers

404 · https://render.githubusercontent.com/

Header	Value
content-type	text/plain; charset=utf-8
vary	Accept-Encoding
x-content-type-options	nosniff
date	Sun, 20 Sep 2026 23:05:03 GMT
content-length	19
x-github-backend	Kubernetes
x-github-request-id	9810:39FA0:615BD2B:7A44CFA:6AB0669F
x-github-edge-region	iad
server	github.com
connection	close

What this tool shows

OrbitProbe requests the home page over HTTPS, follows redirects and lists the headers of the final response exactly as the server sent them. Headers are how a server tells browsers and caches what to do: how long to keep a copy, whether the page may be framed, which scripts may run, and that the site must only be reached over HTTPS.

Cookie values are never displayed. A Set-Cookie header can carry a session identifier, so only the cookie name and its attributes (Secure, HttpOnly, SameSite, expiry) are shown. Those attributes are the part worth reviewing anyway.

HTTP header checker