Skip to content
VoltKit
Get Started
VoltKit

Website Status Checker

Find out whether a website is down for everyone or just for you. VoltKit's server requests the page, follows each redirect one hop at a time and reports the HTTP status, response time, redirect chain, security headers and full response headers.

Server-assistedFreeNo sign-up

Server-assisted. What you enter here (a domain, URL or test payload) is sent to our server to run the check. We don't save it, but our web server logs record the request, including a domain or address you entered, for about 14 days. Details

How to use the website status checker

  1. Enter the site address. A bare domain is checked over HTTPS; paste a full URL to check a specific page.
  2. Press Check status and read the verdict: reachable, error response, or not reachable at all.
  3. Follow the request chain to see every redirect, its status code and how long each hop took.
  4. Scan the headers to confirm caching, content type, server software and security headers.

Features

  • Real HTTP status code and status text of the final response, with a plain-language verdict
  • Redirect chain hop by hop, including HTTP to HTTPS and www changes, up to five hops
  • Response time per hop and in total, measured from our server
  • Security header check for HSTS, CSP, X-Content-Type-Options, X-Frame-Options, Referrer-Policy and Permissions-Policy
  • Full response headers, copyable, with cookies deliberately excluded

Reading the status code

2xx means the server answered normally. 3xx means it sent you somewhere else; a permanent 301/308 is what search engines expect for a moved page, while 302/307 are temporary. 4xx means the request was refused: 404 not found, 403 forbidden, 401 needs login, 429 rate limited. 5xx means the server itself failed: 500 crashed, 502/504 a proxy could not reach the application, 503 overloaded or in maintenance.

A site can be reachable from our server and still fail for you, or the other way round. Regional outages, DNS caches, ISP filtering and corporate proxies all affect only some paths.

What this checker does not do

It sends one GET request from a single region and does not render JavaScript, log in, or accept cookies. A 403 can simply mean the site blocks automated clients. Only public hosts on ports 80 and 443 are accepted, and redirects that point at private addresses are refused; this keeps the tool from being used to probe internal networks.

Frequently asked questions

The site is up here but not for me. What now?

Try a different network (mobile data instead of Wi-Fi), flush your DNS cache, disable a VPN, and check whether your provider or office network filters the site. If those fail, the problem is usually between your provider and the site.

Why does the chain show http, then https, then www?

That is a typical two-redirect setup: the server upgrades to HTTPS, then normalises the hostname. Two hops are fine; long chains slow every first visit and are worth collapsing into one redirect.

Why are cookies missing from the headers?

Set-Cookie headers are stripped on purpose: they can contain session identifiers for the site being checked, and they are never needed to diagnose reachability.

Does it check uptime over time?

No. Each check is a single request when you press the button. Continuous monitoring with alerts would need scheduled jobs and storage, which VoltKit does not run for this tool.

Related tools

Other tools people use alongside Website Status Checker.

You might also like

Something useful from another corner of VoltKit.