Hosting Operations
Read-onlyInspect Response Headers
You need to inspect server and security headers quickly.
Command
curl -sI https://example.comBefore you run this
System impact: Read-only. Low when scoped to the shown target.
When not to use it: Do not use headers alone to validate page content or application behavior.
Expected output
HTTP status and response headers.
System impact
Read-only. Nothing changes. The command prints response headers only.
Recovery / rollback: no state is changed.
When to use it
Use this to check redirects, server headers, cache headers, and security headers.
When not to use it
Do not use headers alone to validate page content or application behavior.
next steps
Related commands
Check HTTP to HTTPS Redirect
HTTPS worked. The plain HTTP redirect still mattered.
curl -I http://example.com
Find HTML Pages Missing from the Sitemap
A page can exist in the build but never make it into the sitemap.
find public -name '*.html' -print | sed 's#^public#https://example.com#' | while read -r url; do grep -q "$url" public/sitemap.xml || echo "$url"; done
Find Feed Links Missing from the Sitemap
Your feed can advertise URLs that the sitemap never lists.
grep -o '<link>https://example.com/[^<]*</link>' public/feed.xml | sed 's#<link>##;s#</link>##' | while read -r url; do grep -q "$url" public/sitemap.xml || echo "$url"; done
Your Site Is Not Down. DNS Might Be Lying.
The browser said the site was gone. The server was answering fine.
curl --resolve example.com:443:203.0.113.10 https://example.com/
Check the Nginx Site Symlink Target
Verify which release or document root symlink Nginx is serving before changing deploy links.
readlink -f /srv/www/example.com/current
Study mapping
Use this as independent command practice: read the notes, predict the output, then compare it with the example before using a real shell.
Independent study support only. No affiliation, endorsement, exam dumps, or real exam questions.