HTTP headers
HTTP /api/v1/http/headersCapture every response header, follow redirects, time each hop.
https://www.google.com/
200
2 hops
141 ms
Redirect chain
-
301
https://services.google.com26 ms -
200
https://www.google.com/58 ms
Final response headers (14)
| content-type | text/html; charset=UTF-8 |
| date | Tue, 15 Sep 2026 23:21:42 GMT |
| expires | -1 |
| cache-control | private, max-age=0 |
| content-security-policy-report-only | object-src 'none';base-uri 'self';script-src 'nonce-q9O9xXuXYdC3oei--13p5w' 'strict-dynamic' 'report-sample' 'unsafe-eval' 'unsafe-inline' https: http:;report-uri https://csp.withgoogle.com/csp/gws/other-hp |
| accept-ch | Sec-CH-Prefers-Color-Scheme |
| p3p | CP="This is not a P3P policy! See g.co/p3phelp for more info." |
| content-encoding | gzip |
| server | gws |
| content-length | 31357 |
| x-xss-protection | 0 |
| x-frame-options | SAMEORIGIN |
| set-cookie | SOCS=CAAaBgiAlaLVBg; expires=Fri, 15-Oct-2027 23:21:42 GMT; path=/; domain=.google.com; Secure; SameSite=lax, AEC=AdJVEavG8MC-Z4G0ch_DUeTfrY3dFMQzY37G3WP-hSXMmFc-u8WW2HRnVg; expires=Sun, 14-Mar-2027 23:21:42 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax, __Secure-ENID=CpYCCAISyAEBAQxeRbKk9_3XZyncMRIqfS6PvE73uBa_-UXvM_815YNOzrXHLVEFaF7RvtNYJfrdkzMzTNzhgsYK6VzGK77guFNZxPPC2sxZUJIscCXUYVgKhSrSI8Yvq2GqnLK2SN4gDCENYKQYOFiDBiFZq0O5wzuUwwr1HIBePDkmmPhY0wztnb4t24ABkChEmhOTJur5iAffxwGk4U-De0lvLUPRELNwC9ed0edIlnLGuIE58PVcVnDFDbvKerzLak_689uJuGr5S1F_4ygCMkUBfWzEquXzIO-5K3FfzjVdO-LCqcf1fmpjUF3NREyRsQJi3kc5QIoftrhYK-YzIky6ZMFPFDDD_SgGzeJ1toQtZ4pwgws; expires=Sat, 16-Oct-2027 15:40:00 GMT; path=/; domain=.google.com; Secure; HttpOnly; SameSite=lax |
| alt-svc | h3=":443"; ma=2592000,h3-29=":443"; ma=2592000 |
Tech stack
HTTP/3 (QUIC)
How to use HTTP headers
-
1
Paste your input
Enter the value at the top — domain, IP, URL, email, ASN, hash, whatever fits this tool. The smart input auto-detects type.
-
2
Click "Inspect"
host.tools issues real probes (DNS, HTTP, TCP, TLS, WHOIS where applicable) and renders the result in milliseconds.
-
3
Open the API tab
Every web tool has a sibling /api/v1/http/headers JSON endpoint with the same payload. One copy-as-curl click and you're scripting it.
Why this matters
Headers are how the modern web declares its security posture. Auditing them is the highest-ROI thing you can do this week.
API equivalent
/api/v1/http/headers?q=services.google.com
curl -s '/api/v1/http/headers?q=services.google.com'
Embed this tool
<iframe src="/http/headers?q={INPUT}&embed=1"
width="100%" height="600" frameborder="0"></iframe>
Drop into any HTML page. The embed=1 flag hides nav and footer.
FAQ · HTTP headers
Common questions
Is HTTP headers free?
Yes — every tool is free on the web with a 200/hour rate limit per IP. The matching API endpoint /api/v1/http/headers is free up to 100 requests/hour, no key required.
Where does the data come from?
Real-time probes against authoritative sources (DNS root, RIRs, registries, the target server itself), plus partner data feeds from hostinfo.com (GeoIP/ASN) and hostcheck.com (reputation).
How fresh are the results?
Live by default. Cached for 5 minutes to make repeat queries instant; pass
?nocache=1 for a forced refresh.Can I run this from the command line?
Yes — every tool ships with a copy-as-curl. There's also an official CLI:
host.tools http headers YOUR_INPUT.Can I monitor results over time?
Pro tier lets you schedule any tool to run every 1/5/15/60 min and alert on diff. See monitors.
host.tools Pro
Run HTTP headers on a schedule. Get pinged when it changes.
Pro gets you bulk lookups, monitors, webhook alerts, history, exports and 10,000 API calls/day. $19/mo.
- ✓Schedule any tool — every 1, 5, 15, 60 min
- ✓Diff against last run, alert on change
- ✓Webhook + email + Slack + PagerDuty + OpsGenie
- ✓Bulk CSV upload, 1,000 inputs per job
- ✓Export results as CSV / NDJSON / Excel
- ✓90-day history, comparison view