HTTP headers
HTTP /api/v1/http/headersCapture every response header, follow redirects, time each hop.
https://accounts.google.com/v3/signin/identifier?continue=https://mail.google.com/mail/u/0/&emr=1&followup=https://mail.google.com/mail/u/0/&osid=1&passive=1209600&service=mail&flowName=WebLiteSignIn&flowEntry=ServiceLogin&dsh=S1966752698:1789519605746923
200
5 hops
229 ms
Redirect chain
-
301
https://mail.google.com24 ms -
301
https://mail.google.com/mail/25 ms -
302
https://mail.google.com/mail/u/0/40 ms -
302
https://accounts.google.com/ServiceLogin?service=mail&passive=1209600&osid=1&continue=https://mail.google.com/mail/u/0/&followup=https://mail.google.com/mail/u/0/&emr=131 ms -
200
https://accounts.google.com/v3/signin/identifier?continue=https://mail.google.com/mail/u/0/&emr=1&followup=https://mail.google.com/mail/u/0/&osid=1&passive=1209600&service=mail&flowName=WebLiteSignIn&flowEntry=ServiceLogin&dsh=S1966752698:178951960574692353 ms
Final response headers (24)
| content-type | text/html; charset=utf-8 |
| x-frame-options | DENY |
| vary | Sec-Fetch-Dest, Sec-Fetch-Mode, Sec-Fetch-Site |
| set-cookie | __Host-GAPS=1:_xZIbARK7CLIjQc_ALpWZW1cc8Lm5w:y8i6rTkFvOAY5QYH; Expires=Fri, 15-Sep-2028 00:46:45 GMT; Path=/; Secure; HttpOnly; Priority=HIGH |
| x-auto-login | realm=com.google&args=service%3Dmail%26continue%3Dhttps://mail.google.com/mail/u/0/ |
| link | <https://workspace.google.com/gmail/>; rel="canonical" |
| x-ua-compatible | IE=edge |
| cache-control | no-cache, no-store, max-age=0, must-revalidate |
| pragma | no-cache |
| expires | Mon, 01 Jan 1990 00:00:00 GMT |
| date | Wed, 16 Sep 2026 00:46:45 GMT |
| strict-transport-security | max-age=31536000; includeSubDomains |
| report-to | {"group":"AccountsSignInUi","max_age":2592000,"endpoints":[{"url":"https://csp.withgoogle.com/csp/report-to/AccountsSignInUi"}]} |
| accept-ch | Sec-CH-UA-Arch, Sec-CH-UA-Bitness, Sec-CH-UA-Full-Version, Sec-CH-UA-Full-Version-List, Sec-CH-UA-Model, Sec-CH-UA-WoW64, Sec-CH-UA-Form-Factors, Sec-CH-UA-Platform, Sec-CH-UA-Platform-Version |
| permissions-policy | ch-ua-arch=*, ch-ua-bitness=*, ch-ua-full-version=*, ch-ua-full-version-list=*, ch-ua-model=*, ch-ua-wow64=*, ch-ua-form-factors=*, ch-ua-platform=*, ch-ua-platform-version=* |
| content-security-policy | require-trusted-types-for 'script';report-uri /v3/signin/_/AccountsSignInUi/cspreport, script-src 'report-sample' 'nonce-Kh_x7ZKTkKhkZGs8hr3gYQ' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /v3/signin/_/AccountsSignInUi/cspreport;worker-src 'self' |
| cross-origin-resource-policy | same-site |
| cross-origin-opener-policy-report-only | same-origin; report-to="AccountsSignInUi" |
| reporting-endpoints | default="/v3/signin/_/AccountsSignInUi/web-reports?context=eJwNw11IU2EABuAx_V5EvFg_lk6I4VULtLnIlIRQKVlzc4ez43RRJ20LB7LpdiaoUZrYhYUo9iPVVQQWYlEXXQhaF0WtWH8uWjMyyCCx0KKNRJHeB57ct1l7co06526jbqZ4Wl99fFF_mK_mLemv8-Cn12KMtVtvxHke4nFuO_lOtHOZ6b04xPWeOeHicEFC9LG5IiFK-Kk5KV7wn56kMPQmRW0mKep4R2peGDmW-CzivNFng67fhh91dvzkc6_sGOD0gh1rPDFXD3OpAyWciTiQrTmwfMGJFZ684sR9vveoAQ85-1cD7g64MMUp_sLPProQY9Uk4RTvd0uo5dvDEu5w6LGECG_GJOhfSljNl_GXDQUytvPvchlpPlolw8nfW2Qs8T_e4G2tMnZyh-qGxqEzbvRsUXCWuwIKli8qWOHO5wqiPBRX0D_TiEG-xCN8jW9wY5EHXp667MEDHk95cJMPFDbhINdMNuEI-9abMW3yYpZP2LzY99ULadcxbM3LSccnPsDw5FtmNKt4b2uoUw34_EEtoHWfDoeCmj_oa4lqbdFAxB_u8odVq8Vabqkss5ZaKtQOy38TKMNe" |
| content-encoding | gzip |
| server | ESF |
| x-xss-protection | 0 |
| x-content-type-options | nosniff |
| 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=mail.google.com
curl -s '/api/v1/http/headers?q=mail.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