HTTP headers
HTTP /api/v1/http/headersCapture every response header, follow redirects, time each hop.
https://auth.services.adobe.com/en_US/deeplink.html?deeplink=ssofirst&callback=https%3A%2F%2Fims-na1.adobelogin.com%2Fims%2Fadobeid%2FCampaign1%2FAdobeID%2Fcode%3Fredirect_uri%3Dhttps%253A%252F%252Fadobe.com%26code_challenge_method%3Dplain%26use_ms_for_expiry%3Dtrue&client_id=Campaign1&scope=AdobeID%2Cperson%2Csession%2Cadditional_info.projectedProductContext%2Cread_organizations%2Cadditional_info.user_image_url%2Cwrite_pc%2Caudiencemanager_api%2Copenid%2Ctriggers&relay=691e6e11-d90e-461d-b55d-b6d4fb1181b7&locale=en_US&flow_type=code&idp_flow_type=login&s_p=google%2Cfacebook%2Capple%2Cmicrosoft%2Cline%2Ckakao&response_type=code&code_challenge_method=plain&redirect_uri=https%3A%2F%2Fadobe.com&use_ms_for_expiry=true
200
4 hops
1195 ms
Redirect chain
-
302
https://t.communication.github.com332 ms -
302
https://t.communication.github.com/xtk/logon.jssp302 ms -
302
https://adobeid-na1.services.adobe.com/ims/authorize/v1?client_id=Campaign1&scope=AdobeID%2Cperson%2Csession%2Cadditional_info.projectedProductContext%2Cread_organizations%2Cadditional_info.user_image_url%2Cwrite_pc%2Caudiencemanager_api%2Copenid%2Ctriggers&response_type=code&redirect_uri=https%3A%2F%2Ft.communication.github.com%2Fxtk%2Flogon.jssp131 ms -
200
https://auth.services.adobe.com/en_US/deeplink.html?deeplink=ssofirst&callback=https%3A%2F%2Fims-na1.adobelogin.com%2Fims%2Fadobeid%2FCampaign1%2FAdobeID%2Fcode%3Fredirect_uri%3Dhttps%253A%252F%252Fadobe.com%26code_challenge_method%3Dplain%26use_ms_for_expiry%3Dtrue&client_id=Campaign1&scope=AdobeID%2Cperson%2Csession%2Cadditional_info.projectedProductContext%2Cread_organizations%2Cadditional_info.user_image_url%2Cwrite_pc%2Caudiencemanager_api%2Copenid%2Ctriggers&relay=691e6e11-d90e-461d-b55d-b6d4fb1181b7&locale=en_US&flow_type=code&idp_flow_type=login&s_p=google%2Cfacebook%2Capple%2Cmicrosoft%2Cline%2Ckakao&response_type=code&code_challenge_method=plain&redirect_uri=https%3A%2F%2Fadobe.com&use_ms_for_expiry=true138 ms
Final response headers (27)
| date | Tue, 15 Sep 2026 23:46:34 GMT |
| content-type | text/html |
| last-modified | Tue, 15 Sep 2026 13:14:10 GMT |
| server | cloudflare |
| x-amz-server-side-encryption | AES256 |
| x-amz-version-id | wFbIfBTMBBcNDrNAPf8WmHvG5ovyEmih |
| cache-control | no-cache |
| etag | W/"382a0b56b84489dd3a7582a3e8117e76" |
| vary | Accept-Encoding |
| x-cache | RefreshHit from cloudfront |
| via | 1.1 227c5509baa8ef8a38bee5b966636346.cloudfront.net (CloudFront) |
| x-amz-cf-pop | AMS56-P1 |
| alt-svc | h3=":443"; ma=86400 |
| x-amz-cf-id | zaG9oFU0Q6uRVHyCEHHKngf0abPz4l8SjXzpG2r-JrSW68LXAKAwCg== |
| x-xss-protection | 1; mode=block |
| x-frame-options | DENY |
| referrer-policy | no-referrer-when-downgrade |
| content-security-policy | report-uri https://auth.services.adobe.com/signin/v1/audit/csp-violation-report; report-to report_api |
| x-content-type-options | nosniff |
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| cross-origin-opener-policy-report-only | restrict-properties; report-to="report_api" |
| report-to | {"group":"report_api","max_age":2592000,"endpoints":[{"url":"https://auth.services.adobe.com/signin/v1/audit/report"}]} |
| reporting-endpoints | report_api="https://auth.services.adobe.com/signin/v1/audit/report" |
| x-robots-tag | noindex |
| cf-cache-status | DYNAMIC |
| content-encoding | br |
| cf-ray | a3bb82f33d620adc-AMS |
Tech stack
CloudflareHTTP/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=https%3A%2F%2Ft.communication.github.com
curl -s '/api/v1/http/headers?q=https%3A%2F%2Ft.communication.github.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