Fetch Website Response Headers
Fetch a URL's HTTP response headers server-side (use HEAD, fall back to GET). Process: send HEAD, follow redirects, collect headers, block private hosts. Example: inspect CORS, Cache-Control, and Strict-Transport-Security headers to debug redirects and CDN settings.
-
Notes
- Some sites do not support HEAD; we will fall back to GET.
- For safety, requests to localhost/private networks are blocked.
What: Fetch and inspect a website's HTTP response headers. Useful for debugging CORS, caching, redirects and verifying security or CDN headers. Scenarios: developer debugging, SEO checks, and verifying server configuration.
Frequently asked questions
What do HTTP response headers show?
They show metadata from the server response such as content type, caching rules, redirects, and security policies like HSTS or CORS.
Does this tool download the full page body?
It prefers HEAD and falls back to GET when needed. The goal is inspecting headers, not scraping page content.
Why are localhost or private IPs blocked?
Requests to private networks are blocked for safety so the worker cannot be used to probe internal hosts.