host.tools

HTTP headers

HTTP /api/v1/http/headers

Capture every response header, follow redirects, time each hop.

Try: https://host.com https://checkhost.com https://hostinfo.com https://crypt.tools
Related: HTTP headers Security headers grader Redirect chain tracer SSL certificate inspector robots.txt parser sitemap.xml inspector
https://accounts.google.com/v3/signin/identifier?continue=https://accounts.google.com/&followup=https://accounts.google.com/&passive=1209600&flowName=WebLiteSignIn&flowEntry=ServiceLogin&dsh=S-1744507181:1789519616066093 200 3 hops 216 ms
Redirect chain
  1. 302 https://accounts.google.com 39 ms
  2. 302 https://accounts.google.com/ServiceLogin?passive=1209600&continue=https%3A%2F%2Faccounts.google.com%2F&followup=https%3A%2F%2Faccounts.google.com%2F 30 ms
  3. 200 https://accounts.google.com/v3/signin/identifier?continue=https://accounts.google.com/&followup=https://accounts.google.com/&passive=1209600&flowName=WebLiteSignIn&flowEntry=ServiceLogin&dsh=S-1744507181:1789519616066093 77 ms
Final response headers (23)
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:4kVMVwUzJ5Oo1pWvttp1h9nSWSzZEw:RxJ8TLHpWcQe1qpq; Expires=Fri, 15-Sep-2028 00:46:56 GMT; Path=/; Secure; HttpOnly; Priority=HIGH
x-auto-login realm=com.google&args=continue%3Dhttps://accounts.google.com/
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:56 GMT
strict-transport-security max-age=31536000; includeSubDomains
cross-origin-resource-policy same-site
content-security-policy script-src 'report-sample' 'nonce-AiU82rJZXMoTHda23GMqjQ' 'unsafe-inline';object-src 'none';base-uri 'self';report-uri /v3/signin/_/AccountsSignInUi/cspreport;worker-src 'self', require-trusted-types-for 'script';report-uri /v3/signin/_/AccountsSignInUi/cspreport
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=*
cross-origin-opener-policy-report-only same-origin; report-to="AccountsSignInUi"
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
reporting-endpoints default="/v3/signin/_/AccountsSignInUi/web-reports?context=eJwNw09IU3EAB_Cx_H0J67D-agtieGqBNheZURAlJXNu7vH2nL3Ql7aFA9l0exOyqJnYwSIEy8Q6RWAhFnnwIFQISg1RMyc-Z1SHgsTCEhUjD34_8Mk2th3Jtprch62mkbxh89nq7-bz3L1z0dzL7fOToov1p1PiNndwD9dfnhYNXGj7JM5weWBG-DiWmxZJthenRT6P2g3xgVdaDGG5boiSdUOU8v7MgrByKv1ZTPBm0gVTqws_S934xbfG3Wjjta9u_OO-mXLYCzzI5_W4B1m6B0t3vFjm_odevOKXQxUY5KzfFXjR5sMAZ_gLj835kGLNJuEKH_dLKOGxBgkpfnZfwnOOvpMQ5z_7ZKyyJVfGXv5bJGONy07L8PKPWhmLvMGbvKdORg43an7oHL3hR8suBTe5Oaxg6a6CZW56ryDBHRMKWt9Uop3vcSc_4sdceTAAlQceBPCaezIBPOETB6pwis_1V-ECB_9fxLBNxVuucanoLlPRy8e-qZAOXcLuHduTk32zsHwcn1XzjtZFm7RwMBTRw_q1q7FoRA9FgrUJvT4RjodizaGY5nQ4ixwnC50FjmKt0bEFG4vE5g"
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. 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. 2
    Click "Inspect"

    host.tools issues real probes (DNS, HTTP, TCP, TLS, WHOIS where applicable) and renders the result in milliseconds.

  3. 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=https%3A%2F%2Faccounts.google.com 
curl -s '/api/v1/http/headers?q=https%3A%2F%2Faccounts.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.

See pricing Tour monitors
  • ✓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