HTTP Status Checker

Find out what a web server really responds with: the final HTTP status code, the redirect chain, the response headers and whether HTTPS is used. Every request is made through a clearly identified server-side API — never disguised as a test from your machine.

Check an HTTP URL

URL

What this tool does

It contacts the URL through two independent public APIs:

microLink follows the redirect chain and reports the final status code, each hop, and the response headers its server received.
hackertarget returns the raw first response — including the original status and Location header — so you can see the first hop even when the page ultimately loads elsewhere.

Your browser also measures the time each round trip takes, which is shown separately as browser-measured.

Why it is not a fake browser request

Browsers normally refuse to read cross-origin responses (CORS), so a pure browser tool often cannot see a site's real status code. This tool deliberately does not try to bypass that restriction. Instead it uses legitimate public APIs that perform the request on their own servers. Every number is labeled either “server-side request” or “browser-measured”, so you always know who made the measurement.

Limitations & transparency

API providers run their servers in specific locations (often the US). Their connection to the target differs from yours, and their results can differ from what a visitor in your country sees. Both services also rate-limit free usage, so if one source is temporarily unavailable the tool shows a clear message and continues with the other.

The checked URL is sent by your browser to microLink and hackertarget. This site has no backend and stores no results. See the Privacy Policy.

HTTP status codes — what they mean

200 OK: Everything worked; the server returned what was requested.
301 Moved Permanently: The page has moved for good and should be bookmarked/linked at its new address. Search engines transfer ranking.
302 Found: A temporary redirect: the page is elsewhere for now, keep using the old address.
307 / 308: Redirects that preserve the request method and body — important for form submissions.
404 Not Found: The URL does not exist on the server. Common causes: typos, moved pages without redirects, deleted content.
410 Gone: Like 404, but the server explicitly says the resource existed and was intentionally removed.
500 Internal Server Error: Something broke on the server while handling the request.
502 Bad Gateway: A proxy or CDN could not get a valid response from the server behind it.
503 Service Unavailable: The server is temporarily unable to serve requests (maintenance, overload).

FAQ

Why do the two APIs sometimes disagree?

They are separate servers at separate moments in time. Caches, geo-based routing or a temporary change in the middle of a redirect chain can make them differ. The tool shows both so you can compare.

The redirect chain shows several hops. Is that bad?

Not necessarily, but each hop costs time before the page loads. Long chains (3+ hops) are a common performance smell and can break link equity. Our Website Speed Test scores redirects as part of its diagnostic score.

Does a 301 mean my site's HTTPS check failed?

A 301 from http to https is normal and healthy. The tool reports the final protocol so you can see where the chain ended.

Can you test a URL that requires a login?

No. The APIs request the public page only, without credentials. A protected URL will return whatever the server shows to anonymous visitors.

Related tools

Website Speed Test

Get the same redirect and status data plus timings and a diagnostic score.

Open Tool

SSL / HTTPS Checker

Confirm HTTPS availability, certificates and security headers.

Open Tool

DNS Lookup

Check whether the domain's DNS records look healthy.

Open Tool