Help / HTTP headers
HTTP headers
Shows the HTTP headers your browser sends, or fetches any URL and shows its response headers, redirect chain and a security-header check.
How to use it
- Leave the box empty and press Fetch to see your own request headers.
- Or enter a URL to fetch it: every redirect hop is listed with its status code.
Reading the results
- Status code
- 200 OK, 301/302 redirect, 404 not found, 5xx server error.
- Redirect chain
- Each hop on the way to the final page. Long chains slow sites down.
- Strict-Transport-Security
- Makes browsers use HTTPS on future visits.
- Content-Security-Policy
- Restricts where scripts and other content may load from.
- X-Frame-Options / frame-ancestors
- Stops other sites embedding the page (clickjacking).
Examples
- http://github.com HTTP → HTTPS redirect
- example.com A simple site
From the command line
curl "https://webmaster.nexayori.com/headers?q=http%3A%2F%2Fgithub.com" curl "https://webmaster.nexayori.com/headers?q=http%3A%2F%2Fgithub.com&format=json"
| q | URL (empty = your own headers) |
| format | text, json or html |
Questions
Why can’t I check tools.nexayori.com itself?
A Cloudflare Worker can’t fetch addresses on its own domain.
Limitations
- Plain GET requests only; JavaScript and meta-refresh redirects aren’t followed.
- Up to 8 redirects.