HTTP Lookup
Fetch a URL over HTTP and report status, headers & redirects.
Enter a value above to run HTTP Lookup
e.g. example.com
Quick answer
HTTP Lookup fetches a URL over plain HTTP and reports the response status code, headers, and any redirect chain. Use it to see how a server responds, for example whether it returns 200 OK or redirects (301/302) to another address.
HTTP Lookup fetches a URL and shows you exactly what a browser or client sees at the protocol level: the numeric status code, every response header, and the full chain of redirects before the final page loads. Instead of guessing why a link behaves oddly, you get the raw request-response detail. It is useful for verifying that a redirect actually lands where you intend, checking whether HTTPS and security headers are set, confirming caching directives, and spotting misconfigured servers or CDNs before real visitors hit them.
How it works
The tool sends a request to the URL you enter and reads the server's reply. It records the status line (for example 200, 301, 404), then captures the response headers such as Content-Type, Location, Cache-Control, Server, and Set-Cookie. When the server answers with a 3xx redirect, the tool follows the Location header to the next URL and repeats, building an ordered list of every hop until it reaches a final non-redirect response or a loop.
How to read the results
Start with the status code: 2xx means success, 3xx a redirect, 4xx a client error like a wrong path or blocked request, and 5xx a server fault. Follow the redirect chain top to bottom and confirm each hop is intentional, especially HTTP-to-HTTPS and www normalization. Then scan headers: Location shows the redirect target, Content-Type must match the payload, and Cache-Control, Strict-Transport-Security, and Content-Security-Policy tell you how the response is cached and secured.
Common problems & fixes
Redirect chains that are too long slow every visit; collapse three hops into one direct 301. A 301 or 302 loop usually comes from conflicting www and HTTPS rules, so fix them in a single ordered rule. A 200 that returns HTML where you expected JSON often means a wrong Content-Type header. Missing Strict-Transport-Security or a wildcard Access-Control-Allow-Origin points to security tuning your server config still needs.
Frequently asked questions
- What is the difference between a 301 and a 302 redirect?
- A 301 is a permanent redirect: browsers and search engines cache it and pass link value to the new URL, which is what you want for a lasting move or an HTTPS switch. A 302 is temporary and tells clients the original URL still matters, so it is not cached long term. Using the wrong one can hurt SEO or cause stale caching.
- Why does the tool show multiple redirects for one URL?
- Many sites chain several rules together: HTTP upgrades to HTTPS, then the non-www host redirects to www, then a trailing slash or locale path is added. Each rule is a separate hop with its own status code. The chain view lets you see the full path and shorten it, since every extra redirect adds a round trip and latency for the visitor.
- Can I use this to check my security headers?
- Yes. The response headers section lists exactly what your server returns, so you can confirm Strict-Transport-Security, Content-Security-Policy, X-Content-Type-Options, and X-Frame-Options are present and correct. It also reveals the Server banner and any cookies set. Reviewing these after a config change is a fast way to catch missing or misapplied protections before deploying.