HTTP headers
HTTP /api/v1/http/headersCapture every response header, follow redirects, time each hop.
https://www.githubstatus.com/
200
2 hops
346 ms
Redirect chain
-
301
https://status.github.com277 ms -
200
https://www.githubstatus.com/49 ms
Final response headers (30)
| content-type | text/html; charset=utf-8 |
| date | Tue, 15 Sep 2026 23:46:03 GMT |
| x-download-options | noopen |
| x-permitted-cross-domain-policies | none |
| referrer-policy | strict-origin-when-cross-origin |
| x-statuspage-version | 2563013abdbd53c189dd67cfefa343497901ce12 |
| strict-transport-security | max-age=259200 |
| x-statuspage-skip-logging | true |
| access-control-allow-origin | * |
| cache-control | max-age=10, public, s-maxage=10, stale-while-revalidate=20, stale-if-error=3600 |
| link | <https://dka575ofm4ao0.cloudfront.net/assets/register_subscription_form-589b657fec607087fc5c740c568270907310bc4f6aaa20256e70f01b103025ca.js>; rel=preload; as=script; nopush,<https://dka575ofm4ao0.cloudfront.net/assets/status_common-a86dffb81955091741c3de8bded6ce66ae0c6d8f736b57b580f853d9f892727e.js>; rel=preload; as=script; nopush,<https://dka575ofm4ao0.cloudfront.net/packs/0.6d587e2c8ae0df459ecd.css>; rel=preload; as=style; nopush,<https://dka575ofm4ao0.cloudfront.net/assets/status/status_manifest-3975cac43f498cd81d991d1abc986307c014f9c6ec29a9abfeb3b0882674850a.css>; rel=preload; as=style; nopush,<https://dka575ofm4ao0.cloudfront.net/assets/jquery-3.5.1.min-729e416557a365062a8a20f0562f18aa171da57298005d392312670c706c68de.js>; rel=preload; as=script; nopush,<https://dka575ofm4ao0.cloudfront.net/assets/status_manifest-9446cbd3af4b0e3706e85200ffeb5f09d6410458c7aea582354bfd4bc5546b5e.js>; rel=preload; as=script; nopush,<https://dka575ofm4ao0.cloudfront.net/packs/common-3e6e8c878eea26f45b29.chunk.js>; rel=preload; as=script; nopush,<https://dka575ofm4ao0.cloudfront.net/packs/globals-f12471d5e878ec0f0705.chunk.js>; rel=preload; as=script; nopush,<https://dka575ofm4ao0.cloudfront.net/packs/runtime-33399279767e29d9b814.js>; rel=preload; as=script; nopush |
| x-pollinator-metadata-service | status-page-web-pages |
| etag | W/"aaf04eb58191772eb76dc431fabecb1d" |
| x-runtime | 0.106885 |
| server | AtlassianEdge |
| accept-ranges | bytes |
| x-content-type-options | nosniff |
| x-xss-protection | 1; mode=block |
| atl-traceid | 4a7d52eaedbc4b038f8661b01e9d8e73 |
| atl-request-id | 4a7d52ea-edbc-4b03-8f86-61b01e9d8e73 |
| report-to | {"endpoints": [{"url": "https://dz8aopenkvv6s.cloudfront.net"}], "group": "endpoint-1", "include_subdomains": true, "max_age": 600} |
| nel | {"failure_fraction": 0.01, "include_subdomains": true, "max_age": 600, "report_to": "endpoint-1"} |
| content-encoding | br |
| vary | Accept,Accept-Encoding |
| x-cache | Hit from cloudfront |
| via | 1.1 a408ef2823875a1f800dc5334ac0cbae.cloudfront.net (CloudFront) |
| x-amz-cf-pop | AMS56-P1 |
| alt-svc | h3=":443"; ma=86400 |
| x-amz-cf-id | QuZeJj1IcEKPv0bF60Qe53S_1sSphLLUuZksZV_lOmjbf-_QKGo3Lw== |
| age | 4 |
Tech stack
HTTP/3 (QUIC)
Between content blocks · 728x90 ·
advertise here
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%2Fstatus.github.com
curl -s '/api/v1/http/headers?q=https%3A%2F%2Fstatus.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.
Related tools
More in HTTP
Sidebar — skyscraper · 160x600 ·
advertise here
Between content (square) · 300x250 ·
advertise here
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