Skip to content

HTTP Headers Checker

See exactly what a web server answers: status code, headers and redirects.

This tool runs on our server, because a browser cannot send DNS queries, pings or raw network connections. Only the domain, address or URL you enter is sent; results are not stored. Privacy

Shows the status code and every HTTP response header the server sends, for each redirect step.

Report a problem

Don't include personal or sensitive information.

What happened, and what did you expect? (10–2000 characters) 0 / 2000

Your browser and system, screen size and recent error messages on this page. Never what you typed or your files. Privacy

What is sent
 

Enter a URL to see the HTTP status code and every response header the server sends: Content-Type, Cache-Control, ETag, Server, Set-Cookie, X-Robots-Tag, security headers and more. If the URL redirects, each step is shown with its own status and headers, so you can follow the whole chain to the final page.

You can make the request as desktop Chrome, an iPhone, Googlebot or curl, and use GET or HEAD. That makes it easy to spot problems that only some visitors see – such as a mobile redirect, a bot block, a wrong cache header or a missing HSTS header – without opening developer tools.

How to use the HTTP Headers Checker tool

  1. Enter the web address, for example example.com/page.
  2. Choose the user agent and method if you need to.
  3. Click Get headers.
  4. Read the headers of the final response; open earlier steps to see their headers.

Why use ToolOrca HTTP Headers Checker

  • Status code, HTTP version, server IP and response time
  • All response headers, security headers marked with 🛡️
  • Follows up to 10 redirects, each with its own headers
  • Chrome, iPhone Safari, Googlebot or curl user agent
  • GET or HEAD requests
  • Copy everything as plain text

Headers worth checking

Cache-Control and Expires decide how long browsers and CDNs keep a page. Content-Type should include the right charset. X-Robots-Tag can hide a page from search engines even when the HTML looks fine. Set-Cookie should carry Secure, HttpOnly and SameSite flags.

Security headers – Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy – are marked with a shield. For a graded report on them, use the website security checker.

Common status codes

200 OK, 301/308 permanent redirect, 302/307 temporary redirect, 304 not modified, 403 forbidden, 404 not found, 410 gone, 429 too many requests, 500 server error, 502/504 the proxy could not reach the application, 503 unavailable or maintenance.

Frequently asked questions

Why do I get a different result than in my browser?

Your browser sends cookies and is in another location. Sites may also answer bots, phones and desktops differently – try another user agent.

Can I check a URL with a port like :8080?

No, only the standard web ports 80 and 443 are allowed.

Does it download the whole page?

No. It reads the headers and discards the body.

Why does a site return 403 to the tool?

Some sites block requests from data centres or unknown bots. That is a decision of the site, not an error in the tool.

Can I check a device on my home or office network?

No. For safety, private and local addresses (192.168.x.x, 10.x.x.x, localhost, .local names and similar) are refused. Our server can only test public hosts on the internet.